Search by property

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

Search by property

A list of all pages that have property "Contains text" with value "Thank you soo much El!! This would be amazing! to be frank, you already help us here in the working group and we all truly appreciate that ❤️ [[Social WG/Responsibilities]] If you officially join, what this would do is allow us to give you access to the moderation interface where we handle new account requests and reports, and you'd also publicly get the credit that you deserve for all your contributions! :) I think some academics can be really stingy about giving credits (uh see one of my recent polls :P https://neuromatch.social/@manisha/110556283019459141) but in a place like ours where we are all volunteers doing the work, every bit of appreciation goes a long way. So another thing we could be doing more often is showing gratitude to instance members and like <@305044217393053697> mentioned -- make everyone feel welcome and improve our onboarding experience. Like recently from the socialwg account, I've been boosting intros, lab pics, graduation news, etc etc.. We could make all of that more fun and be like "hey #neuromatchstodon <awesome NMS member> got their PhD give them boosts" 🥳 or something Account requests are usually the fun part of moderation -- I love reading the reasons people/organizations/departments/conferences share for joining the instance and they are always so interesting and spanerse! (e.g. the time someone said they had fomo of not being on neuromatch.social ❤️ https://discord.com/channels/1049136631065628772/1049136631065628775/1116378014897426432) The only thing to be careful of is if the account requester mentions something that could be a violation of our rules or our bylaws. In such instances, I typically ask the instance for their opinion on our social wg forum channel. For full transparency we do have a private mod channel but we haven't used that since April! A good sign that we are not hiding things from the instance. We used to use it only for cases where we had to disclose some PII". Since there have been only a few results, also nearby values are displayed.

Showing below up to 26 results starting with #1.

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

Property: Value:

List of results

Institutional Memory#sneakers-the-rat-22-12-09 12:10:47 + (as u talk about stuff you can tag in vario … as u talk about stuff you can tag in various concepts like [[Institutional Memory]] or if your working group is organized you can even tag in specific projects and Todo lists or just use it to bookmark conversations so you have an indexical/plastic memorybank alongside a fluid/streamlike mode of communication. the cscw ppl in the workshop we did a month or so ago went bananas for this lol it is goodo ago went bananas for this lol it is good)
Discord Messages#sneakers-the-rat-23-01-26 03:58:14 + (great! let me plant a bookmark on the wiki to remind me to fill in this information when I get internet at my new place & can edit it. [[Accessibility#Disabling Motion]] [[Discord#Accessibility]])
Accessibility#sneakers-the-rat-23-01-26 03:58:14 + (great! let me plant a bookmark on the wiki to remind me to fill in this information when I get internet at my new place & can edit it. [[Accessibility#Disabling Motion]] [[Discord#Accessibility]])
Discord#sneakers-the-rat-23-01-26 03:58:14 + (great! let me plant a bookmark on the wiki to remind me to fill in this information when I get internet at my new place & can edit it. [[Accessibility#Disabling Motion]] [[Discord#Accessibility]])
Discord Messages#sneakers.the.rat-24-01-15 03:31:15 + (i can't remember where we left off w.r.t. enabling [[trends]] on the instance, i can't think of a strong reason to leave them disabled, but does anyone have feelings about this?)
Trends#sneakers.the.rat-24-01-15 03:31:15 + (i can't remember where we left off w.r.t. enabling [[trends]] on the instance, i can't think of a strong reason to leave them disabled, but does anyone have feelings about this?)
DIY Algorithms#sneakers-the-rat-23-02-07 04:15:02 + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
Discord Messages#sneakers-the-rat-23-02-07 04:15:02 + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
Mastodon/TODO#sneakers-the-rat-23-02-07 04:15:02 + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
Nested Threads#sneakers-the-rat-23-02-07 04:15:02 + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
Grants#sneakers-the-rat-23-02-07 04:15:02 + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
Mastodon/Grants#sneakers-the-rat-23-02-07 04:15:02 + (i think it would be cool if we could pay a … i think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
Tech WG/Ops Diary#sneakers-the-rat-23-05-20 08:29:54 + (ok [[Tech_WG/Ops_Diary#23-05-19]] … ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
WikiBot#sneakers-the-rat-23-05-20 08:29:54 + (ok [[Tech_WG/Ops_Diary#23-05-19]] … ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
Discord Messages#sneakers-the-rat-23-05-20 08:29:54 + (ok [[Tech_WG/Ops_Diary#23-05-19]] … ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
Discord Messages#sneakers-the-rat-22-12-26 23:33:51 + (ok here's [[Fetch All Replies]]: https://neuromatch.social/@jonny/109582537808504261)
Fetch All Replies#sneakers-the-rat-22-12-26 23:33:51 + (ok here's [[Fetch All Replies]]: https://neuromatch.social/@jonny/109582537808504261)
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)
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]])
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-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))
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))
WikiBot#sneakers-the-rat-22-12-29 00:22:33 + (the DOI thing I think will only take an ho … the DOI thing I think will only take an hour or two more, and then yeah will be adapting some of the [[WikiBot]] code that runs on this discord already to do an agora-like thing. I've talked to flancian about this as well a bunch of times, unifying the agora bots and making a general framework for that kind of cross platform linkingrk for that kind of cross platform linking)

