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-04-25]]: restarted systems services as we were hitting swap limits https://neuromatch.social/@manisha/110259466647197417". Since there have been only a few results, also nearby values are displayed.

Showing below up to 11 results starting with #1.

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

    

List of results

  • 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-22-12-26 23:33:51  + (ok here's [[Fetch All Replies]]: https://neuromatch.social/@jonny/109582537808504261)
  • Fetch All Replies#sneakers-the-rat-22-12-26 23:33:51  + (ok here's [[Fetch All Replies]]: https://neuromatch.social/@jonny/109582537808504261)
  • 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]])
  • 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]])
  • 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]])
  • Discord Messages#sneakers-the-rat-22-12-21 17:49:16  + (so! the "local" feed is the one that shows … so! the "local" feed is the one that shows all the toots from our instance, the "federated" feed shows all toots from everyone that everyone on the instance follow. "local-only toots" are a special feature of glitch-soc where you can make your post *only* visible to the other members of the instance (in base masto you can only limit to mentioned accounts or followers). Local feed also will show you boosts from people on our instance, I'm not sure if there's a way to turn that off but if there isn't there should be bc that would be nice</br></br>[[Mastodon/Social WG#TODO]]: guides on how the different [[Mastodon/Feeds]] and [[Mastodon/Post Visibility]] work[[Mastodon/Post Visibility]] work)
  • Mastodon/Feeds#sneakers-the-rat-22-12-21 17:49:16  + (so! the "local" feed is the one that shows … so! the "local" feed is the one that shows all the toots from our instance, the "federated" feed shows all toots from everyone that everyone on the instance follow. "local-only toots" are a special feature of glitch-soc where you can make your post *only* visible to the other members of the instance (in base masto you can only limit to mentioned accounts or followers). Local feed also will show you boosts from people on our instance, I'm not sure if there's a way to turn that off but if there isn't there should be bc that would be nice</br></br>[[Mastodon/Social WG#TODO]]: guides on how the different [[Mastodon/Feeds]] and [[Mastodon/Post Visibility]] work[[Mastodon/Post Visibility]] work)
  • 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))
  • 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))
  • 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))
  • Discord Messages#sneakers.the.rat-23-07-07 18:51:01  + (- solidarity with the fedi: to survive thi … - solidarity with the fedi: to survive this and future attempts at corporate capture, it is important to act together. many instances have already committed to defederation, and even if it is symbolic, symbols are important.</br></br>- being defederated by other instances: we are currently in the good graces of some very protective instances through prior social ties and our promise to be a good actor in the space, these include instances with many leftists, queer people, and others that would likely defederate from us if we were to federate with meta. this would put NMS in a more homogeneous, corporate nice space in the fedi.</br></br>- communication with threads users: some people probably want to communicate with some threads users, and this might cause dual accounts, as you say. defederation would potentially split ties. I will hold my thoughts on this for now since I'm just trying to list the relevant factors.</br></br>what else? listing the concerns, we could then see how each impacts a decision to limit/defederate based on what each decision does. </br></br>I am traveling and AFK until Monday, but I think it would also be good to make a [[Defederation from Meta]] wiki page to keep more organized notes. forgot to tag the previous post.ed notes. forgot to tag the previous post.)
  • 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 ❤️ 🙏)
  • 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.)
  • 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.)
  • 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.)
Retrieved from "https://wiki.neuromatch.social/Special:SearchByProperty/:Contains-20text/-5B-5BTech-20WG-2FOps-20Diary-2323-2D04-2D25-5D-5D:-20restarted-20systems-20services-20as-20we-20were-20hitting-20swap-20limits-20https:-2F-2Fneuromatch.social-2F@manisha-2F110259466647197417"