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

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]])
Discord Messages#sneakers-the-rat-23-03-30 04:49:04 + (ok [[Tech WG/Ops Diary#23-03-29]] … ok [[Tech WG/Ops Diary#23-03-29]]: going to pull in dev branch and deploy to tha server: https://github.com/NeuromatchAcademy/mastodon/pull/13 I thought this had fetch all replies in it but i need to rebase it and also now that we know how to write them i want to write some tests....It does have [[Better Code Blocks]] in it from <@485848481995423755> : https://github.com/NeuromatchAcademy/mastodon/pull/9wish e luckm/NeuromatchAcademy/mastodon/pull/9 wish e luck)
Tech WG/Ops Diary#sneakers-the-rat-23-03-30 04:49:04 + (ok [[Tech WG/Ops Diary#23-03-29]] … ok [[Tech WG/Ops Diary#23-03-29]]: going to pull in dev branch and deploy to tha server: https://github.com/NeuromatchAcademy/mastodon/pull/13 I thought this had fetch all replies in it but i need to rebase it and also now that we know how to write them i want to write some tests....It does have [[Better Code Blocks]] in it from <@485848481995423755> : https://github.com/NeuromatchAcademy/mastodon/pull/9wish e luckm/NeuromatchAcademy/mastodon/pull/9 wish e luck)
Better Code Blocks#sneakers-the-rat-23-03-30 04:49:04 + (ok [[Tech WG/Ops Diary#23-03-29]] … ok [[Tech WG/Ops Diary#23-03-29]]: going to pull in dev branch and deploy to tha server: https://github.com/NeuromatchAcademy/mastodon/pull/13 I thought this had fetch all replies in it but i need to rebase it and also now that we know how to write them i want to write some tests....It does have [[Better Code Blocks]] in it from <@485848481995423755> : https://github.com/NeuromatchAcademy/mastodon/pull/9wish e luckm/NeuromatchAcademy/mastodon/pull/9 wish e luck)
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)
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)
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]])
Lessons We Gone And Learned From Maintaining A Fork Of A Fork#sneakers.the.rat-24-02-16 23:01:41 + (ok so they refactored all the css, and it … ok so they refactored all the css, and it was pretty hard to track down what in the heck was changed, so here is another [[Lessons We Gone And Learned From Maintaining A Fork Of A Fork]] - patching is good, editing in place can be fragile. i moved the custom styles from better code blocks and expanded status previews to their own set of stub scss files that then get imported at the end of the scss index, so they should override conflicting rules set previously. that keeps them nice and separate and survivable in the case of big refactorings. this is similar to the "flavours" system which takes whatever isn't overridden from base masto. i can't run the dev server rn bc my brother is in town but since these are just css changes we can uh test in prod i thinkhttps://github.com/NeuromatchAcademy/mastodon/commit/8e54a6bf891ff855104225032dd9ccfb0163aceat/8e54a6bf891ff855104225032dd9ccfb0163acea)
Discord Messages#sneakers.the.rat-24-02-16 23:01:41 + (ok so they refactored all the css, and it … ok so they refactored all the css, and it was pretty hard to track down what in the heck was changed, so here is another [[Lessons We Gone And Learned From Maintaining A Fork Of A Fork]] - patching is good, editing in place can be fragile. i moved the custom styles from better code blocks and expanded status previews to their own set of stub scss files that then get imported at the end of the scss index, so they should override conflicting rules set previously. that keeps them nice and separate and survivable in the case of big refactorings. this is similar to the "flavours" system which takes whatever isn't overridden from base masto. i can't run the dev server rn bc my brother is in town but since these are just css changes we can uh test in prod i thinkhttps://github.com/NeuromatchAcademy/mastodon/commit/8e54a6bf891ff855104225032dd9ccfb0163aceat/8e54a6bf891ff855104225032dd9ccfb0163acea)
Stoplight#sneakers.the.rat-24-01-09 04:53:38 + (so re: [[Stoplight]] … so re: [[Stoplight]] and [[Cooldown]]s, [[Sidekiq#Cooldown]] tries to deliver something 16 times ( https://github.com/NeuromatchAcademy/mastodon/blob/eb24c0ad07c4137517e6bd37ebcc99d6e2b86797/app/workers/activitypub/delivery_worker.rb#L11 )the delay rises exponentially (^4) with each retry. So eg by the 10th retry we're delaying an average of 208 minutes, and by 16 we're at 1365 (22 hours). That delay uses sidekiq's `sidekiq_retry_in` method, which applies to each delivery task (ie. each status we're trying to push), but there is also an additional control flow tool Stoplight ( https://blog.bolshakov.dev/stoplight/ ) that applies per inbox URL (rather than per job). You start in a good (green) state. Each failure counts towards a threshold (10), after which it halts all jobs matching that inbox (red). After the cooldown period (60 seconds) it flips into a "yellow" state: if the next job succeeds, it flips back to green. If it fails, it goes immediately back to red. That configuration seems sorta... pointless to me? if it only kicks in after 10 failures, then it'll only be halting after really long delays, right? it seems like that should be a high threshold with like a really long cooldown to me - if we haven't been able to deliver like 200 messages, then cooldown for like 6 hours (i'm not sure if receiving a message clears the stoplight) receiving a message clears the stoplight))
Cooldown#sneakers.the.rat-24-01-09 04:53:38 + (so re: [[Stoplight]] … so re: [[Stoplight]] and [[Cooldown]]s, [[Sidekiq#Cooldown]] tries to deliver something 16 times ( https://github.com/NeuromatchAcademy/mastodon/blob/eb24c0ad07c4137517e6bd37ebcc99d6e2b86797/app/workers/activitypub/delivery_worker.rb#L11 )the delay rises exponentially (^4) with each retry. So eg by the 10th retry we're delaying an average of 208 minutes, and by 16 we're at 1365 (22 hours). That delay uses sidekiq's `sidekiq_retry_in` method, which applies to each delivery task (ie. each status we're trying to push), but there is also an additional control flow tool Stoplight ( https://blog.bolshakov.dev/stoplight/ ) that applies per inbox URL (rather than per job). You start in a good (green) state. Each failure counts towards a threshold (10), after which it halts all jobs matching that inbox (red). After the cooldown period (60 seconds) it flips into a "yellow" state: if the next job succeeds, it flips back to green. If it fails, it goes immediately back to red. That configuration seems sorta... pointless to me? if it only kicks in after 10 failures, then it'll only be halting after really long delays, right? it seems like that should be a high threshold with like a really long cooldown to me - if we haven't been able to deliver like 200 messages, then cooldown for like 6 hours (i'm not sure if receiving a message clears the stoplight) receiving a message clears the stoplight))
Sidekiq#sneakers.the.rat-24-01-09 04:53:38 + (so re: [[Stoplight]] … so re: [[Stoplight]] and [[Cooldown]]s, [[Sidekiq#Cooldown]] tries to deliver something 16 times ( https://github.com/NeuromatchAcademy/mastodon/blob/eb24c0ad07c4137517e6bd37ebcc99d6e2b86797/app/workers/activitypub/delivery_worker.rb#L11 )the delay rises exponentially (^4) with each retry. So eg by the 10th retry we're delaying an average of 208 minutes, and by 16 we're at 1365 (22 hours). That delay uses sidekiq's `sidekiq_retry_in` method, which applies to each delivery task (ie. each status we're trying to push), but there is also an additional control flow tool Stoplight ( https://blog.bolshakov.dev/stoplight/ ) that applies per inbox URL (rather than per job). You start in a good (green) state. Each failure counts towards a threshold (10), after which it halts all jobs matching that inbox (red). After the cooldown period (60 seconds) it flips into a "yellow" state: if the next job succeeds, it flips back to green. If it fails, it goes immediately back to red. That configuration seems sorta... pointless to me? if it only kicks in after 10 failures, then it'll only be halting after really long delays, right? it seems like that should be a high threshold with like a really long cooldown to me - if we haven't been able to deliver like 200 messages, then cooldown for like 6 hours (i'm not sure if receiving a message clears the stoplight) receiving a message clears the stoplight))
Discord Messages#sneakers.the.rat-24-01-09 04:53:38 + (so re: [[Stoplight]] … so re: [[Stoplight]] and [[Cooldown]]s, [[Sidekiq#Cooldown]] tries to deliver something 16 times ( https://github.com/NeuromatchAcademy/mastodon/blob/eb24c0ad07c4137517e6bd37ebcc99d6e2b86797/app/workers/activitypub/delivery_worker.rb#L11 )the delay rises exponentially (^4) with each retry. So eg by the 10th retry we're delaying an average of 208 minutes, and by 16 we're at 1365 (22 hours). That delay uses sidekiq's `sidekiq_retry_in` method, which applies to each delivery task (ie. each status we're trying to push), but there is also an additional control flow tool Stoplight ( https://blog.bolshakov.dev/stoplight/ ) that applies per inbox URL (rather than per job). You start in a good (green) state. Each failure counts towards a threshold (10), after which it halts all jobs matching that inbox (red). After the cooldown period (60 seconds) it flips into a "yellow" state: if the next job succeeds, it flips back to green. If it fails, it goes immediately back to red. That configuration seems sorta... pointless to me? if it only kicks in after 10 failures, then it'll only be halting after really long delays, right? it seems like that should be a high threshold with like a really long cooldown to me - if we haven't been able to deliver like 200 messages, then cooldown for like 6 hours (i'm not sure if receiving a message clears the stoplight) receiving a message clears the stoplight))
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-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 ))
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 ))
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)

