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.

List of results

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]])
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]])
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.[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
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.[[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.[[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.[[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.[[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.[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
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)
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)
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)
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.here's one idea of what that might look like:v1- 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.- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post- sticky posts come from an autofollowed @ discussions account- ... are local only posts- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed- ... 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 feedquestions: - can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'- should stickies have a time limit? or just a mechanism to close them in governance process?v2a) The threading interface on the web interface is awful, b) it would be nice to be able to show a title on a minimized sticky postc) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike wayso- posts can have titles- titles are declared with a special "title" field in the web ui- or with a first line beginning with a # from other clients, a la markdown- replies with titles can be minimized too- replies with titles are sorted first (bc they can be minimized)[[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.here's one idea of what that might look like:v1- 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.- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post- sticky posts come from an autofollowed @ discussions account- ... are local only posts- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed- ... 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 feedquestions: - can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'- should stickies have a time limit? or just a mechanism to close them in governance process?v2a) The threading interface on the web interface is awful, b) it would be nice to be able to show a title on a minimized sticky postc) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike wayso- posts can have titles- titles are declared with a special "title" field in the web ui- or with a first line beginning with a # from other clients, a la markdown- replies with titles can be minimized too- replies with titles are sorted first (bc they can be minimized)[[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.here's one idea of what that might look like:v1- 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.- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post- sticky posts come from an autofollowed @ discussions account- ... are local only posts- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed- ... 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 feedquestions: - can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'- should stickies have a time limit? or just a mechanism to close them in governance process?v2a) The threading interface on the web interface is awful, b) it would be nice to be able to show a title on a minimized sticky postc) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike wayso- posts can have titles- titles are declared with a special "title" field in the web ui- or with a first line beginning with a # from other clients, a la markdown- replies with titles can be minimized too- replies with titles are sorted first (bc they can be minimized)[[Hacks]][[Hacks]])
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[[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-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[[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-22-12-12 12:03:08 + (this week is a good week to finish our rul … this week is a good week to finish our rules, instance description, invite statement and make a mass coordinated announcement ♥️♥️♥️😘😘😘in cooperation, towards information liberation!!!!!pls join us in conversations in <#1050561894752198706> if you are so inclined 🙂[[Mastodon/Seed Council#TODO]]https://open.spotify.com/track/0fEasSvs63eKApKfYbi2uDTODO]] https://open.spotify.com/track/0fEasSvs63eKApKfYbi2uD)
Mastodon/Seed Council#sneakers-the-rat-22-12-12 12:03:08 + (this week is a good week to finish our rul … this week is a good week to finish our rules, instance description, invite statement and make a mass coordinated announcement ♥️♥️♥️😘😘😘in cooperation, towards information liberation!!!!!pls join us in conversations in <#1050561894752198706> if you are so inclined 🙂[[Mastodon/Seed Council#TODO]]https://open.spotify.com/track/0fEasSvs63eKApKfYbi2uDTODO]] https://open.spotify.com/track/0fEasSvs63eKApKfYbi2uD)
Discord Messages#sneakers-the-rat-22-12-09 12:28:39 + (up to y'all but all I'll say is we did indeed already start one and [[The Wiki Is Happening]] feat. [[The Wiki Waits For No One]] [[WikiParables]])
The Wiki Waits For No One#sneakers-the-rat-22-12-09 12:28:39 + (up to y'all but all I'll say is we did indeed already start one and [[The Wiki Is Happening]] feat. [[The Wiki Waits For No One]] [[WikiParables]])
The Wiki Is Happening#sneakers-the-rat-22-12-09 12:28:39 + (up to y'all but all I'll say is we did indeed already start one and [[The Wiki Is Happening]] feat. [[The Wiki Waits For No One]] [[WikiParables]])
WikiParables#sneakers-the-rat-22-12-09 12:28:39 + (up to y'all but all I'll say is we did indeed already start one and [[The Wiki Is Happening]] feat. [[The Wiki Waits For No One]] [[WikiParables]])
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. I need to log off for the day bc am visiting friends, but in short it's- 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- do all the git work that we're familiar with to prepare the new deploy- check upgrade notes, usually on base masto release notes, to see if anything out of the ordinary is required- pull down new changes to server- potentially recompile yarn assets- potentially run database migrations- restart mastodon-* servicesand 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. I need to log off for the day bc am visiting friends, but in short it's- 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- do all the git work that we're familiar with to prepare the new deploy- check upgrade notes, usually on base masto release notes, to see if anything out of the ordinary is required- pull down new changes to server- potentially recompile yarn assets- potentially run database migrations- restart mastodon-* servicesand 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. I need to log off for the day bc am visiting friends, but in short it's- 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- do all the git work that we're familiar with to prepare the new deploy- check upgrade notes, usually on base masto release notes, to see if anything out of the ordinary is required- pull down new changes to server- potentially recompile yarn assets- potentially run database migrations- restart mastodon-* servicesand 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))
WikiBot#sneakers-the-rat-22-12-29 00:24:51 + (yes! this is definitely the idea with the … yes! this is definitely the idea with the [[WikiBot]]: capture links in situ for reminders and backlinks, but then have them be part of the wiki that can be curated down rather than just being the raw content of the post forever. Need to fix up the css for representing posts on the wiki to make them a little less obtrusive, but then yeah they can be hidden or collapsed once the page matures.hidden or collapsed once the page matures.)

Discord Messages#sneakers-the-rat-22-12-09 12:37:58 + ([[Wiki/TODO#Onboarding]] Document account migration process, re: https://fediscience.org/@dbarack/109483724167917771)
Wiki/TODO#sneakers-the-rat-22-12-09 12:37:58 + ([[Wiki/TODO#Onboarding]] Document account migration process, re: https://fediscience.org/@dbarack/109483724167917771)

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.- 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.- 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.what else? listing the concerns, we could then see how each impacts a decision to limit/defederate based on what each decision does. 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.)
Exclusive Lists#sneakers-the-rat-23-03-18 21:48:09 + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: [[Mastodon/Tests]][[Mastodon/Tech WG]][[Exclusive Lists]][[Ruby Spec]][[Ruby]]spec for home feed:https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rbfor public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rbthat gives more examples on how feeds are supposed to be filteredtag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rbin case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rband so on 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`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.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.jsand 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.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: [[Mastodon/Tests]][[Mastodon/Tech WG]][[Exclusive Lists]][[Ruby Spec]][[Ruby]]spec for home feed:https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rbfor public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rbthat gives more examples on how feeds are supposed to be filteredtag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rbin case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rband so on 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`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.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.jsand 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.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: [[Mastodon/Tests]][[Mastodon/Tech WG]][[Exclusive Lists]][[Ruby Spec]][[Ruby]]spec for home feed:https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rbfor public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rbthat gives more examples on how feeds are supposed to be filteredtag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rbin case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rband so on 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`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.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.jsand 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.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: [[Mastodon/Tests]][[Mastodon/Tech WG]][[Exclusive Lists]][[Ruby Spec]][[Ruby]]spec for home feed:https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rbfor public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rbthat gives more examples on how feeds are supposed to be filteredtag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rbin case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rband so on 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`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.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.jsand 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.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: [[Mastodon/Tests]][[Mastodon/Tech WG]][[Exclusive Lists]][[Ruby Spec]][[Ruby]]spec for home feed:https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rbfor public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rbthat gives more examples on how feeds are supposed to be filteredtag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rbin case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rband so on 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`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.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.jsand 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.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: [[Mastodon/Tests]][[Mastodon/Tech WG]][[Exclusive Lists]][[Ruby Spec]][[Ruby]]spec for home feed:https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rbfor public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rbthat gives more examples on how feeds are supposed to be filteredtag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rbin case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rband so on 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`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.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.jsand 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.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#VotingYes, 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. 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). 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.)
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#VotingYes, 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. 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). 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.)
TODO#sneakers.the.rat-24-01-20 05:20:06 + (Also that reminds me that I did get the announcement notif but the interface opened starting with the first announcement not the most recent one so [[TODO]])
Discord Messages#sneakers.the.rat-24-01-20 05:20:06 + (Also that reminds me that I did get the announcement notif but the interface opened starting with the first announcement not the most recent one so [[TODO]])
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)
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: - $0/mo for students/people making <$50k annually- $1/mo for postdocs/people making <$75k annually- $5/mo for PIs/people making >$75k annuallythough 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. 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.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.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)<@215274946560131074> [[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: - $0/mo for students/people making <$50k annually- $1/mo for postdocs/people making <$75k annually- $5/mo for PIs/people making >$75k annuallythough 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. 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.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.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)<@215274946560131074> [[Mastodon/Finances]][[Mastodon/Finances]])
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: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.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/Docsthen 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).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(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))
Wiki/TODO#mstimberg-22-12-09 20:16:00 + (Re [[Wiki/TODO#Onboarding]]: I migrated earlier today and took some notes, happy to add them to the wiki – I'd need someone to approve my account (`mstimberg`), though 😊)
Discord Messages#mstimberg-22-12-09 20:16:00 + (Re [[Wiki/TODO#Onboarding]]: I migrated earlier today and took some notes, happy to add them to the wiki – I'd need someone to approve my account (`mstimberg`), though 😊)
TODO#sneakers-the-rat-22-12-09 11:52:48 + (So anyway [[TODO]] Document the [[WikiBot]])
Social WG/Responsibilities#mannaz-23-07-07 00:50:28 + (Thank you El and welcome onboard!! woohoo! … Thank you El and welcome onboard!! woohoo!! 🥳 ❤️ 💚 💜 💙 🧡 [[Social WG/Responsibilities]] continued: with great power comes great responsibility :) 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 :) )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>) 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. 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!! 🥳 ❤️ 💚 💜 💙 🧡 [[Social WG/Responsibilities]] continued: with great power comes great responsibility :) 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 :) )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>) 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. 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 ❤️ [[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 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)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 ❤️ [[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 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)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! > forum mode! one thing I would love is for NMS to be a place where non-neuroscientists can come and ask questions of neuroscientists...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! 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). 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?)