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 "[[Mastodon/Tech WG#TODO]] [[Mastodon/Social WG#TODO]] Look into setting up Relays https://neuromatch.social/@manisha/109523786200081610". Since there have been only a few results, also nearby values are displayed.

Showing below up to 12 results starting with #1.

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

    

List of results

  • Mastodon/Feeds#sneakers-the-rat-22-12-21 17:49:16  + (so! the "local" feed is the one that shows … so! the "local" feed is the one that shows all the toots from our instance, the "federated" feed shows all toots from everyone that everyone on the instance follow. "local-only toots" are a special feature of glitch-soc where you can make your post *only* visible to the other members of the instance (in base masto you can only limit to mentioned accounts or followers). Local feed also will show you boosts from people on our instance, I'm not sure if there's a way to turn that off but if there isn't there should be bc that would be nice</br></br>[[Mastodon/Social WG#TODO]]: guides on how the different [[Mastodon/Feeds]] and [[Mastodon/Post Visibility]] work[[Mastodon/Post Visibility]] work)
  • Discord Messages#sneakers-the-rat-22-12-21 17:49:16  + (so! the "local" feed is the one that shows … so! the "local" feed is the one that shows all the toots from our instance, the "federated" feed shows all toots from everyone that everyone on the instance follow. "local-only toots" are a special feature of glitch-soc where you can make your post *only* visible to the other members of the instance (in base masto you can only limit to mentioned accounts or followers). Local feed also will show you boosts from people on our instance, I'm not sure if there's a way to turn that off but if there isn't there should be bc that would be nice</br></br>[[Mastodon/Social WG#TODO]]: guides on how the different [[Mastodon/Feeds]] and [[Mastodon/Post Visibility]] work[[Mastodon/Post Visibility]] work)
  • Discord Messages#sneakers-the-rat-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 ♥️♥️♥️😘😘😘</br>in cooperation, towards information liberation!!!!!</br></br>pls join us in conversations in <#1050561894752198706> if you are so inclined 🙂</br></br>[[Mastodon/Seed Council#TODO]]</br></br>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 ♥️♥️♥️😘😘😘</br>in cooperation, towards information liberation!!!!!</br></br>pls join us in conversations in <#1050561894752198706> if you are so inclined 🙂</br></br>[[Mastodon/Seed Council#TODO]]</br></br>https://open.spotify.com/track/0fEasSvs63eKApKfYbi2uDTODO]] https://open.spotify.com/track/0fEasSvs63eKApKfYbi2uD)
  • Camel Case#sneakers-the-rat-22-12-29 00:27:20  + (we've talked about this as well, being abl … we've talked about this as well, being able to make the bot more granularly opt-in, as well as make some simple degeneracy rules like #CamelCase == [[Camel Case]] (actually proposed that probably to no result in masto here: https://github.com/mastodon/mastodon/issues/19992#issuecomment-1363496984 )don/issues/19992#issuecomment-1363496984 ))
  • Discord Messages#sneakers-the-rat-22-12-29 00:27:20  + (we've talked about this as well, being abl … we've talked about this as well, being able to make the bot more granularly opt-in, as well as make some simple degeneracy rules like #CamelCase == [[Camel Case]] (actually proposed that probably to no result in masto here: https://github.com/mastodon/mastodon/issues/19992#issuecomment-1363496984 )don/issues/19992#issuecomment-1363496984 ))
  • Mastodon updates#mannaz-23-07-04 20:31:28  + (worst case scenario -- ppl get a break from scrolling our local TL for a while 😂 🙈 writing here in caps so that we [[Mastodon updates]] REMEMBER TO TAKE A BACKUP BEFORE starting.. we should have a rocess of the typical steps to follow)
  • Discord Messages#mannaz-23-07-04 20:31:28  + (worst case scenario -- ppl get a break from scrolling our local TL for a while 😂 🙈 writing here in caps so that we [[Mastodon updates]] REMEMBER TO TAKE A BACKUP BEFORE starting.. we should have a rocess of the typical steps to follow)
  • Discord Messages#sneakers.the.rat-23-07-04 21:16:38  + (yes agreed we should make a wiki guide to … yes agreed we should make a wiki guide to updating the instance. </br></br>I need to log off for the day bc am visiting friends, but in short it's</br>- start backup in linode (reminder to also set you up with an account there and add that to [[Tech WG#TODO]] [[Tech WG/Onboarding]] docs</br>- do all the git work that we're familiar with to prepare the new deploy</br>- check upgrade notes, usually on base masto release notes, to see if anything out of the ordinary is required</br>- pull down new changes to server</br>- potentially recompile yarn assets</br>- potentially run database migrations</br>- restart mastodon-* services</br></br>and that's usually it. downtime is usually on the order of a few seconds (and we could explore how to make that zero, I think that's how the pros do it with like multiple servers)the pros do it with like multiple servers))
  • Tech WG/Onboarding#sneakers.the.rat-23-07-04 21:16:38  + (yes agreed we should make a wiki guide to … yes agreed we should make a wiki guide to updating the instance. </br></br>I need to log off for the day bc am visiting friends, but in short it's</br>- start backup in linode (reminder to also set you up with an account there and add that to [[Tech WG#TODO]] [[Tech WG/Onboarding]] docs</br>- do all the git work that we're familiar with to prepare the new deploy</br>- check upgrade notes, usually on base masto release notes, to see if anything out of the ordinary is required</br>- pull down new changes to server</br>- potentially recompile yarn assets</br>- potentially run database migrations</br>- restart mastodon-* services</br></br>and that's usually it. downtime is usually on the order of a few seconds (and we could explore how to make that zero, I think that's how the pros do it with like multiple servers)the pros do it with like multiple servers))
  • Tech WG#sneakers.the.rat-23-07-04 21:16:38  + (yes agreed we should make a wiki guide to … yes agreed we should make a wiki guide to updating the instance. </br></br>I need to log off for the day bc am visiting friends, but in short it's</br>- start backup in linode (reminder to also set you up with an account there and add that to [[Tech WG#TODO]] [[Tech WG/Onboarding]] docs</br>- do all the git work that we're familiar with to prepare the new deploy</br>- check upgrade notes, usually on base masto release notes, to see if anything out of the ordinary is required</br>- pull down new changes to server</br>- potentially recompile yarn assets</br>- potentially run database migrations</br>- restart mastodon-* services</br></br>and that's usually it. downtime is usually on the order of a few seconds (and we could explore how to make that zero, I think that's how the pros do it with like multiple servers)the pros do it with like multiple servers))
  • Discord Messages#sneakers.the.rat-23-07-07 18:51:01  + (- solidarity with the fedi: to survive thi … - solidarity with the fedi: to survive this and future attempts at corporate capture, it is important to act together. many instances have already committed to defederation, and even if it is symbolic, symbols are important.</br></br>- being defederated by other instances: we are currently in the good graces of some very protective instances through prior social ties and our promise to be a good actor in the space, these include instances with many leftists, queer people, and others that would likely defederate from us if we were to federate with meta. this would put NMS in a more homogeneous, corporate nice space in the fedi.</br></br>- communication with threads users: some people probably want to communicate with some threads users, and this might cause dual accounts, as you say. defederation would potentially split ties. I will hold my thoughts on this for now since I'm just trying to list the relevant factors.</br></br>what else? listing the concerns, we could then see how each impacts a decision to limit/defederate based on what each decision does. </br></br>I am traveling and AFK until Monday, but I think it would also be good to make a [[Defederation from Meta]] wiki page to keep more organized notes. forgot to tag the previous post.ed notes. forgot to tag the previous post.)
  • 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]])
  • 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]])
  • Announcements#mannaz-23-07-07 20:10:07  + (@here [[Announcements]] … @here [[Announcements]] hello #neuromatchstodon membies </br>So far [[Jonny]] and [[Manisha]] have been doing most of the admin and moderation work in cooperation with the rest of the instance members. </br></br>We are excited to welcome new members joining our working groups!🎉 🥳 </br></br>This has been a long time coming but #MastoDev extraordinaire [[Lina]] (who contributed to the Exclusive Lists PR that got merged upstream) is joining our [[Tech_WG]] 🙌 </br></br>And the amazing [[El]] (who is one of the organizers of #Maystodon #JoinMastodonDay and #NeuroParty) is joining our [[Social_WG]] 🙌 </br></br>Thank you both for your outstanding contributions ❤️ 🙏th for your outstanding contributions ❤️ 🙏)
  • Discord Messages#sneakers-the-rat-23-03-18 21:48:09  + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: </br>[[Mastodon/Tests]]</br>[[Mastodon/Tech WG]]</br>[[Exclusive Lists]]</br>[[Ruby Spec]]</br>[[Ruby]]</br>spec for home feed:</br>https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rb</br>for public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rb</br>that gives more examples on how feeds are supposed to be filtered</br>tag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rb</br>in case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)</br>account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rb</br></br>and so on </br></br>the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write</br>`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.</br></br>Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.js</br>and doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.</br></br>So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
  • Mastodon/Tests#sneakers-the-rat-23-03-18 21:48:09  + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: </br>[[Mastodon/Tests]]</br>[[Mastodon/Tech WG]]</br>[[Exclusive Lists]]</br>[[Ruby Spec]]</br>[[Ruby]]</br>spec for home feed:</br>https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rb</br>for public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rb</br>that gives more examples on how feeds are supposed to be filtered</br>tag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rb</br>in case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)</br>account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rb</br></br>and so on </br></br>the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write</br>`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.</br></br>Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.js</br>and doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.</br></br>So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
  • Jest#sneakers-the-rat-23-03-18 21:48:09  + (@lina gathering some stuff here: [[Mastodon/Tests]] … @lina gathering some stuff here: </br>[[Mastodon/Tests]]</br>[[Mastodon/Tech WG]]</br>[[Exclusive Lists]]</br>[[Ruby Spec]]</br>[[Ruby]]</br>spec for home feed:</br>https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/home_feed_spec.rb</br>for public feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/public_feed_spec.rb</br>that gives more examples on how feeds are supposed to be filtered</br>tag feed: https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/tag_feed_spec.rb</br>in case we might want to add exclusive tag feeds (I personally do, self interested bc monsterdon lol)</br>account filter (looks like for blocks): https://github.com/NeuromatchAcademy/mastodon/blob/main/spec/models/account_statuses_filter_spec.rb</br></br>and so on </br></br>the question to me is basically how these things are structured: you have some fabricator steps that set up the conditions for the test, but then you also have these `context` statements that looks like plain English strings to me? like how do those and the `describe` fields map onto the code? like is their testing system so good that you can really just write</br>`it {is_expected.to be_filtered }` and that just works???? or how do you define all those.</br></br>Also u mentioned they are using a separate JavaScript testing framework? [[Jest]] ? that looks like it's configured here: https://github.com/NeuromatchAcademy/mastodon/blob/main/jest.config.js</br>and doesn't cover the glitch flavours, just the mastodon folder. it seems like that is for testing the appearance and function of the JS? not sure how it interacts with the ruby tests.</br></br>So for the sake of us learning to write tests here, I don't think we need to aim for full adversarial coverage of the feature, but just get the basics: "when an account is in an exclusive list, their posts dont show up on the home feed." judging from the other tests, it looks like we'll have to also test for boosts from them, but since it's not like a block we don't have to test a bunch of edge cases like interactions.t a bunch of edge cases like interactions.)
Retrieved from "https://wiki.neuromatch.social/Special:SearchByProperty/:Contains-20text/-5B-5BMastodon-2FTech-20WG-23TODO-5D-5D-20-5B-5BMastodon-2FSocial-20WG-23TODO-5D-5D-20Look-20into-20setting-20up-20Relays-20https:-2F-2Fneuromatch.social-2F@manisha-2F109523786200081610"