Discord Messages#mannaz-23-07-06 23:31:37 + (Thank you soo much El!! This would be amaz … Thank you soo much El!! This would be amazing! to be frank, you already help us here in the working group and we all truly appreciate that ❤️ [[Social WG/Responsibilities]] If you officially join, what this would do is allow us to give you access to the moderation interface where we handle new account requests and reports, and you'd also publicly get the credit that you deserve for all your contributions! :) I think some academics can be really stingy about giving credits (uh see one of my recent polls :P https://neuromatch.social/@manisha/110556283019459141) but in a place like ours where we are all volunteers doing the work, every bit of appreciation goes a long way. So another thing we could be doing more often is showing gratitude to instance members and like <@305044217393053697> mentioned -- make everyone feel welcome and improve our onboarding experience. Like recently from the socialwg account, I've been boosting intros, lab pics, graduation news, etc etc.. We could make all of that more fun and be like "hey #neuromatchstodon <awesome NMS member> got their PhD give them boosts" 🥳 or something Account requests are usually the fun part of moderation -- I love reading the reasons people/organizations/departments/conferences share for joining the instance and they are always so interesting and diverse! (e.g. the time someone said they had fomo of not being on neuromatch.social ❤️ https://discord.com/channels/1049136631065628772/1049136631065628775/1116378014897426432)The only thing to be careful of is if the account requester mentions something that could be a violation of our rules or our bylaws. In such instances, I typically ask the instance for their opinion on our social wg forum channel. For full transparency we do have a private mod channel but we haven't used that since April! A good sign that we are not hiding things from the instance. We used to use it only for cases where we had to disclose some PIIse it only for cases where we had to disclose some PII)
Social WG/Responsibilities#mannaz-23-07-06 23:31:37 + (Thank you soo much El!! This would be amaz … Thank you soo much El!! This would be amazing! to be frank, you already help us here in the working group and we all truly appreciate that ❤️ [[Social WG/Responsibilities]] If you officially join, what this would do is allow us to give you access to the moderation interface where we handle new account requests and reports, and you'd also publicly get the credit that you deserve for all your contributions! :) I think some academics can be really stingy about giving credits (uh see one of my recent polls :P https://neuromatch.social/@manisha/110556283019459141) but in a place like ours where we are all volunteers doing the work, every bit of appreciation goes a long way. So another thing we could be doing more often is showing gratitude to instance members and like <@305044217393053697> mentioned -- make everyone feel welcome and improve our onboarding experience. Like recently from the socialwg account, I've been boosting intros, lab pics, graduation news, etc etc.. We could make all of that more fun and be like "hey #neuromatchstodon <awesome NMS member> got their PhD give them boosts" 🥳 or something Account requests are usually the fun part of moderation -- I love reading the reasons people/organizations/departments/conferences share for joining the instance and they are always so interesting and diverse! (e.g. the time someone said they had fomo of not being on neuromatch.social ❤️ https://discord.com/channels/1049136631065628772/1049136631065628775/1116378014897426432)The only thing to be careful of is if the account requester mentions something that could be a violation of our rules or our bylaws. In such instances, I typically ask the instance for their opinion on our social wg forum channel. For full transparency we do have a private mod channel but we haven't used that since April! A good sign that we are not hiding things from the instance. We used to use it only for cases where we had to disclose some PIIse it only for cases where we had to disclose some PII)

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 ❤️ 🙏)
Discord Messages#sneakers-the-rat-23-03-18 21:48:09 + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: [[Mastodon/Tests]][[Mastodon/Tech WG]][[Exclusive Lists]][[Ruby Spec]][[Ruby]]spec for home feed:https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rbfor public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rbthat gives more examples on how feeds are supposed to be filteredtag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rbin case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rband so on the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.jsand doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
Mastodon/Tests#sneakers-the-rat-23-03-18 21:48:09 + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: [[Mastodon/Tests]][[Mastodon/Tech WG]][[Exclusive Lists]][[Ruby Spec]][[Ruby]]spec for home feed:https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rbfor public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rbthat gives more examples on how feeds are supposed to be filteredtag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rbin case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rband so on the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.jsand doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
Jest#sneakers-the-rat-23-03-18 21:48:09 + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: [[Mastodon/Tests]][[Mastodon/Tech WG]][[Exclusive Lists]][[Ruby Spec]][[Ruby]]spec for home feed:https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rbfor public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rbthat gives more examples on how feeds are supposed to be filteredtag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rbin case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rband so on the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.jsand doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
Ruby Spec#sneakers-the-rat-23-03-18 21:48:09 + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: [[Mastodon/Tests]][[Mastodon/Tech WG]][[Exclusive Lists]][[Ruby Spec]][[Ruby]]spec for home feed:https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rbfor public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rbthat gives more examples on how feeds are supposed to be filteredtag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rbin case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rband so on the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.jsand doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
Ruby#sneakers-the-rat-23-03-18 21:48:09 + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: [[Mastodon/Tests]][[Mastodon/Tech WG]][[Exclusive Lists]][[Ruby Spec]][[Ruby]]spec for home feed:https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rbfor public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rbthat gives more examples on how feeds are supposed to be filteredtag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rbin case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rband so on the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.jsand doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
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-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?)
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?)
TODO#sneakers.the.rat-24-01-20 05:20:06 + (Also that reminds me that I did get the announcement notif but the interface opened starting with the first announcement not the most recent one so [[TODO]])
Discord Messages#sneakers.the.rat-24-01-20 05:20:06 + (Also that reminds me that I did get the announcement notif but the interface opened starting with the first announcement not the most recent one so [[TODO]])
Unattended Upgrades#sneakers.the.rat-23-09-21 21:37:59 + (Btw I noticed we don't have [[Unattended Upgrades]] … Btw I noticed we don't have [[Unattended Upgrades]] turned on to automatically keep system-level packages up to date. I usually do that with servers I manage because i have been told by security ppl that keeping up to date is like most of what matters with day-to-say security probs, but i mean it seems like it could uh accidentally break a package one day and kill the instance, so idk if there's a reason to not do that but thought i'd ask reason to not do that but thought i'd ask)
Discord Messages#sneakers.the.rat-23-09-21 21:37:59 + (Btw I noticed we don't have [[Unattended Upgrades]] … Btw I noticed we don't have [[Unattended Upgrades]] turned on to automatically keep system-level packages up to date. I usually do that with servers I manage because i have been told by security ppl that keeping up to date is like most of what matters with day-to-say security probs, but i mean it seems like it could uh accidentally break a package one day and kill the instance, so idk if there's a reason to not do that but thought i'd ask reason to not do that but thought i'd ask)
Discord Messages#sneakers-the-rat-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)
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)
Trends#mannaz-23-07-10 22:57:03 + (I think that's part of trends (but I'd nee … I think that's part of trends (but I'd need to check). and the reason why we didn't have [[Trends]] enabled was because of this: https://discord.com/channels/1049136631065628772/1052069805856935996/1067653230533804093 if that has changed in the recent versions of masto/glitch, we can enable trends againf masto/glitch, we can enable trends again)
Discord Messages#mannaz-23-07-10 22:57:03 + (I think that's part of trends (but I'd nee … I think that's part of trends (but I'd need to check). and the reason why we didn't have [[Trends]] enabled was because of this: https://discord.com/channels/1049136631065628772/1052069805856935996/1067653230533804093 if that has changed in the recent versions of masto/glitch, we can enable trends againf masto/glitch, we can enable trends again)
Discord Messages#sneakers.the.rat-23-09-27 23:54:40 + (I wanted to check in before I invited some … I wanted to check in before I invited someone(s) that is not a neuromatch.social member to the discord - we already have a few beloved [[Honorary Members]] but I dont think we have any explicit norm here. Does anyone have any objection to this? The main reason to use discord is to be able to coordinate in small groups in real time in a way masto doesn't really work for, and nothing in public channels as far as I can tell is private, so it makes sense to me for members to be able to invite ppl they vouch for? If honorary members cause trouble (which I doubt they would) then we could address that when/if it happens, it seems like prevailing social norms of being responsible for someone u bring into a space mostly take care of that yno.If I dont hear anything in a day or so ill invite them!r anything in a day or so ill invite them!)
Honorary Members#sneakers.the.rat-23-09-27 23:54:40 + (I wanted to check in before I invited some … I wanted to check in before I invited someone(s) that is not a neuromatch.social member to the discord - we already have a few beloved [[Honorary Members]] but I dont think we have any explicit norm here. Does anyone have any objection to this? The main reason to use discord is to be able to coordinate in small groups in real time in a way masto doesn't really work for, and nothing in public channels as far as I can tell is private, so it makes sense to me for members to be able to invite ppl they vouch for? If honorary members cause trouble (which I doubt they would) then we could address that when/if it happens, it seems like prevailing social norms of being responsible for someone u bring into a space mostly take care of that yno.If I dont hear anything in a day or so ill invite them!r anything in a day or so ill invite them!)
Wiki/TODO#mstimberg-22-12-09 20:16:00 + (Re [[Wiki/TODO#Onboarding]]: I migrated earlier today and took some notes, happy to add them to the wiki – I'd need someone to approve my account (`mstimberg`), though 😊)
Discord Messages#mstimberg-22-12-09 20:16:00 + (Re [[Wiki/TODO#Onboarding]]: I migrated earlier today and took some notes, happy to add them to the wiki – I'd need someone to approve my account (`mstimberg`), though 😊)
Mastodon/Hacks#sneakers.the.rat-23-10-06 21:45:39 + (So idle thought, i saw someone whose inst … So idle thought, i saw someone whose instance had [[Slugified URLs]] for posts, ( eg. https://neuromatch.social/@Jonny /my-post-title )And it looks like it would be pretty easy to do...- add a `slug` db column in the statuses table- add a route using `slug` https://github.com/mastodon/mastodon/blob/3262d1f1b62a984343f0f6c67c1d18921daabb0a/config/routes.rb#L130- add a field to the status composer component to optionally add a slug, which would need to validate for correct formatting and uniqueness (eg. Show red outline with message when slug is already used, disallow spaces and other non URI chars)- add API endpoint to check if slug exists- add button in "share" dropdown to copy slugified link- optionally: provide an auto-slug option that slugifies the first n unique characters in a post, or parses a leading # headerThat would be for adding them as an additional ui thing, rather than changing the representation of the AP objects/etc. ID URL would remain canonical, slug would be useful for sharing, and also if we want to allow posts to behave more like pages (eg. Set custom page CSS for an `Article` type vs the usual `Note` ) for a future rich text editor hack that makes masto both micro and macro blog[[Mastodon/Hacks]][[Mastodon/Hacks]])