Admin#sneakers-the-rat-22-12-17 06:03:49 + ([[Tech WG/Ops Diary#22-12-16 Upgrading Lin … [[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Following the instructions to * [[Resizing Linode]] [[Linode]]: https://www.linode.com/docs/guides/resizing-a-linode/* [[Mastodon/Admin#Shutdown]]: https://docs.joinmastodon.org/admin/migrating/ from the migraing docsrg/admin/migrating/ from the migraing docs)
Discord Messages#sneakers-the-rat-22-12-17 06:03:49 + ([[Tech WG/Ops Diary#22-12-16 Upgrading Lin … [[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Following the instructions to * [[Resizing Linode]] [[Linode]]: https://www.linode.com/docs/guides/resizing-a-linode/* [[Mastodon/Admin#Shutdown]]: https://docs.joinmastodon.org/admin/migrating/ from the migraing docsrg/admin/migrating/ from the migraing docs)
Linode#sneakers-the-rat-22-12-17 06:03:49 + ([[Tech WG/Ops Diary#22-12-16 Upgrading Lin … [[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Following the instructions to * [[Resizing Linode]] [[Linode]]: https://www.linode.com/docs/guides/resizing-a-linode/* [[Mastodon/Admin#Shutdown]]: https://docs.joinmastodon.org/admin/migrating/ from the migraing docsrg/admin/migrating/ from the migraing docs)
Resizing Linode#sneakers-the-rat-22-12-17 06:03:49 + ([[Tech WG/Ops Diary#22-12-16 Upgrading Lin … [[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Following the instructions to * [[Resizing Linode]] [[Linode]]: https://www.linode.com/docs/guides/resizing-a-linode/* [[Mastodon/Admin#Shutdown]]: https://docs.joinmastodon.org/admin/migrating/ from the migraing docsrg/admin/migrating/ from the migraing docs)
Tech WG/Ops Diary#sneakers-the-rat-22-12-17 06:03:49 + ([[Tech WG/Ops Diary#22-12-16 Upgrading Lin … [[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Following the instructions to * [[Resizing Linode]] [[Linode]]: https://www.linode.com/docs/guides/resizing-a-linode/* [[Mastodon/Admin#Shutdown]]: https://docs.joinmastodon.org/admin/migrating/ from the migraing docsrg/admin/migrating/ from the migraing docs)

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]])
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]])
Announcements#mannaz-23-07-07 20:10:07 + (@here [[Announcements]] … @here [[Announcements]] hello #neuromatchstodon membies So far [[Jonny]] and [[Manisha]] have been doing most of the admin and moderation work in cooperation with the rest of the instance members. We are excited to welcome new members joining our working groups!🎉 🥳 This has been a long time coming but #MastoDev extraordinaire [[Lina]] (who contributed to the Exclusive Lists PR that got merged upstream) is joining our [[Tech_WG]] 🙌 And the amazing [[El]] (who is one of the organizers of #Maystodon #JoinMastodonDay and #NeuroParty) is joining our [[Social_WG]] 🙌 Thank you both for your outstanding contributions ❤️ 🙏th for your outstanding contributions ❤️ 🙏)
Discord Messages#mannaz-23-07-07 20:10:07 + (@here [[Announcements]] … @here [[Announcements]] hello #neuromatchstodon membies So far <@305044217393053697> and I have been doing most of the admin and moderation work in cooperation with the rest of the instance members. We are excited to welcome new members joining our working groups!🎉 🥳 This has been a long time coming but our very own #MastoDev <@485848481995423755> (who contributed to the exclusive lists PR that got merged upstream) is joining our <#1049184335514828860> 🙌 And the amazing <@961628326005440552> (who is one of the organizers of #Maystodon #JoinMastodonDay and #NeuroParty) is joining the <#1049184264832417823> 🙌 Thank you both for your outstanding contributions ❤️ 🙏832417823> 🙌 Thank you both for your outstanding contributions ❤️ 🙏)
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.)
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.)
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.)
Mastodon/Mathjax#sneakers-the-rat-22-12-12 08:37:18 + (Aight i'm totally flummoxed about how to g … Aight i'm totally flummoxed about how to get [[Mastodon/Mathjax#Stumpted]] to load. it <really really> wants you to use the <script> tag loading method, which i would rather not do since that makes it way less portable or else requires a call-out to an external CDN, but I can't get the startup functions to trigger programmatically, and i've tried all the various things in their docs as well as some other stuff that isn't. I am tempted to just rewrite the mathstodon stuff using a react component that i was able to find but idk <@451520217139511306> u know anything else about this?<@451520217139511306> u know anything else about this?)
Discord Messages#sneakers-the-rat-22-12-12 08:37:18 + (Aight i'm totally flummoxed about how to g … Aight i'm totally flummoxed about how to get [[Mastodon/Mathjax#Stumpted]] to load. it <really really> wants you to use the <script> tag loading method, which i would rather not do since that makes it way less portable or else requires a call-out to an external CDN, but I can't get the startup functions to trigger programmatically, and i've tried all the various things in their docs as well as some other stuff that isn't. I am tempted to just rewrite the mathstodon stuff using a react component that i was able to find but idk <@451520217139511306> u know anything else about this?<@451520217139511306> u know anything else about this?)
Zenodo Social Reading#sneakers-the-rat-23-03-10 07:10:00 + (I just had a good idea I think: [[Mastodon/Hacks#Ideas]] … I just had a good idea I think:[[Mastodon/Hacks#Ideas]] [[Zenodo Social Reading]]https://neuromatch.social/@jonny/109997725222638244> ok you know what would actually rock: a #Zenodo plugin where you could sync a collection to an #ActivityPub outbox, and do social public highlighting that way - share a set of papers under a topic for ppl to browse, but also share your annotations and then be able to show your friends annotations over the papers you're reading if u want to#MastoHacks #MastoDevre reading if u want to #MastoHacks #MastoDev)
Mastodon/Hacks#sneakers-the-rat-23-03-10 07:10:00 + (I just had a good idea I think: [[Mastodon/Hacks#Ideas]] … I just had a good idea I think:[[Mastodon/Hacks#Ideas]] [[Zenodo Social Reading]]https://neuromatch.social/@jonny/109997725222638244> ok you know what would actually rock: a #Zenodo plugin where you could sync a collection to an #ActivityPub outbox, and do social public highlighting that way - share a set of papers under a topic for ppl to browse, but also share your annotations and then be able to show your friends annotations over the papers you're reading if u want to#MastoHacks #MastoDevre reading if u want to #MastoHacks #MastoDev)
Discord Messages#sneakers-the-rat-23-03-10 07:10:00 + (I just had a good idea I think: [[Mastodon/Hacks#Ideas]] … I just had a good idea I think:[[Mastodon/Hacks#Ideas]] [[Zenodo Social Reading]]https://neuromatch.social/@jonny/109997725222638244> ok you know what would actually rock: a #Zenodo plugin where you could sync a collection to an #ActivityPub outbox, and do social public highlighting that way - share a set of papers under a topic for ppl to browse, but also share your annotations and then be able to show your friends annotations over the papers you're reading if u want to#MastoHacks #MastoDevre reading if u want to #MastoHacks #MastoDev)
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)
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-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))
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]])