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 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]]: - Fix semantic wikilinks in the [[WikiBot#TODO]], - 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]]: - Fix semantic wikilinks in the [[WikiBot#TODO]], - 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-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-18 21:14:38 + ([[Mastodon/Tech WG#TODO]]: why are follow buttons not present for all instances for user accounts on the notification feed?)
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 oneas root`cd /etc/nginxcd site-enabledvim mastodon`search for "system"added the following two headers in that block as per the release notes:`add_header X-Content-Type-Options nosniff; add_header Content-Security-Policy "default-src 'none'; form-action 'none'"; `savetest nginx configs are valid or not (w/o running)`nginx -t `all looked good`nginx: the configuration file /etc/nginx/nginx.conf syntax is oknginx: configuration file /etc/nginx/nginx.conf test is successful`Reload nginxinx.conf test is successful ` Reload nginx)
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 oneas rootcd /etc/nginxcd sites-enabledvim mastodonsearch for "system"added the following two headers in that block as per the release notes:`add_header X-Content-Type-Options nosniff; add_header Content-Security-Policy "default-src 'none'; form-action 'none'";`savetest nginx configs are valid or not (w/o running)`nginx -t`all looked good`nginx: the configuration file /etc/nginx/nginx.conf syntax is oknginx: configuration file /etc/nginx/nginx.conf test is successful`Reload nginx`nginx reload`s successful` Reload nginx `nginx reload`)
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.)
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]])
WikiBot Checkup#sneakers-the-rat-23-04-27 04:17:50 + (sidenote I just looked at the channel member list and holy crap wikibot are you still alive [[WikiBot Checkup]])
Discord Messages#sneakers-the-rat-23-04-27 04:17:50 + (sidenote I just looked at the channel member list and holy crap wikibot are you still alive [[WikiBot Checkup]])
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)
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-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)
Camel Case#sneakers-the-rat-22-12-29 00:27:20 + (we've talked about this as well, being abl … we've talked about this as well, being able to make the bot more granularly opt-in, as well as make some simple degeneracy rules like #CamelCase == [[Camel Case]] (actually proposed that probably to no result in masto here: https://github.com/mastodon/mastodon/issues/19992#issuecomment-1363496984 )don/issues/19992#issuecomment-1363496984 ))
Discord Messages#sneakers-the-rat-22-12-29 00:27:20 + (we've talked about this as well, being abl … we've talked about this as well, being able to make the bot more granularly opt-in, as well as make some simple degeneracy rules like #CamelCase == [[Camel Case]] (actually proposed that probably to no result in masto here: https://github.com/mastodon/mastodon/issues/19992#issuecomment-1363496984 )don/issues/19992#issuecomment-1363496984 ))
Mastodon updates#mannaz-23-07-04 20:31:28 + (worst case scenario -- ppl get a break from scrolling our local TL for a while 😂 🙈 writing here in caps so that we [[Mastodon updates]] REMEMBER TO TAKE A BACKUP BEFORE starting.. we should have a rocess of the typical steps to follow)
Discord Messages#mannaz-23-07-04 20:31:28 + (worst case scenario -- ppl get a break from scrolling our local TL for a while 😂 🙈 writing here in caps so that we [[Mastodon updates]] REMEMBER TO TAKE A BACKUP BEFORE starting.. we should have a rocess of the typical steps to follow)
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))
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))
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.)

Autofollow#sneakers-the-rat-22-12-22 18:46:31 + ([[Autofollow]]: Make all new accounts follow a a comma-separated list of account handles given in the .env file 🙂)

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.)
Code Review#sneakers-the-rat-23-01-02 22:39:57 + (<@863052667857534996> do y'all have … <@863052667857534996> do y'all have anything like this for the pyopensci stuff? like a "make a feature branch off dev, make a pull request back to dev, during a code review, look for xyz" then we will also need stuff like how to do the merge and update the instance [[Hack Merging Policy]] [[Updating Mastodon]] [[Code Review]][[Code Review]])
Discord Messages#sneakers-the-rat-23-01-02 22:39:57 + (<@863052667857534996> do y'all have … <@863052667857534996> do y'all have anything like this for the pyopensci stuff? like a "make a feature branch off dev, make a pull request back to dev, during a code review, look for xyz" then we will also need stuff like how to do the merge and update the instance [[Hack Merging Policy]] [[Updating Mastodon]] [[Code Review]][[Code Review]])
Hack Merging Policy#sneakers-the-rat-23-01-02 22:39:57 + (<@863052667857534996> do y'all have … <@863052667857534996> do y'all have anything like this for the pyopensci stuff? like a "make a feature branch off dev, make a pull request back to dev, during a code review, look for xyz" then we will also need stuff like how to do the merge and update the instance [[Hack Merging Policy]] [[Updating Mastodon]] [[Code Review]][[Code Review]])
Updating Mastodon#sneakers-the-rat-23-01-02 22:39:57 + (<@863052667857534996> do y'all have … <@863052667857534996> do y'all have anything like this for the pyopensci stuff? like a "make a feature branch off dev, make a pull request back to dev, during a code review, look for xyz" then we will also need stuff like how to do the merge and update the instance [[Hack Merging Policy]] [[Updating Mastodon]] [[Code Review]][[Code Review]])
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.)
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.)
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.)
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]])
Tech WG/Ops Diary#sneakers-the-rat-22-12-25 01:59:05 + (OK [[Tech WG/Ops Diary#22-12-24]] … OK[[Tech WG/Ops Diary#22-12-24]] going to pull in a few upgrades:https://github.com/NeuromatchAcademy/mastodon/pull/7* Mathjax* Larger Post Previews* Default false notifications for new follows* Autofollow accountsAnd 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[[Tech WG/Ops Diary#22-12-24]] going to pull in a few upgrades:https://github.com/NeuromatchAcademy/mastodon/pull/7* Mathjax* Larger Post Previews* Default false notifications for new follows* Autofollow accountsAnd 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: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))
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 hackingtagging the neuromatch ppl I know are on the discord <@540104559079456770> <@1050459047582781480> <@215274946560131074> <@651480296415297553> and who else sorry I don't have a list[[Mastodon and Neuromatch]][[Neuromatch and Mastodon]] (idk lol I'll just redirect one page to another)[[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 hackingtagging the neuromatch ppl I know are on the discord <@540104559079456770> <@1050459047582781480> <@215274946560131074> <@651480296415297553> and who else sorry I don't have a list[[Mastodon and Neuromatch]][[Neuromatch and Mastodon]] (idk lol I'll just redirect one page to another)[[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 hackingtagging the neuromatch ppl I know are on the discord <@540104559079456770> <@1050459047582781480> <@215274946560131074> <@651480296415297553> and who else sorry I don't have a list[[Mastodon and Neuromatch]][[Neuromatch and Mastodon]] (idk lol I'll just redirect one page to another)[[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 hackingtagging the neuromatch ppl I know are on the discord <@540104559079456770> <@1050459047582781480> <@215274946560131074> <@651480296415297553> and who else sorry I don't have a list[[Mastodon and Neuromatch]][[Neuromatch and Mastodon]] (idk lol I'll just redirect one page to another)[[Infrastructure]][[Infrastructure]])
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 hackingtagging the neuromatch ppl I know are on the discord <@540104559079456770> <@1050459047582781480> <@215274946560131074> <@651480296415297553> and who else sorry I don't have a list[[Mastodon and Neuromatch]][[Neuromatch and Mastodon]] (idk lol I'll just redirect one page to another)[[Infrastructure]][[Infrastructure]])