Search by property

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

Search by property

A list of all pages that have property "Contains text" with value "[[Tech WG/Ops Diary#23-01-20 Installed NTP to sync system clock]] This was done to resolve a 2FA issue involving Authy (a TOTP app) https://discord.com/channels/1049136631065628772/1049184335514828860/1065990577381974067". Since there have been only a few results, also nearby values are displayed.

Showing below up to 119 results starting with #1.

View (previous 500 | next 500) (20 | 50 | 100 | 250 | 500)

    

List of results

    • Discord Messages#mannaz-23-01-20 14:33:05  + ([[Tech WG/Ops Diary#23-01-20 Installed NTP to sync system clock]] This was done to resolve a 2FA issue involving Authy (a TOTP app) https://discord.com/channels/1049136631065628772/1049184335514828860/1065990577381974067)
    • Tech WG/Ops Diary#mannaz-23-01-20 14:33:05  + ([[Tech WG/Ops Diary#23-01-20 Installed NTP to sync system clock]] This was done to resolve a 2FA issue involving Authy (a TOTP app) https://discord.com/channels/1049136631065628772/1049184335514828860/1065990577381974067)
    • Announcements#mannaz-23-07-07 20:10:07  + (@here [[Announcements]] … @here [[Announcements]] hello #neuromatchstodon membies </br>So far [[Jonny]] and [[Manisha]] have been doing most of the admin and moderation work in cooperation with the rest of the instance members. </br></br>We are excited to welcome new members joining our working groups!🎉 🥳 </br></br>This has been a long time coming but #MastoDev extraordinaire [[Lina]] (who contributed to the Exclusive Lists PR that got merged upstream) is joining our [[Tech_WG]] 🙌 </br></br>And the amazing [[El]] (who is one of the organizers of #Maystodon #JoinMastodonDay and #NeuroParty) is joining our [[Social_WG]] 🙌 </br></br>Thank you both for your outstanding contributions ❤️ 🙏th for your outstanding contributions ❤️ 🙏)
    • Discord Messages#mannaz-23-07-07 20:10:07  + (@here [[Announcements]] … @here [[Announcements]] hello #neuromatchstodon membies </br>So far <@305044217393053697> and I have been doing most of the admin and moderation work in cooperation with the rest of the instance members. </br></br>We are excited to welcome new members joining our working groups!🎉 🥳 </br></br>This has been a long time coming but our very own #MastoDev <@485848481995423755> (who contributed to the exclusive lists PR that got merged upstream) is joining our <#1049184335514828860> 🙌 </br></br>And the amazing <@961628326005440552> (who is one of the organizers of #Maystodon #JoinMastodonDay and #NeuroParty) is joining the <#1049184264832417823> 🙌 </br></br>Thank you both for your outstanding contributions ❤️ 🙏832417823> 🙌 Thank you both for your outstanding contributions ❤️ 🙏)
    • Discord Messages#sneakers-the-rat-23-03-18 21:48:09  + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: </br>[[Mastodon/Tests]]</br>[[Mastodon/Tech WG]]</br>[[Exclusive Lists]]</br>[[Ruby Spec]]</br>[[Ruby]]</br>spec for home feed:</br>https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rb</br>for public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rb</br>that gives more examples on how feeds are supposed to be filtered</br>tag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rb</br>in case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)</br>account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rb</br></br>and so on </br></br>the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write</br>`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.</br></br>Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.js</br>and doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.</br></br>So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
    • Mastodon/Tests#sneakers-the-rat-23-03-18 21:48:09  + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: </br>[[Mastodon/Tests]]</br>[[Mastodon/Tech WG]]</br>[[Exclusive Lists]]</br>[[Ruby Spec]]</br>[[Ruby]]</br>spec for home feed:</br>https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rb</br>for public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rb</br>that gives more examples on how feeds are supposed to be filtered</br>tag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rb</br>in case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)</br>account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rb</br></br>and so on </br></br>the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write</br>`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.</br></br>Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.js</br>and doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.</br></br>So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
    • Jest#sneakers-the-rat-23-03-18 21:48:09  + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: </br>[[Mastodon/Tests]]</br>[[Mastodon/Tech WG]]</br>[[Exclusive Lists]]</br>[[Ruby Spec]]</br>[[Ruby]]</br>spec for home feed:</br>https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rb</br>for public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rb</br>that gives more examples on how feeds are supposed to be filtered</br>tag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rb</br>in case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)</br>account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rb</br></br>and so on </br></br>the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write</br>`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.</br></br>Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.js</br>and doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.</br></br>So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
    • Ruby Spec#sneakers-the-rat-23-03-18 21:48:09  + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: </br>[[Mastodon/Tests]]</br>[[Mastodon/Tech WG]]</br>[[Exclusive Lists]]</br>[[Ruby Spec]]</br>[[Ruby]]</br>spec for home feed:</br>https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rb</br>for public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rb</br>that gives more examples on how feeds are supposed to be filtered</br>tag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rb</br>in case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)</br>account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rb</br></br>and so on </br></br>the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write</br>`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.</br></br>Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.js</br>and doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.</br></br>So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
    • Ruby#sneakers-the-rat-23-03-18 21:48:09  + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: </br>[[Mastodon/Tests]]</br>[[Mastodon/Tech WG]]</br>[[Exclusive Lists]]</br>[[Ruby Spec]]</br>[[Ruby]]</br>spec for home feed:</br>https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rb</br>for public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rb</br>that gives more examples on how feeds are supposed to be filtered</br>tag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rb</br>in case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)</br>account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rb</br></br>and so on </br></br>the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write</br>`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.</br></br>Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.js</br>and doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.</br></br>So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
    • Exclusive Lists#sneakers-the-rat-23-03-18 21:48:09  + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: </br>[[Mastodon/Tests]]</br>[[Mastodon/Tech WG]]</br>[[Exclusive Lists]]</br>[[Ruby Spec]]</br>[[Ruby]]</br>spec for home feed:</br>https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rb</br>for public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rb</br>that gives more examples on how feeds are supposed to be filtered</br>tag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rb</br>in case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)</br>account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rb</br></br>and so on </br></br>the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write</br>`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.</br></br>Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.js</br>and doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.</br></br>So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
    • Consensus#sneakers-the-rat-23-02-02 03:11:06  + (Ah yes, this is a [[Consensus]] … Ah yes, this is a [[Consensus]] thing. I just updated the wiki page to explain a bit better: https://wiki.neuromatch.io/Mastodon/Governance#Voting</br>Yes, you can think of it analogously to a veto. Consensus refers both to making decisions that accommodate the needs of all members as well as consent - you should not be able to be coerced into consent by a bare majority of people. In more intimate consensus processes, a single person might be able to block a proposal. That becomes untenable in larger groups for sort of obvious reasons, hence the design of this governance system to have different proportional thresholds for different types of proposals, as well as division of decisionmaking power between working groups and the general membership. </br></br>A block means something different than voting in a few ways, including that blocks should be rare: consensus sort of inverts the decisionmaking process, where care should be taken to discuss with the membership and refine a proposal before, rather than after making the proposal - so in a majoritarian system one might make a proposal and make an argument in favor, people discuss in the comments and then make up their minds there. The purpose of requiring discussion beforehand is to make more space for everyone to craft the proposal in the first place, register concerns, etc. So if people are blocking a proposal, that is a sign that the process has failed (as opposed to in a majoritarian system that the proposal has failed). </br></br>Blocking also typically enjoins the person blocking to help remedy the reason for their block: if a proposal is being made in good faith, we assume that it is meeting some unmet need by the proposer/other members. If someone blocks a proposal, that will mean that it might cause them or the organization harm, but those unmet needs still remain - so it's basically like conflict res at that point. Ofc there are exceptions like not making marginalized ppl do additional labor, etc.marginalized ppl do additional labor, etc.)
    • Discord Messages#sneakers-the-rat-23-02-02 03:11:06  + (Ah yes, this is a [[Consensus]] … Ah yes, this is a [[Consensus]] thing. I just updated the wiki page to explain a bit better: https://wiki.neuromatch.io/Mastodon/Governance#Voting</br>Yes, you can think of it analogously to a veto. Consensus refers both to making decisions that accommodate the needs of all members as well as consent - you should not be able to be coerced into consent by a bare majority of people. In more intimate consensus processes, a single person might be able to block a proposal. That becomes untenable in larger groups for sort of obvious reasons, hence the design of this governance system to have different proportional thresholds for different types of proposals, as well as division of decisionmaking power between working groups and the general membership. </br></br>A block means something different than voting in a few ways, including that blocks should be rare: consensus sort of inverts the decisionmaking process, where care should be taken to discuss with the membership and refine a proposal before, rather than after making the proposal - so in a majoritarian system one might make a proposal and make an argument in favor, people discuss in the comments and then make up their minds there. The purpose of requiring discussion beforehand is to make more space for everyone to craft the proposal in the first place, register concerns, etc. So if people are blocking a proposal, that is a sign that the process has failed (as opposed to in a majoritarian system that the proposal has failed). </br></br>Blocking also typically enjoins the person blocking to help remedy the reason for their block: if a proposal is being made in good faith, we assume that it is meeting some unmet need by the proposer/other members. If someone blocks a proposal, that will mean that it might cause them or the organization harm, but those unmet needs still remain - so it's basically like conflict res at that point. Ofc there are exceptions like not making marginalized ppl do additional labor, etc.marginalized ppl do additional labor, etc.)
    • Wikilink#sneakers.the.rat-23-09-26 21:34:40  + (BTW since we have lotsa new people here, w … BTW since we have lotsa new people here, when I make a [[Wikilink]] we have a bot that copies your message to the wiki so we can capture discussion contextually and refine it later. Eg. In this case that previous message went here: https://wiki.neuromatch.io/Consensus#Discordtps://wiki.neuromatch.io/Consensus#Discord)
    • Discord Messages#sneakers.the.rat-23-09-26 21:34:40  + (BTW since we have lotsa new people here, w … BTW since we have lotsa new people here, when I make a [[Wikilink]] we have a bot that copies your message to the wiki so we can capture discussion contextually and refine it later. Eg. In this case that previous message went here: https://wiki.neuromatch.io/Consensus#Discordtps://wiki.neuromatch.io/Consensus#Discord)
    • Unattended Upgrades#sneakers.the.rat-23-09-21 21:37:59  + (Btw I noticed we don't have [[Unattended Upgrades]] … Btw I noticed we don't have [[Unattended Upgrades]] turned on to automatically keep system-level packages up to date. I usually do that with servers I manage because i have been told by security ppl that keeping up to date is like most of what matters with day-to-say security probs, but i mean it seems like it could uh accidentally break a package one day and kill the instance, so idk if there's a reason to not do that but thought i'd ask reason to not do that but thought i'd ask)
    • Discord Messages#sneakers.the.rat-23-09-21 21:37:59  + (Btw I noticed we don't have [[Unattended Upgrades]] … Btw I noticed we don't have [[Unattended Upgrades]] turned on to automatically keep system-level packages up to date. I usually do that with servers I manage because i have been told by security ppl that keeping up to date is like most of what matters with day-to-say security probs, but i mean it seems like it could uh accidentally break a package one day and kill the instance, so idk if there's a reason to not do that but thought i'd ask reason to not do that but thought i'd ask)
    • Discord Messages#sneakers-the-rat-22-12-17 00:07:49  + (For the moment, until we decide on a diffe … For the moment, until we decide on a different model, neuromatch bears the costs of the instance. Though we trust neuromatch to not abuse that power, one question we should answer as a community is whether we want to move to a fully cooperative model where the members of the instance support its costs so it is truly member-owned and operated. That would likely look like some sliding scale model where members are encouraged to pay what they can, a rough guideline based on nothing but vibes might be: </br>- $0/mo for students/people making <$50k annually</br>- $1/mo for postdocs/people making <$75k annually</br>- $5/mo for PIs/people making >$75k annually</br>though this would be something we would determine based on how many members we have and how much the instance costs to run. If we were to do this, then we would use opencollective to make our finances transparent. </br></br>We could also do a hybrid model where neuromatch kicks in some defined contribution and the members donate the rest, or if we establish a financial working group we could collectively apply for grants with neuromatch as a fiscal sponsor.</br></br>Another benefit is that by having some financial surplus we would be able to pay stipends to people who volunteer for mod duty/being on call for tech emergencies.</br></br>In the meantime though, mostly so the <#1049184335514828860> knows what it's working with: what kind of costs is neuromatch willing to bear? eg. upgrading to a 16GB ram node with 8 dedicated CPUs would be $120/month but would probably be as much scale as we need for the indefinite future. Currently we are going to upgrade to an 8GB ram node at $60/month, which is already $720 annually (just for the instance, we are also running another node that will host the wiki and loomio)</br><@215274946560131074> </br>[[Mastodon/Finances]][[Mastodon/Finances]])
    • Mastodon/Finances#sneakers-the-rat-22-12-17 00:07:49  + (For the moment, until we decide on a diffe … For the moment, until we decide on a different model, neuromatch bears the costs of the instance. Though we trust neuromatch to not abuse that power, one question we should answer as a community is whether we want to move to a fully cooperative model where the members of the instance support its costs so it is truly member-owned and operated. That would likely look like some sliding scale model where members are encouraged to pay what they can, a rough guideline based on nothing but vibes might be: </br>- $0/mo for students/people making <$50k annually</br>- $1/mo for postdocs/people making <$75k annually</br>- $5/mo for PIs/people making >$75k annually</br>though this would be something we would determine based on how many members we have and how much the instance costs to run. If we were to do this, then we would use opencollective to make our finances transparent. </br></br>We could also do a hybrid model where neuromatch kicks in some defined contribution and the members donate the rest, or if we establish a financial working group we could collectively apply for grants with neuromatch as a fiscal sponsor.</br></br>Another benefit is that by having some financial surplus we would be able to pay stipends to people who volunteer for mod duty/being on call for tech emergencies.</br></br>In the meantime though, mostly so the <#1049184335514828860> knows what it's working with: what kind of costs is neuromatch willing to bear? eg. upgrading to a 16GB ram node with 8 dedicated CPUs would be $120/month but would probably be as much scale as we need for the indefinite future. Currently we are going to upgrade to an 8GB ram node at $60/month, which is already $720 annually (just for the instance, we are also running another node that will host the wiki and loomio)</br><@215274946560131074> </br>[[Mastodon/Finances]][[Mastodon/Finances]])
    • Discord Messages#sneakers-the-rat-23-03-10 07:10:00  + (I just had a good idea I think: [[Mastodon/Hacks#Ideas]] … I just had a good idea I think:</br>[[Mastodon/Hacks#Ideas]] [[Zenodo Social Reading]]</br>https://neuromatch.social/@jonny/109997725222638244</br></br>> ok you know what would actually rock: a #Zenodo plugin where you could sync a collection to an #ActivityPub outbox, and do social public highlighting that way - share a set of papers under a topic for ppl to browse, but also share your annotations and then be able to show your friends annotations over the papers you're reading if u want to</br>#MastoHacks #MastoDevre reading if u want to #MastoHacks #MastoDev)
    • Zenodo Social Reading#sneakers-the-rat-23-03-10 07:10:00  + (I just had a good idea I think: [[Mastodon/Hacks#Ideas]] … I just had a good idea I think:</br>[[Mastodon/Hacks#Ideas]] [[Zenodo Social Reading]]</br>https://neuromatch.social/@jonny/109997725222638244</br></br>> ok you know what would actually rock: a #Zenodo plugin where you could sync a collection to an #ActivityPub outbox, and do social public highlighting that way - share a set of papers under a topic for ppl to browse, but also share your annotations and then be able to show your friends annotations over the papers you're reading if u want to</br>#MastoHacks #MastoDevre reading if u want to #MastoHacks #MastoDev)
    • Mastodon/Hacks#sneakers-the-rat-23-03-10 07:10:00  + (I just had a good idea I think: [[Mastodon/Hacks#Ideas]] … I just had a good idea I think:</br>[[Mastodon/Hacks#Ideas]] [[Zenodo Social Reading]]</br>https://neuromatch.social/@jonny/109997725222638244</br></br>> ok you know what would actually rock: a #Zenodo plugin where you could sync a collection to an #ActivityPub outbox, and do social public highlighting that way - share a set of papers under a topic for ppl to browse, but also share your annotations and then be able to show your friends annotations over the papers you're reading if u want to</br>#MastoHacks #MastoDevre reading if u want to #MastoHacks #MastoDev)
    • Discord Messages#mannaz-23-07-10 22:57:03  + (I think that's part of trends (but I'd nee … I think that's part of trends (but I'd need to check). and the reason why we didn't have [[Trends]] enabled was because of this: https://discord.com/channels/1049136631065628772/1052069805856935996/1067653230533804093 </br></br>if that has changed in the recent versions of masto/glitch, we can enable trends againf masto/glitch, we can enable trends again)
    • Trends#mannaz-23-07-10 22:57:03  + (I think that's part of trends (but I'd nee … I think that's part of trends (but I'd need to check). and the reason why we didn't have [[Trends]] enabled was because of this: https://discord.com/channels/1049136631065628772/1052069805856935996/1067653230533804093 </br></br>if that has changed in the recent versions of masto/glitch, we can enable trends againf masto/glitch, we can enable trends again)
    • Discord Messages#sneakers.the.rat-23-09-27 23:54:40  + (I wanted to check in before I invited some … I wanted to check in before I invited someone(s) that is not a neuromatch.social member to the discord - we already have a few beloved [[Honorary Members]] but I dont think we have any explicit norm here. Does anyone have any objection to this? </br></br>The main reason to use discord is to be able to coordinate in small groups in real time in a way masto doesn't really work for, and nothing in public channels as far as I can tell is private, so it makes sense to me for members to be able to invite ppl they vouch for? If honorary members cause trouble (which I doubt they would) then we could address that when/if it happens, it seems like prevailing social norms of being responsible for someone u bring into a space mostly take care of that yno.</br></br>If I dont hear anything in a day or so ill invite them!r anything in a day or so ill invite them!)
    • Honorary Members#sneakers.the.rat-23-09-27 23:54:40  + (I wanted to check in before I invited some … I wanted to check in before I invited someone(s) that is not a neuromatch.social member to the discord - we already have a few beloved [[Honorary Members]] but I dont think we have any explicit norm here. Does anyone have any objection to this? </br></br>The main reason to use discord is to be able to coordinate in small groups in real time in a way masto doesn't really work for, and nothing in public channels as far as I can tell is private, so it makes sense to me for members to be able to invite ppl they vouch for? If honorary members cause trouble (which I doubt they would) then we could address that when/if it happens, it seems like prevailing social norms of being responsible for someone u bring into a space mostly take care of that yno.</br></br>If I dont hear anything in a day or so ill invite them!r anything in a day or so ill invite them!)
    • Tech WG/Ops Diary#sneakers-the-rat-22-12-25 01:59:05  + (OK [[Tech WG/Ops Diary#22-12-24]] … OK</br>[[Tech WG/Ops Diary#22-12-24]] going to pull in a few upgrades:</br>https://github.com/NeuromatchAcademy/mastodon/pull/7</br>* Mathjax</br>* Larger Post Previews</br>* Default false notifications for new follows</br>* Autofollow accounts</br></br>And also pulling in updates from upstream glitch-soc, which in my test run means that we have to upgrade node from 14 to 16that we have to upgrade node from 14 to 16)
    • Discord Messages#sneakers-the-rat-22-12-25 01:59:05  + (OK [[Tech WG/Ops Diary#22-12-24]] … OK</br>[[Tech WG/Ops Diary#22-12-24]] going to pull in a few upgrades:</br>https://github.com/NeuromatchAcademy/mastodon/pull/7</br>* Mathjax</br>* Larger Post Previews</br>* Default false notifications for new follows</br>* Autofollow accounts</br></br>And also pulling in updates from upstream glitch-soc, which in my test run means that we have to upgrade node from 14 to 16that we have to upgrade node from 14 to 16)
    • Discord Messages#sneakers.the.rat-23-12-05 06:58:02  + (OK <@318247805124870145> i'm doing a … OK <@318247805124870145> i'm doing a little wiki gardening rn and here i'll narrate a little of what i'm doing as i do it to give you a sense of what that looks like:</br></br>first i am reading this and wondering how i could offer part of this to you, and with this set of prompts and with ur previous comments about 'where do i even start with this thing' which are extremely justified i want to make a 'how to get started with masto as software' page, so I go to where we have previously put such things on the Tech WG page (https://wiki.neuromatch.social/Tech_WG ) and add a link there to a new [[Intro To Mastohacking]] page ( https://wiki.neuromatch.social/Intro_To_Mastohacking ) since i figure "intro to mastodon" is too much like our general getting started on fedi pages. idk we can always change it later.</br></br>So then i do a search for "docs" to see where else we might have written stuff like this and lo and behold there's also a page for that, so i add a link from there too: https://wiki.neuromatch.social/Mastodon/Docs</br></br>then i start my new page by adding categories and backlinks. Don't worry about the syntax for right now, but what i'm doing here is making this page findable in a few different ways - by navigating from related pages, formally through the semantic relationship `Part Of`, and then also via the category system (which we can also query to eg. display a list of all pages in the "hacking" and "guide" categories if we want to make some automatic index, but i digress).</br></br>nothing on the page yet but that? fuck it, save page. we can keep saving as we update, no need to be shy on wiki</br></br>(sorry for notifs el i'm going to split this up into a few messages so i can intersperse images)into a few messages so i can intersperse images))
    • Discord Messages#sneakers-the-rat-22-12-17 05:57:19  + (OK [[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]])
    • Tech WG/Ops Diary#sneakers-the-rat-22-12-17 05:57:19  + (OK [[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]])
    • NMA#sneakers-the-rat-23-04-01 22:32:47  + (QUESTION isn't [[NMA]] … QUESTION isn't [[NMA]] coming up? and maybe [[NMC]] at some point???? how can the instance support that????? can we make some cool pages for people to share their code or whatever, index the talks in a conference, etc???? I have posted a few ideas before in the neuromatch slack but wanted to pose this generally to the instance and see if we can yno use that as a motivating reason to do some masto hacking</br>tagging the neuromatch ppl I know are on the discord <@540104559079456770> <@1050459047582781480> <@215274946560131074> <@651480296415297553> and who else sorry I don't have a list</br>[[Mastodon and Neuromatch]]</br>[[Neuromatch and Mastodon]] (idk lol I'll just redirect one page to another)</br>[[Infrastructure]][[Infrastructure]])
    • NMC#sneakers-the-rat-23-04-01 22:32:47  + (QUESTION isn't [[NMA]] … QUESTION isn't [[NMA]] coming up? and maybe [[NMC]] at some point???? how can the instance support that????? can we make some cool pages for people to share their code or whatever, index the talks in a conference, etc???? I have posted a few ideas before in the neuromatch slack but wanted to pose this generally to the instance and see if we can yno use that as a motivating reason to do some masto hacking</br>tagging the neuromatch ppl I know are on the discord <@540104559079456770> <@1050459047582781480> <@215274946560131074> <@651480296415297553> and who else sorry I don't have a list</br>[[Mastodon and Neuromatch]]</br>[[Neuromatch and Mastodon]] (idk lol I'll just redirect one page to another)</br>[[Infrastructure]][[Infrastructure]])
    • Mastodon and Neuromatch#sneakers-the-rat-23-04-01 22:32:47  + (QUESTION isn't [[NMA]] … QUESTION isn't [[NMA]] coming up? and maybe [[NMC]] at some point???? how can the instance support that????? can we make some cool pages for people to share their code or whatever, index the talks in a conference, etc???? I have posted a few ideas before in the neuromatch slack but wanted to pose this generally to the instance and see if we can yno use that as a motivating reason to do some masto hacking</br>tagging the neuromatch ppl I know are on the discord <@540104559079456770> <@1050459047582781480> <@215274946560131074> <@651480296415297553> and who else sorry I don't have a list</br>[[Mastodon and Neuromatch]]</br>[[Neuromatch and Mastodon]] (idk lol I'll just redirect one page to another)</br>[[Infrastructure]][[Infrastructure]])
    • Infrastructure#sneakers-the-rat-23-04-01 22:32:47  + (QUESTION isn't [[NMA]] … QUESTION isn't [[NMA]] coming up? and maybe [[NMC]] at some point???? how can the instance support that????? can we make some cool pages for people to share their code or whatever, index the talks in a conference, etc???? I have posted a few ideas before in the neuromatch slack but wanted to pose this generally to the instance and see if we can yno use that as a motivating reason to do some masto hacking</br>tagging the neuromatch ppl I know are on the discord <@540104559079456770> <@1050459047582781480> <@215274946560131074> <@651480296415297553> and who else sorry I don't have a list</br>[[Mastodon and Neuromatch]]</br>[[Neuromatch and Mastodon]] (idk lol I'll just redirect one page to another)</br>[[Infrastructure]][[Infrastructure]])
    • Discord Messages#sneakers-the-rat-23-04-01 22:32:47  + (QUESTION isn't [[NMA]] … QUESTION isn't [[NMA]] coming up? and maybe [[NMC]] at some point???? how can the instance support that????? can we make some cool pages for people to share their code or whatever, index the talks in a conference, etc???? I have posted a few ideas before in the neuromatch slack but wanted to pose this generally to the instance and see if we can yno use that as a motivating reason to do some masto hacking</br>tagging the neuromatch ppl I know are on the discord <@540104559079456770> <@1050459047582781480> <@215274946560131074> <@651480296415297553> and who else sorry I don't have a list</br>[[Mastodon and Neuromatch]]</br>[[Neuromatch and Mastodon]] (idk lol I'll just redirect one page to another)</br>[[Infrastructure]][[Infrastructure]])
    • Neuromatch and Mastodon#sneakers-the-rat-23-04-01 22:32:47  + (QUESTION isn't [[NMA]] … QUESTION isn't [[NMA]] coming up? and maybe [[NMC]] at some point???? how can the instance support that????? can we make some cool pages for people to share their code or whatever, index the talks in a conference, etc???? I have posted a few ideas before in the neuromatch slack but wanted to pose this generally to the instance and see if we can yno use that as a motivating reason to do some masto hacking</br>tagging the neuromatch ppl I know are on the discord <@540104559079456770> <@1050459047582781480> <@215274946560131074> <@651480296415297553> and who else sorry I don't have a list</br>[[Mastodon and Neuromatch]]</br>[[Neuromatch and Mastodon]] (idk lol I'll just redirect one page to another)</br>[[Infrastructure]][[Infrastructure]])
    • Social WG/Responsibilities#mannaz-23-07-07 00:50:28  + (Thank you El and welcome onboard!! woohoo! … Thank you El and welcome onboard!! woohoo!! 🥳 ❤️ 💚 💜 💙 🧡 </br></br>[[Social WG/Responsibilities]] continued: with great power comes great responsibility :) </br></br>Before taking any drastic decisions, we should discuss things with the instance -- things like defederation/limiting instances and banning accounts. Also, we should be careful when speaking on behalf of the instance from our "official" accounts like the @socialwg one (this one is quite scary for me because sometime mods say something that ticks another mod/instance member off and then it leads to pile ons 😬 -- so we try to be as cordial as possible and respect people from other instances even if they choose different things for their community - that's fine. we all don't have to be an exact replica of each other :) )</br></br>we learn new things from other mods too -- I follow the #fediblock hashtag and keep an eye on anything that could affect us terribly. In the past we have blocked instances based on reports from other mods on this hashtag (see <#1055915765133488158>) </br></br>I've been on call since December https://wiki.neuromatch.io/Mastodon/Mods_On_Call. You could add your availability here. Let's get you wiki access as well if you don't have already. Create an account here: https://wiki.neuromatch.io and <@305044217393053697> can approve it when they are back from their short holiday. </br></br>Being on call means I check for new account requests once a day and approve them if there aren't any issues. Or bring the discussion to the instance. And handle any reports. We get updates from linode when a few settings cross a threshold. Usually it just means the instance has been busy. But it could also be a DDoS attack -- so I also quickly browse through our local TL and this discord to see nothings blowing up. We have an admin@neuromatch.social account that I monitor every few days. We get very few emails there. monitor every few days. We get very few emails there.)
    • Discord Messages#mannaz-23-07-07 00:50:28  + (Thank you El and welcome onboard!! woohoo! … Thank you El and welcome onboard!! woohoo!! 🥳 ❤️ 💚 💜 💙 🧡 </br></br>[[Social WG/Responsibilities]] continued: with great power comes great responsibility :) </br></br>Before taking any drastic decisions, we should discuss things with the instance -- things like defederation/limiting instances and banning accounts. Also, we should be careful when speaking on behalf of the instance from our "official" accounts like the @socialwg one (this one is quite scary for me because sometime mods say something that ticks another mod/instance member off and then it leads to pile ons 😬 -- so we try to be as cordial as possible and respect people from other instances even if they choose different things for their community - that's fine. we all don't have to be an exact replica of each other :) )</br></br>we learn new things from other mods too -- I follow the #fediblock hashtag and keep an eye on anything that could affect us terribly. In the past we have blocked instances based on reports from other mods on this hashtag (see <#1055915765133488158>) </br></br>I've been on call since October https://wiki.neuromatch.io/Mastodon/Mods_On_Call. You could add your availability here. Let's get you wiki access as well if you don't have already. Create an account here: https://wiki.neuromatch.io and <@305044217393053697> can approve it when they are back from their short holiday. </br></br>Being on call means I check for new account requests once a day and approve them if there aren't any issues. Or bring the discussion to the instance. And handle any reports. We get updates from linode when a few settings cross a threshold. Usually it just means the instance has been busy. But it could also be a DDoS attack -- so I also quickly browse through our local TL and this discord to see nothings blowing up. We have an admin@neuromatch.social account that I monitor every few days. We get very few emails there. monitor every few days. We get very few emails there.)
    • Social WG/Responsibilities#mannaz-23-07-06 23:31:37  + (Thank you soo much El!! This would be amaz … Thank you soo much El!! This would be amazing! to be frank, you already help us here in the working group and we all truly appreciate that ❤️ </br></br>[[Social WG/Responsibilities]] If you officially join, what this would do is allow us to give you access to the moderation interface where we handle new account requests and reports, and you'd also publicly get the credit that you deserve for all your contributions! :) I think some academics can be really stingy about giving credits (uh see one of my recent polls :P https://neuromatch.social/@manisha/110556283019459141) but in a place like ours where we are all volunteers doing the work, every bit of appreciation goes a long way. So another thing we could be doing more often is showing gratitude to instance members and like <@305044217393053697> mentioned -- make everyone feel welcome and improve our onboarding experience. Like recently from the socialwg account, I've been boosting intros, lab pics, graduation news, etc etc.. We could make all of that more fun and be like "hey #neuromatchstodon <awesome NMS member> got their PhD give them boosts" 🥳 or something </br></br>Account requests are usually the fun part of moderation -- I love reading the reasons people/organizations/departments/conferences share for joining the instance and they are always so interesting and diverse! (e.g. the time someone said they had fomo of not being on neuromatch.social ❤️ https://discord.com/channels/1049136631065628772/1049136631065628775/1116378014897426432)</br></br>The only thing to be careful of is if the account requester mentions something that could be a violation of our rules or our bylaws. In such instances, I typically ask the instance for their opinion on our social wg forum channel. For full transparency we do have a private mod channel but we haven't used that since April! A good sign that we are not hiding things from the instance. We used to use it only for cases where we had to disclose some PIIse it only for cases where we had to disclose some PII)
    • Discord Messages#mannaz-23-07-06 23:31:37  + (Thank you soo much El!! This would be amaz … Thank you soo much El!! This would be amazing! to be frank, you already help us here in the working group and we all truly appreciate that ❤️ </br></br>[[Social WG/Responsibilities]] If you officially join, what this would do is allow us to give you access to the moderation interface where we handle new account requests and reports, and you'd also publicly get the credit that you deserve for all your contributions! :) I think some academics can be really stingy about giving credits (uh see one of my recent polls :P https://neuromatch.social/@manisha/110556283019459141) but in a place like ours where we are all volunteers doing the work, every bit of appreciation goes a long way. So another thing we could be doing more often is showing gratitude to instance members and like <@305044217393053697> mentioned -- make everyone feel welcome and improve our onboarding experience. Like recently from the socialwg account, I've been boosting intros, lab pics, graduation news, etc etc.. We could make all of that more fun and be like "hey #neuromatchstodon <awesome NMS member> got their PhD give them boosts" 🥳 or something </br></br>Account requests are usually the fun part of moderation -- I love reading the reasons people/organizations/departments/conferences share for joining the instance and they are always so interesting and diverse! (e.g. the time someone said they had fomo of not being on neuromatch.social ❤️ https://discord.com/channels/1049136631065628772/1049136631065628775/1116378014897426432)</br></br>The only thing to be careful of is if the account requester mentions something that could be a violation of our rules or our bylaws. In such instances, I typically ask the instance for their opinion on our social wg forum channel. For full transparency we do have a private mod channel but we haven't used that since April! A good sign that we are not hiding things from the instance. We used to use it only for cases where we had to disclose some PIIse it only for cases where we had to disclose some PII)
    • Knowledge Group#mannaz-23-05-31 23:55:22  + (Those are great ideas!! We'd shared some o … Those are great ideas!! We'd shared some of these on the NM conference channel as well and there is definitely some interest around it. So this is exciting! </br></br>> forum mode! one thing I would love is for NMS to be a place where non-neuroscientists can come and ask questions of neuroscientists...</br>Yess! I've also been thinking of how to break down the barriers between scientists and non-scientists in general and for the NM and climatematch communities. Currently if anyone wants to be a part of the NM/CM community they need to be actively involved with it somehow -- as a student/TA/conference presenter/organizer/mentor/volunteer/... but with NMS anyone whose interests and values align is welcome to join us and hang out with a bunch of scientists. NMS is a low barrier entry to the community and expands the scope of the community! </br></br>I think forums would be great for the [[Knowledge Group]] [[Knowledge Club]] that we've discussed [here](https://discord.com/channels/1049136631065628772/1049184264832417823/1106307113359265932) and looks like there is interest for it in even outside of neuroscience (on the same thread that Jonny linked earlier -- https://weirder.earth/@dessertgeek/110460194256055941 and my response https://neuromatch.social/@manisha/110463002047148596). </br></br>The only thing with forum mode is we'd need to figure out how to basically take lemmy's code and make it work with masto. Easiest would be to host it as a separate forum.neuromatch.social subdomain but it would be awesome if folks didn't have to create a separate account for that. We could ask for funding to implement the forum mode with DIY stuff where we hack it to make it work with masto accounts?? does that seem feasible?ith masto accounts?? does that seem feasible?)
    • Knowledge Club#mannaz-23-05-31 23:55:22  + (Those are great ideas!! We'd shared some o … Those are great ideas!! We'd shared some of these on the NM conference channel as well and there is definitely some interest around it. So this is exciting! </br></br>> forum mode! one thing I would love is for NMS to be a place where non-neuroscientists can come and ask questions of neuroscientists...</br>Yess! I've also been thinking of how to break down the barriers between scientists and non-scientists in general and for the NM and climatematch communities. Currently if anyone wants to be a part of the NM/CM community they need to be actively involved with it somehow -- as a student/TA/conference presenter/organizer/mentor/volunteer/... but with NMS anyone whose interests and values align is welcome to join us and hang out with a bunch of scientists. NMS is a low barrier entry to the community and expands the scope of the community! </br></br>I think forums would be great for the [[Knowledge Group]] [[Knowledge Club]] that we've discussed [here](https://discord.com/channels/1049136631065628772/1049184264832417823/1106307113359265932) and looks like there is interest for it in even outside of neuroscience (on the same thread that Jonny linked earlier -- https://weirder.earth/@dessertgeek/110460194256055941 and my response https://neuromatch.social/@manisha/110463002047148596). </br></br>The only thing with forum mode is we'd need to figure out how to basically take lemmy's code and make it work with masto. Easiest would be to host it as a separate forum.neuromatch.social subdomain but it would be awesome if folks didn't have to create a separate account for that. We could ask for funding to implement the forum mode with DIY stuff where we hack it to make it work with masto accounts?? does that seem feasible?ith masto accounts?? does that seem feasible?)
    • Discord Messages#mannaz-23-05-31 23:55:22  + (Those are great ideas!! We'd shared some o … Those are great ideas!! We'd shared some of these on the NM conference channel as well and there is definitely some interest around it. So this is exciting! </br></br>> forum mode! one thing I would love is for NMS to be a place where non-neuroscientists can come and ask questions of neuroscientists...</br>Yess! I've also been thinking of how to break down the barriers between scientists and non-scientists in general and for the NM and climatematch communities. Currently if anyone wants to be a part of the NM/CM community they need to be actively involved with it somehow -- as a student/TA/conference presenter/organizer/mentor/volunteer/... but with NMS anyone whose interests and values align is welcome to join us and hang out with a bunch of scientists. NMS is a low barrier entry to the community and expands the scope of the community! </br></br>I think forums would be great for the [[Knowledge Group]] [[Knowledge Club]] that we've discussed [here](https://discord.com/channels/1049136631065628772/1049184264832417823/1106307113359265932) and looks like there is interest for it in even outside of neuroscience (on the same thread that Jonny linked earlier -- https://weirder.earth/@dessertgeek/110460194256055941 and my response https://neuromatch.social/@manisha/110463002047148596). </br></br>The only thing with forum mode is we'd need to figure out how to basically take lemmy's code and make it work with masto. Easiest would be to host it as a separate forum.neuromatch.social subdomain but it would be awesome if folks didn't have to create a separate account for that. We could ask for funding to implement the forum mode with DIY stuff where we hack it to make it work with masto accounts?? does that seem feasible?ith masto accounts?? does that seem feasible?)
    • Access Policy#mannazsci-23-08-30 08:45:21  + ([[Access_Policy]] for - Server shell acces … [[Access_Policy]] for</br>- Server shell access : root, user</br>- Git repo access: admin, maintain, write, triage, read </br>- email accounts: admin@ noreply@</br>- Mastodon Admin portal</br>- Mastodon @admin account</br>- Mastodon @techwg account</br>- Sendgrid </br>- Loomio </br>- Wiki </br>- DNS (neuromatch.social) </br>- Discord mod chat : discord roles until we move away from discord</br></br>Based on the access policy we decide, we would need to update access and note that on this page: https://wiki.neuromatch.io/Administrators https://wiki.neuromatch.io/Administrators)
    • Discord Messages#mannazsci-23-08-30 08:45:21  + ([[Access_Policy]] for - Server shell acces … [[Access_Policy]] for</br>- Server shell access : root, user</br>- Git repo access: admin, maintain, write, triage, read </br>- email accounts: admin@ noreply@</br>- Mastodon Admin portal</br>- Mastodon @admin account</br>- Mastodon @techwg account</br>- Sendgrid </br>- Loomio </br>- Wiki </br>- DNS (neuromatch.social) </br>- Discord mod chat : discord roles until we move away from discord</br></br>Based on the access policy we decide, we would need to update access and note that on this page: https://wiki.neuromatch.io/Administrators https://wiki.neuromatch.io/Administrators)
    • Discord Messages#mannaz-22-12-24 09:07:52  + ([[Mastodon/Tech WG#Done]] changed default email notifications in config/settings.yml to turn off new follow notifs and restarted services)
    • Discord Messages#sneakers-the-rat-22-12-12 18:51:13  + ([[Mastodon/Tech WG#Project Ideas]]: Collapse long lists of @'s in posts. see https://scholar.social/@neuralreckoning/109501954921707960)
    • Wasabi#sneakers-the-rat-22-12-14 08:21:18  + ([[Mastodon/Tech WG#TODO]] [[Mastodon/Storage#TODO]] investigate [[Wasabi]] for storage 🙂)
    • Mastodon/Storage#sneakers-the-rat-22-12-14 08:21:18  + ([[Mastodon/Tech WG#TODO]] [[Mastodon/Storage#TODO]] investigate [[Wasabi]] for storage 🙂)
    • Discord Messages#sneakers-the-rat-22-12-14 08:21:18  + ([[Mastodon/Tech WG#TODO]] [[Mastodon/Storage#TODO]] investigate [[Wasabi]] for storage 🙂)
    • Hack Merging Policy#sneakers-the-rat-22-12-27 19:53:46  + ([[Mastodon/Tech WG#TODO]] Make a [[Hacking Masto]] guide including setting up a [[Mastodon/Dev Environment]] and a [[Hack Merging Policy]])
    • Hacking Masto#sneakers-the-rat-22-12-27 19:53:46  + ([[Mastodon/Tech WG#TODO]] Make a [[Hacking Masto]] guide including setting up a [[Mastodon/Dev Environment]] and a [[Hack Merging Policy]])
    • Mastodon/Dev Environment#sneakers-the-rat-22-12-27 19:53:46  + ([[Mastodon/Tech WG#TODO]] Make a [[Hacking Masto]] guide including setting up a [[Mastodon/Dev Environment]] and a [[Hack Merging Policy]])
    • Discord Messages#mannaz-22-12-16 14:51:09  + ([[Mastodon/Tech WG#TODO]] [[Mastodon/Social WG#TODO]] Look into setting up Relays https://neuromatch.social/@manisha/109523786200081610)
    • Discord Messages#sneakers-the-rat-22-12-18 00:23:06  + ([[Mastodon/Tech WG#TODO]] [[Translation]] … [[Mastodon/Tech WG#TODO]] [[Translation]] services! can we do something like Kolektiva does: https://kolektiva.social/@subMedia/109531114768269437 isn't there some fancy new offline/self-contained translation network thing??? I don't want to make any calls to Google from the instance but translation would be greathe instance but translation would be great)
    • Translation#sneakers-the-rat-22-12-18 00:23:06  + ([[Mastodon/Tech WG#TODO]] [[Translation]] … [[Mastodon/Tech WG#TODO]] [[Translation]] services! can we do something like Kolektiva does: https://kolektiva.social/@subMedia/109531114768269437 isn't there some fancy new offline/self-contained translation network thing??? I don't want to make any calls to Google from the instance but translation would be greathe instance but translation would be great)
    • Discord Messages#sneakers-the-rat-22-12-15 21:59:34  + ([[Mastodon/Tech WG#TODO]] change default email notifications to turn off new follow notifs)
    • Discord Messages#sneakers-the-rat-22-12-15 22:57:13  + ([[Mastodon/Tech WG#TODO]]: - Fix semantic … [[Mastodon/Tech WG#TODO]]: </br>- Fix semantic wikilinks in the [[WikiBot#TODO]], </br>- Allow `:` prefixed wikilinks to link to a page without embedding the post in that page (and then ofc stripping the colon) - this would trade off with n-back wikilinks because it wouldn't make sense to archive a series of posts at the same time as not embedding the posts into a pageime as not embedding the posts into a page)
    • WikiBot#sneakers-the-rat-22-12-15 22:57:13  + ([[Mastodon/Tech WG#TODO]]: - Fix semantic … [[Mastodon/Tech WG#TODO]]: </br>- Fix semantic wikilinks in the [[WikiBot#TODO]], </br>- Allow `:` prefixed wikilinks to link to a page without embedding the post in that page (and then ofc stripping the colon) - this would trade off with n-back wikilinks because it wouldn't make sense to archive a series of posts at the same time as not embedding the posts into a pageime as not embedding the posts into a page)
    • Discord Messages#sneakers-the-rat-22-12-10 06:24:49  + ([[Mastodon/Tech WG#TODO]]: Change the favicon i have way too many instances open in my tabs for this)
    • Discord Messages#sneakers-the-rat-22-12-22 18:51:13  + ([[Mastodon/Tech WG#TODO]]: Secrets manager/password manager so we can have shared accounts better 🙂)
    • Discord Messages#sneakers-the-rat-22-12-17 22:13:21  + ([[Mastodon/Tech WG#TODO]]: increase the size of collapsed messages: https://neuromatch.social/@PessoaBrain/109530080695260906)
    • Discord Messages#sneakers-the-rat-22-12-18 21:14:38  + ([[Mastodon/Tech WG#TODO]]: why are follow buttons not present for all instances for user accounts on the notification feed?)
    • Linode#sneakers-the-rat-22-12-17 06:03:49  + ([[Tech WG/Ops Diary#22-12-16 Upgrading Lin … [[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Following the instructions to </br>* [[Resizing Linode]] [[Linode]]: https://www.linode.com/docs/guides/resizing-a-linode/</br>* [[Mastodon/Admin#Shutdown]]: https://docs.joinmastodon.org/admin/migrating/ from the migraing docsrg/admin/migrating/ from the migraing docs)
    • Resizing Linode#sneakers-the-rat-22-12-17 06:03:49  + ([[Tech WG/Ops Diary#22-12-16 Upgrading Lin … [[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Following the instructions to </br>* [[Resizing Linode]] [[Linode]]: https://www.linode.com/docs/guides/resizing-a-linode/</br>* [[Mastodon/Admin#Shutdown]]: https://docs.joinmastodon.org/admin/migrating/ from the migraing docsrg/admin/migrating/ from the migraing docs)
    • Discord Messages#sneakers-the-rat-22-12-17 06:19:24  + ([[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Mission accomplished. by god we've done it)
    • Tech WG/Ops Diary#sneakers-the-rat-22-12-17 06:19:24  + ([[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Mission accomplished. by god we've done it)
    • Admin#sneakers-the-rat-22-12-17 06:03:49  + ([[Tech WG/Ops Diary#22-12-16 Upgrading Lin … [[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Following the instructions to </br>* [[Resizing Linode]] [[Linode]]: https://www.linode.com/docs/guides/resizing-a-linode/</br>* [[Mastodon/Admin#Shutdown]]: https://docs.joinmastodon.org/admin/migrating/ from the migraing docsrg/admin/migrating/ from the migraing docs)
    • Tech WG/Ops Diary#mannaz-23-04-25 12:52:00  + ([[Tech WG/Ops Diary#23-04-25]]: restarted systems services as we were hitting swap limits https://neuromatch.social/@manisha/110259466647197417)
    • Discord Messages#mannaz-23-04-25 12:52:00  + ([[Tech WG/Ops Diary#23-04-25]]: restarted systems services as we were hitting swap limits https://neuromatch.social/@manisha/110259466647197417)
    • TODO#sneakers-the-rat-23-05-20 06:08:40  + ([[Tech WG/Ops Diary#23-05-19]]: [[TODO]] c … [[Tech WG/Ops Diary#23-05-19]]: [[TODO]] check out how user-specific settings were reformatted re: config/settings.yml. See also https://discord.com/channels/1049136631065628772/1049184335514828860/1109359788602707988 and https://discord.com/channels/1049136631065628772/1049184335514828860/110936074243355854872/1049184335514828860/1109360742433558548)
    • Tech WG/Ops Diary#sneakers-the-rat-23-05-20 05:46:32  + ([[Tech WG/Ops Diary#23-05-19]]: We are att … [[Tech WG/Ops Diary#23-05-19]]: We are attempting to [[Upgrade Mastodon]] to 4.1.2 and also merge in [[Exclusive Lists]], wish us luck. </br></br>We begin with what is probably the worst way to do it based on the conversation in <#1049184335514828860> , specifically:</br></br>* main -> dev, </br>* upstream -> dev, </br>* dev -> pr, </br>* pr -> dev, </br>* dev -> main </br></br>https://discord.com/channels/1049136631065628772/1049184335514828860/1109355378178789396els/1049136631065628772/1049184335514828860/1109355378178789396)
    • Tech WG/Ops Diary#sneakers-the-rat-23-05-20 06:08:40  + ([[Tech WG/Ops Diary#23-05-19]]: [[TODO]] c … [[Tech WG/Ops Diary#23-05-19]]: [[TODO]] check out how user-specific settings were reformatted re: config/settings.yml. See also https://discord.com/channels/1049136631065628772/1049184335514828860/1109359788602707988 and https://discord.com/channels/1049136631065628772/1049184335514828860/110936074243355854872/1049184335514828860/1109360742433558548)
    • Exclusive Lists#sneakers-the-rat-23-05-20 05:46:32  + ([[Tech WG/Ops Diary#23-05-19]]: We are att … [[Tech WG/Ops Diary#23-05-19]]: We are attempting to [[Upgrade Mastodon]] to 4.1.2 and also merge in [[Exclusive Lists]], wish us luck. </br></br>We begin with what is probably the worst way to do it based on the conversation in <#1049184335514828860> , specifically:</br></br>* main -> dev, </br>* upstream -> dev, </br>* dev -> pr, </br>* pr -> dev, </br>* dev -> main </br></br>https://discord.com/channels/1049136631065628772/1049184335514828860/1109355378178789396els/1049136631065628772/1049184335514828860/1109355378178789396)
    • Upgrade Mastodon#sneakers-the-rat-23-05-20 05:46:32  + ([[Tech WG/Ops Diary#23-05-19]]: We are att … [[Tech WG/Ops Diary#23-05-19]]: We are attempting to [[Upgrade Mastodon]] to 4.1.2 and also merge in [[Exclusive Lists]], wish us luck. </br></br>We begin with what is probably the worst way to do it based on the conversation in <#1049184335514828860> , specifically:</br></br>* main -> dev, </br>* upstream -> dev, </br>* dev -> pr, </br>* pr -> dev, </br>* dev -> main </br></br>https://discord.com/channels/1049136631065628772/1049184335514828860/1109355378178789396els/1049136631065628772/1049184335514828860/1109355378178789396)
    • Discord Messages#sneakers-the-rat-23-05-20 05:46:32  + ([[Tech WG/Ops Diary#23-05-19]]: We are att … [[Tech WG/Ops Diary#23-05-19]]: We are attempting to [[Upgrade Mastodon]] to 4.1.2 and also merge in [[Exclusive Lists]], wish us luck. </br></br>We begin with what is probably the worst way to do it based on the conversation in <#1049184335514828860> , specifically:</br></br>* main -> dev, </br>* upstream -> dev, </br>* dev -> pr, </br>* pr -> dev, </br>* dev -> main </br></br>https://discord.com/channels/1049136631065628772/1049184335514828860/1109355378178789396els/1049136631065628772/1049184335514828860/1109355378178789396)
    • Discord Messages#sneakers-the-rat-23-05-20 06:08:40  + ([[Tech WG/Ops Diary#23-05-19]]: [[TODO]] c … [[Tech WG/Ops Diary#23-05-19]]: [[TODO]] check out how user-specific settings were reformatted re: config/settings.yml. See also https://discord.com/channels/1049136631065628772/1049184335514828860/1109359788602707988 and https://discord.com/channels/1049136631065628772/1049184335514828860/110936074243355854872/1049184335514828860/1109360742433558548)
    • Exclusive Lists#sneakers-the-rat-23-05-23 01:35:39  + ([[Tech WG/Ops Diary#23-05-22]]: What up it's me and we're about to deploy [[Exclusive Lists]] and update to 4.1.2. starting by making a linode backup and then following instructions on https://github.com/mastodon/mastodon/releases/tag/v4.1.2)
    • Tech WG/Ops Diary#sneakers-the-rat-23-05-23 01:35:39  + ([[Tech WG/Ops Diary#23-05-22]]: What up it's me and we're about to deploy [[Exclusive Lists]] and update to 4.1.2. starting by making a linode backup and then following instructions on https://github.com/mastodon/mastodon/releases/tag/v4.1.2)
    • Discord Messages#sneakers-the-rat-23-05-23 01:35:39  + ([[Tech WG/Ops Diary#23-05-22]]: What up it's me and we're about to deploy [[Exclusive Lists]] and update to 4.1.2. starting by making a linode backup and then following instructions on https://github.com/mastodon/mastodon/releases/tag/v4.1.2)
    • Tech WG/Ops Diary#mannaz-23-06-27 12:20:04  + ([[Tech WG/Ops Diary#23-06-27]]: restarted systems services as we were hitting swap limits https://neuromatch.social/@manisha/110616054514875151 This time I remembered to take a screenshot before and after)
    • Discord Messages#mannaz-23-06-27 12:20:04  + ([[Tech WG/Ops Diary#23-06-27]]: restarted systems services as we were hitting swap limits https://neuromatch.social/@manisha/110616054514875151 This time I remembered to take a screenshot before and after)
    • Discord Messages#mannaz-23-07-07 18:47:50  + ([[Tech WG/Ops Diary#23-07-07]]: masto 4.1. … [[Tech WG/Ops Diary#23-07-07]]: masto 4.1.3 update -- security patch. Jonny's on the road so Lina and Manisha are going to give this a try. If we muck something up, please be kind 🥺 starting by making a linode backup and then following instructions on ... </br></br>oh wait! dang they already released 4.1.4 just an hour ago </br>https://github.com/mastodon/mastodon/releases/tag/v4.1.4 </br></br>4.1.3 from yesterday: https://github.com/mastodon/mastodon/releases/tag/v4.1.3.com/mastodon/mastodon/releases/tag/v4.1.3)
    • Tech WG/Ops Diary#mannaz-23-07-07 18:47:50  + ([[Tech WG/Ops Diary#23-07-07]]: masto 4.1. … [[Tech WG/Ops Diary#23-07-07]]: masto 4.1.3 update -- security patch. Jonny's on the road so Lina and Manisha are going to give this a try. If we muck something up, please be kind 🥺 starting by making a linode backup and then following instructions on ... </br></br>oh wait! dang they already released 4.1.4 just an hour ago </br>https://github.com/mastodon/mastodon/releases/tag/v4.1.4 </br></br>4.1.3 from yesterday: https://github.com/mastodon/mastodon/releases/tag/v4.1.3.com/mastodon/mastodon/releases/tag/v4.1.3)
    • Tech WG/Ops Diary#mannaz-23-07-10 00:35:37  + ([[Tech WG/Ops Diary#23-07-09]]: Updating r … [[Tech WG/Ops Diary#23-07-09]]: Updating reverse proxy config to the recommended one</br>as root</br></br>cd /etc/nginx</br>cd sites-enabled</br>vim mastodon</br></br>search for "system"</br>added the following two headers in that block as per the release notes:</br></br>`add_header X-Content-Type-Options nosniff;</br> add_header Content-Security-Policy "default-src 'none'; form-action 'none'";`</br></br>save</br>test nginx configs are valid or not (w/o running)</br></br>`nginx -t`</br></br>all looked good</br></br>`nginx: the configuration file /etc/nginx/nginx.conf syntax is ok</br>nginx: configuration file /etc/nginx/nginx.conf test is successful`</br></br>Reload nginx</br>`nginx reload`s successful` Reload nginx `nginx reload`)
    • Discord Messages#mannaz-23-07-10 00:35:37  + ([[Tech WG/Ops Diary#23-07-09]]: Updating r … [[Tech WG/Ops Diary#23-07-09]]: Updating reverse proxy config to the recommended one</br>as root</br>`cd /etc/nginx</br>cd site-enabled</br>vim mastodon`</br></br>search for "system"</br>added the following two headers in that block as per the release notes:</br>`add_header X-Content-Type-Options nosniff;</br> add_header Content-Security-Policy "default-src 'none'; form-action 'none'"; `</br></br>save</br>test nginx configs are valid or not (w/o running)</br>`nginx -t `</br></br>all looked good</br>`nginx: the configuration file /etc/nginx/nginx.conf syntax is ok</br>nginx: configuration file /etc/nginx/nginx.conf test is successful</br>`</br>Reload nginxinx.conf test is successful ` Reload nginx)
    • Discord Messages#sneakers.the.rat-23-09-20 02:55:44  + ([[Tech WG/Ops Diary#23-09-19]] - Upgrading … [[Tech WG/Ops Diary#23-09-19]] - Upgrading to 4.2-RC2 while trying to write the [[Upgrade Mastodon]] docs. currently doing the merge from upstream and noticing db migrations for exclusive lists failing, but not fixing now because that would put the fixes in the `glitch-soc-main` branch which is a local mirror of upstream which gets force pushed. Seems like that should happen in the `merge-upstream` branch after upstream is merged-upstream` branch after upstream is merged)
    • Tech WG/Ops Diary#sneakers.the.rat-23-09-20 02:55:44  + ([[Tech WG/Ops Diary#23-09-19]] - Upgrading … [[Tech WG/Ops Diary#23-09-19]] - Upgrading to 4.2-RC2 while trying to write the [[Upgrade Mastodon]] docs. currently doing the merge from upstream and noticing db migrations for exclusive lists failing, but not fixing now because that would put the fixes in the `glitch-soc-main` branch which is a local mirror of upstream which gets force pushed. Seems like that should happen in the `merge-upstream` branch after upstream is merged-upstream` branch after upstream is merged)
    • Tech WG/Ops Diary#mannazsci-23-10-01 07:44:40  + ([[Tech WG/Ops Diary#23-10-01]] I am ready to deploy v4.2 but I encountered a few issues while following the process mentioned in [[Upgrade_Mastodon]]. I'll update the wiki with the steps I took.)
    • Upgrade Mastodon#mannazsci-23-10-01 07:44:40  + ([[Tech WG/Ops Diary#23-10-01]] I am ready … [[Tech WG/Ops Diary#23-10-01]] I am ready to deploy v4.2 but I encountered a few issues while following the process mentioned in [[Upgrade_Mastodon]]. The glitch-soc-main branch had commits from merge-upstream even after syncing the the branch. So I created a new branch called glitch-clean-sync from glitch-soc's main branch and added protections to this branch. This let's us keep this branch clean and not merge any custom features to this branch. We'd only use the sync feature. I also tried to follow the rest of the process but it seemed a bit complicated/unclear. I've tried to simplify it in a separate section above for glitch+4.2+our instance's features. I've also created a clean and stable dev-stable branch for custom features that we add. I've added branch protections here as well and PRs will require reviews on this branch.d PRs will require reviews on this branch.)
    • Discord Messages#mannazsci-23-10-01 07:44:40  + ([[Tech WG/Ops Diary#23-10-01]] I am ready to deploy v4.2 but I encountered a few issues while following the process mentioned in [[Upgrade_Mastodon]]. I'll update the wiki with the steps I took.)
    • Tech WG/Ops Diary#sneakers.the.rat-24-02-02 01:16:50  + ([[Tech WG/Ops Diary#24-02-01]] - Patching some mysterious critical security vuln thread)
    • Discord Messages#sneakers.the.rat-24-02-02 01:16:50  + ([[Tech WG/Ops Diary#24-02-01]] - Patching some mysterious critical security vuln thread)
    • Discord Messages#sneakers.the.rat-24-02-17 22:16:31  + ([[Tech WG/Ops Diary#24-02-14]] - Patching two more security bugs thread!)
    • Tech WG/Ops Diary#sneakers.the.rat-24-02-17 22:16:31  + ([[Tech WG/Ops Diary#24-02-14]] - Patching two more security bugs thread!)
    • Accessibility#sneakers-the-rat-23-01-26 03:58:14  + (great! let me plant a bookmark on the wiki to remind me to fill in this information when I get internet at my new place & can edit it. [[Accessibility#Disabling Motion]] [[Discord#Accessibility]])
    • Discord Messages#sneakers-the-rat-23-01-26 03:58:14  + (great! let me plant a bookmark on the wiki to remind me to fill in this information when I get internet at my new place & can edit it. [[Accessibility#Disabling Motion]] [[Discord#Accessibility]])
    • Discord#sneakers-the-rat-23-01-26 03:58:14  + (great! let me plant a bookmark on the wiki to remind me to fill in this information when I get internet at my new place & can edit it. [[Accessibility#Disabling Motion]] [[Discord#Accessibility]])
    • Grants#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
    • Nested Threads#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
    • Mastodon/TODO#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
    • Discord Messages#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
    • DIY Algorithms#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
    • Mastodon/Grants#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
    • Discord Messages#sneakers-the-rat-23-03-30 04:49:04  + (ok [[Tech WG/Ops Diary#23-03-29]] … ok [[Tech WG/Ops Diary#23-03-29]]: going to pull in dev branch and deploy to tha server: https://github.com/NeuromatchAcademy/mastodon/pull/13</br></br> I thought this had fetch all replies in it but i need to rebase it and also now that we know how to write them i want to write some tests....</br>It does have [[Better Code Blocks]] in it from <@485848481995423755> : https://github.com/NeuromatchAcademy/mastodon/pull/9</br></br>wish e luckm/NeuromatchAcademy/mastodon/pull/9 wish e luck)
    • Better Code Blocks#sneakers-the-rat-23-03-30 04:49:04  + (ok [[Tech WG/Ops Diary#23-03-29]] … ok [[Tech WG/Ops Diary#23-03-29]]: going to pull in dev branch and deploy to tha server: https://github.com/NeuromatchAcademy/mastodon/pull/13</br></br> I thought this had fetch all replies in it but i need to rebase it and also now that we know how to write them i want to write some tests....</br>It does have [[Better Code Blocks]] in it from <@485848481995423755> : https://github.com/NeuromatchAcademy/mastodon/pull/9</br></br>wish e luckm/NeuromatchAcademy/mastodon/pull/9 wish e luck)
    • Tech WG/Ops Diary#sneakers-the-rat-23-03-30 04:49:04  + (ok [[Tech WG/Ops Diary#23-03-29]] … ok [[Tech WG/Ops Diary#23-03-29]]: going to pull in dev branch and deploy to tha server: https://github.com/NeuromatchAcademy/mastodon/pull/13</br></br> I thought this had fetch all replies in it but i need to rebase it and also now that we know how to write them i want to write some tests....</br>It does have [[Better Code Blocks]] in it from <@485848481995423755> : https://github.com/NeuromatchAcademy/mastodon/pull/9</br></br>wish e luckm/NeuromatchAcademy/mastodon/pull/9 wish e luck)
    • WikiBot#sneakers-the-rat-23-05-20 08:29:54  + (ok [[Tech_WG/Ops_Diary#23-05-19]] … ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
    • Tech WG/Ops Diary#sneakers-the-rat-23-05-20 08:29:54  + (ok [[Tech_WG/Ops_Diary#23-05-19]] … ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
    • Discord Messages#sneakers-the-rat-23-05-20 08:29:54  + (ok [[Tech_WG/Ops_Diary#23-05-19]] … ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
    • Discord Messages#sneakers.the.rat-24-01-17 10:58:31  + (ok i'd like to raise an olde idea again an … ok i'd like to raise an olde idea again and that is having an instancewide [[Sticky Posts]] to supplement announcements to be able to make discussions that are intended to lead to a proposal more visible to the instance. loomio and discord merely by virtue of being separate platforms are less visible, so let's try and do a lil bridging of mediums.</br></br>here's one idea of what that might look like:</br>v1</br>- currently we have a [[Discussions]] stage in governance docs (https://wiki.neuromatch.social/Governance#Discussions) we can make that a more formal definition and say that a discussion intended to lead to a proposal is a stickied post.</br>- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post</br>- sticky posts come from an autofollowed @ discussions account</br>- ... are local only posts</br>- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed</br>- ... have a "minimize" button that is persistent across sessions, so once you minimize a sticky post it is hidden but still visible, I'm thinking like a 1em bar across the top of the feed</br></br>questions: </br>- can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'</br>- should stickies have a time limit? or just a mechanism to close them in governance process?</br></br>v2</br>a) The threading interface on the web interface is awful, </br>b) it would be nice to be able to show a title on a minimized sticky post</br>c) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike way</br>so</br>- posts can have titles</br>- titles are declared with a special "title" field in the web ui</br>- or with a first line beginning with a # from other clients, a la markdown</br>- replies with titles can be minimized too</br>- replies with titles are sorted first (bc they can be minimized)</br></br>[[Hacks]][[Hacks]])
    • Hacks#sneakers.the.rat-24-01-17 10:58:31  + (ok i'd like to raise an olde idea again an … ok i'd like to raise an olde idea again and that is having an instancewide [[Sticky Posts]] to supplement announcements to be able to make discussions that are intended to lead to a proposal more visible to the instance. loomio and discord merely by virtue of being separate platforms are less visible, so let's try and do a lil bridging of mediums.</br></br>here's one idea of what that might look like:</br>v1</br>- currently we have a [[Discussions]] stage in governance docs (https://wiki.neuromatch.social/Governance#Discussions) we can make that a more formal definition and say that a discussion intended to lead to a proposal is a stickied post.</br>- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post</br>- sticky posts come from an autofollowed @ discussions account</br>- ... are local only posts</br>- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed</br>- ... have a "minimize" button that is persistent across sessions, so once you minimize a sticky post it is hidden but still visible, I'm thinking like a 1em bar across the top of the feed</br></br>questions: </br>- can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'</br>- should stickies have a time limit? or just a mechanism to close them in governance process?</br></br>v2</br>a) The threading interface on the web interface is awful, </br>b) it would be nice to be able to show a title on a minimized sticky post</br>c) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike way</br>so</br>- posts can have titles</br>- titles are declared with a special "title" field in the web ui</br>- or with a first line beginning with a # from other clients, a la markdown</br>- replies with titles can be minimized too</br>- replies with titles are sorted first (bc they can be minimized)</br></br>[[Hacks]][[Hacks]])
    • Discussions#sneakers.the.rat-24-01-17 10:58:31  + (ok i'd like to raise an olde idea again an … ok i'd like to raise an olde idea again and that is having an instancewide [[Sticky Posts]] to supplement announcements to be able to make discussions that are intended to lead to a proposal more visible to the instance. loomio and discord merely by virtue of being separate platforms are less visible, so let's try and do a lil bridging of mediums.</br></br>here's one idea of what that might look like:</br>v1</br>- currently we have a [[Discussions]] stage in governance docs (https://wiki.neuromatch.social/Governance#Discussions) we can make that a more formal definition and say that a discussion intended to lead to a proposal is a stickied post.</br>- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post</br>- sticky posts come from an autofollowed @ discussions account</br>- ... are local only posts</br>- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed</br>- ... have a "minimize" button that is persistent across sessions, so once you minimize a sticky post it is hidden but still visible, I'm thinking like a 1em bar across the top of the feed</br></br>questions: </br>- can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'</br>- should stickies have a time limit? or just a mechanism to close them in governance process?</br></br>v2</br>a) The threading interface on the web interface is awful, </br>b) it would be nice to be able to show a title on a minimized sticky post</br>c) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike way</br>so</br>- posts can have titles</br>- titles are declared with a special "title" field in the web ui</br>- or with a first line beginning with a # from other clients, a la markdown</br>- replies with titles can be minimized too</br>- replies with titles are sorted first (bc they can be minimized)</br></br>[[Hacks]][[Hacks]])
    • Lessons We Gone And Learned From Maintaining A Fork Of A Fork#sneakers.the.rat-24-02-16 23:01:41  + (ok so they refactored all the css, and it … ok so they refactored all the css, and it was pretty hard to track down what in the heck was changed, so here is another [[Lessons We Gone And Learned From Maintaining A Fork Of A Fork]] - patching is good, editing in place can be fragile. i moved the custom styles from better code blocks and expanded status previews to their own set of stub scss files that then get imported at the end of the scss index, so they should override conflicting rules set previously. that keeps them nice and separate and survivable in the case of big refactorings. this is similar to the "flavours" system which takes whatever isn't overridden from base masto. i can't run the dev server rn bc my brother is in town but since these are just css changes we can uh test in prod i think</br>https://github.com/NeuromatchAcademy/mastodon/commit/8e54a6bf891ff855104225032dd9ccfb0163aceat/8e54a6bf891ff855104225032dd9ccfb0163acea)
    • Discord Messages#sneakers.the.rat-24-02-16 23:01:41  + (ok so they refactored all the css, and it … ok so they refactored all the css, and it was pretty hard to track down what in the heck was changed, so here is another [[Lessons We Gone And Learned From Maintaining A Fork Of A Fork]] - patching is good, editing in place can be fragile. i moved the custom styles from better code blocks and expanded status previews to their own set of stub scss files that then get imported at the end of the scss index, so they should override conflicting rules set previously. that keeps them nice and separate and survivable in the case of big refactorings. this is similar to the "flavours" system which takes whatever isn't overridden from base masto. i can't run the dev server rn bc my brother is in town but since these are just css changes we can uh test in prod i think</br>https://github.com/NeuromatchAcademy/mastodon/commit/8e54a6bf891ff855104225032dd9ccfb0163aceat/8e54a6bf891ff855104225032dd9ccfb0163acea)
    • WikiBot#sneakers-the-rat-22-12-29 00:22:33  + (the DOI thing I think will only take an ho … the DOI thing I think will only take an hour or two more, and then yeah will be adapting some of the [[WikiBot]] code that runs on this discord already to do an agora-like thing. I've talked to flancian about this as well a bunch of times, unifying the agora bots and making a general framework for that kind of cross platform linkingrk for that kind of cross platform linking)
    • Tech WG#sneakers.the.rat-23-07-04 21:16:38  + (yes agreed we should make a wiki guide to … yes agreed we should make a wiki guide to updating the instance. </br></br>I need to log off for the day bc am visiting friends, but in short it's</br>- start backup in linode (reminder to also set you up with an account there and add that to [[Tech WG#TODO]] [[Tech WG/Onboarding]] docs</br>- do all the git work that we're familiar with to prepare the new deploy</br>- check upgrade notes, usually on base masto release notes, to see if anything out of the ordinary is required</br>- pull down new changes to server</br>- potentially recompile yarn assets</br>- potentially run database migrations</br>- restart mastodon-* services</br></br>and that's usually it. downtime is usually on the order of a few seconds (and we could explore how to make that zero, I think that's how the pros do it with like multiple servers)the pros do it with like multiple servers))
    • Tech WG/Onboarding#sneakers.the.rat-23-07-04 21:16:38  + (yes agreed we should make a wiki guide to … yes agreed we should make a wiki guide to updating the instance. </br></br>I need to log off for the day bc am visiting friends, but in short it's</br>- start backup in linode (reminder to also set you up with an account there and add that to [[Tech WG#TODO]] [[Tech WG/Onboarding]] docs</br>- do all the git work that we're familiar with to prepare the new deploy</br>- check upgrade notes, usually on base masto release notes, to see if anything out of the ordinary is required</br>- pull down new changes to server</br>- potentially recompile yarn assets</br>- potentially run database migrations</br>- restart mastodon-* services</br></br>and that's usually it. downtime is usually on the order of a few seconds (and we could explore how to make that zero, I think that's how the pros do it with like multiple servers)the pros do it with like multiple servers))
    • Discord Messages#sneakers.the.rat-23-07-04 21:16:38  + (yes agreed we should make a wiki guide to … yes agreed we should make a wiki guide to updating the instance. </br></br>I need to log off for the day bc am visiting friends, but in short it's</br>- start backup in linode (reminder to also set you up with an account there and add that to [[Tech WG#TODO]] [[Tech WG/Onboarding]] docs</br>- do all the git work that we're familiar with to prepare the new deploy</br>- check upgrade notes, usually on base masto release notes, to see if anything out of the ordinary is required</br>- pull down new changes to server</br>- potentially recompile yarn assets</br>- potentially run database migrations</br>- restart mastodon-* services</br></br>and that's usually it. downtime is usually on the order of a few seconds (and we could explore how to make that zero, I think that's how the pros do it with like multiple servers)the pros do it with like multiple servers))
    Retrieved from "https://wiki.neuromatch.social/Special:SearchByProperty/:Contains-20text/-5B-5BTech-20WG-2FOps-20Diary-2323-2D01-2D20-20Installed-20NTP-20to-20sync-20system-20clock-5D-5D-20This-20was-20done-20to-20resolve-20a-202FA-20issue-20involving-20Authy-20(a-20TOTP-20app)-20https:-2F-2Fdiscord.com-2Fchannels-2F1049136631065628772-2F1049184335514828860-2F1065990577381974067"