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 "<@827519038120132608> also re: memory and bridging between the garden and the stream or whatever metaphor ya want, you should check out [[WikiBot#Purpose]]". 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)


    

List of results

  • Discord Messages#sneakers-the-rat-22-12-09 11:39:41  + ([[Testing Wikibot]])
  • Discord Messages#sneakers-the-rat-22-12-09 11:34:07  + ([[Testing Wikibot]])
  • Testing Wikibot#sneakers-the-rat-22-12-09 11:39:41  + ([[Testing Wikibot]])
  • Testing Wikibot#sneakers-the-rat-22-12-09 11:34:07  + ([[Testing Wikibot]])
  • Wiki/TODO#sneakers-the-rat-22-12-09 12:38:45  + ([[Wiki#TODO]] Clean up link to [[Wiki/TODO]] and write some docs on [[Wikibot#Usage Patterns]])
  • Wikibot#sneakers-the-rat-22-12-09 12:38:45  + ([[Wiki#TODO]] Clean up link to [[Wiki/TODO]] and write some docs on [[Wikibot#Usage Patterns]])
  • Wiki#sneakers-the-rat-22-12-09 12:38:45  + ([[Wiki#TODO]] Clean up link to [[Wiki/TODO]] and write some docs on [[Wikibot#Usage Patterns]])
  • Discord Messages#sneakers-the-rat-22-12-09 12:38:45  + ([[Wiki#TODO]] Clean up link to [[Wiki/TODO]] and write some docs on [[Wikibot#Usage Patterns]])
  • Institutional Memory#sneakers-the-rat-22-12-09 12:10:47  + (as u talk about stuff you can tag in varioas 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-22-12-09 12:10:47  + (as u talk about stuff you can tag in varioas 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)
  • Tech WG/Ops Diary#sneakers-the-rat-23-05-20 08:29:54  + (ok [[Tech_WG/Ops_Diary#23-05-19]]ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
  • WikiBot#sneakers-the-rat-23-05-20 08:29:54  + (ok [[Tech_WG/Ops_Diary#23-05-19]]ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
  • Discord Messages#sneakers-the-rat-23-05-20 08:29:54  + (ok [[Tech_WG/Ops_Diary#23-05-19]]ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
  • Discussions#sneakers.the.rat-24-01-17 10:58:31  + (ok i'd like to raise an olde idea again anok 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.</br></br>here's one idea of what that might look like:</br>v1</br>- 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.</br>- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post</br>- sticky posts come from an autofollowed @ discussions account</br>- ... are local only posts</br>- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed</br>- ... 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 feed</br></br>questions: </br>- can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'</br>- should stickies have a time limit? or just a mechanism to close them in governance process?</br></br>v2</br>a) The threading interface on the web interface is awful, </br>b) it would be nice to be able to show a title on a minimized sticky post</br>c) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike way</br>so</br>- posts can have titles</br>- titles are declared with a special "title" field in the web ui</br>- or with a first line beginning with a # from other clients, a la markdown</br>- replies with titles can be minimized too</br>- replies with titles are sorted first (bc they can be minimized)</br></br>[[Hacks]][[Hacks]])
  • Hacks#sneakers.the.rat-24-01-17 10:58:31  + (ok i'd like to raise an olde idea again anok 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.</br></br>here's one idea of what that might look like:</br>v1</br>- 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.</br>- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post</br>- sticky posts come from an autofollowed @ discussions account</br>- ... are local only posts</br>- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed</br>- ... 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 feed</br></br>questions: </br>- can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'</br>- should stickies have a time limit? or just a mechanism to close them in governance process?</br></br>v2</br>a) The threading interface on the web interface is awful, </br>b) it would be nice to be able to show a title on a minimized sticky post</br>c) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike way</br>so</br>- posts can have titles</br>- titles are declared with a special "title" field in the web ui</br>- or with a first line beginning with a # from other clients, a la markdown</br>- replies with titles can be minimized too</br>- replies with titles are sorted first (bc they can be minimized)</br></br>[[Hacks]][[Hacks]])
  • Discord Messages#sneakers.the.rat-24-01-17 10:58:31  + (ok i'd like to raise an olde idea again anok 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.</br></br>here's one idea of what that might look like:</br>v1</br>- 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.</br>- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post</br>- sticky posts come from an autofollowed @ discussions account</br>- ... are local only posts</br>- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed</br>- ... 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 feed</br></br>questions: </br>- can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'</br>- should stickies have a time limit? or just a mechanism to close them in governance process?</br></br>v2</br>a) The threading interface on the web interface is awful, </br>b) it would be nice to be able to show a title on a minimized sticky post</br>c) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike way</br>so</br>- posts can have titles</br>- titles are declared with a special "title" field in the web ui</br>- or with a first line beginning with a # from other clients, a la markdown</br>- replies with titles can be minimized too</br>- replies with titles are sorted first (bc they can be minimized)</br></br>[[Hacks]][[Hacks]])
  • WikiBot Checkup#sneakers-the-rat-23-04-27 04:17:50  + (sidenote I just looked at the channel member list and holy crap wikibot are you still alive [[WikiBot Checkup]])
  • Discord Messages#sneakers-the-rat-23-04-27 04:17:50  + (sidenote I just looked at the channel member list and holy crap wikibot are you still alive [[WikiBot Checkup]])
  • WikiBot#sneakers-the-rat-22-12-29 00:22:33  + (the DOI thing I think will only take an hothe 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#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))
  • WikiBot#sneakers-the-rat-22-12-29 00:24:51  + (yes! this is definitely the idea with the yes! this is definitely the idea with the [[WikiBot]]: capture links in situ for reminders and backlinks, but then have them be part of the wiki that can be curated down rather than just being the raw content of the post forever. Need to fix up the css for representing posts on the wiki to make them a little less obtrusive, but then yeah they can be hidden or collapsed once the page matures.hidden or collapsed once the page matures.)
  • WikiBot#sneakers-the-rat-22-12-09 12:07:42  +
  • Discord Messages#sneakers-the-rat-22-12-09 12:07:42  +
  • 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#Voting</br>Yes, 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. </br></br>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). </br></br>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#Voting</br>Yes, 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. </br></br>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). </br></br>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.)
  • Discord Messages#mannaz-23-07-10 22:57:03  + (I think that's part of trends (but I'd neeI 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 </br></br>if that has changed in the recent versions of masto/glitch, we can enable trends againf masto/glitch, we can enable trends again)
  • Trends#mannaz-23-07-10 22:57:03  + (I think that's part of trends (but I'd neeI 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 </br></br>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 someI 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? </br></br>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.</br></br>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 someI 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? </br></br>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.</br></br>If I dont hear anything in a day or so ill invite them!r anything in a day or so ill invite them!)
  • TODO#sneakers-the-rat-22-12-09 11:52:48  + (So anyway [[TODO]] Document the [[WikiBot]])
  • Discord Messages#sneakers.the.rat-23-10-06 21:45:39  + (So idle thought, i saw someone whose instSo idle thought, i saw someone whose instance had [[Slugified URLs]] for posts, ( eg. https://neuromatch.social/@Jonny /my-post-title )</br>And it looks like it would be pretty easy to do...</br>- add a `slug` db column in the statuses table</br>- add a route using `slug` https://github.com/mastodon/mastodon/blob/3262d1f1b62a984343f0f6c67c1d18921daabb0a/config/routes.rb#L130</br>- 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)</br>- add API endpoint to check if slug exists</br>- add button in "share" dropdown to copy slugified link</br>- optionally: provide an auto-slug option that slugifies the first n unique characters in a post, or parses a leading # header</br></br>That 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</br></br>[[Mastodon/Hacks]][[Mastodon/Hacks]])
  • Mastodon/Hacks#sneakers.the.rat-23-10-06 21:45:39  + (So idle thought, i saw someone whose instSo idle thought, i saw someone whose instance had [[Slugified URLs]] for posts, ( eg. https://neuromatch.social/@Jonny /my-post-title )</br>And it looks like it would be pretty easy to do...</br>- add a `slug` db column in the statuses table</br>- add a route using `slug` https://github.com/mastodon/mastodon/blob/3262d1f1b62a984343f0f6c67c1d18921daabb0a/config/routes.rb#L130</br>- 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)</br>- add API endpoint to check if slug exists</br>- add button in "share" dropdown to copy slugified link</br>- optionally: provide an auto-slug option that slugifies the first n unique characters in a post, or parses a leading # header</br></br>That 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</br></br>[[Mastodon/Hacks]][[Mastodon/Hacks]])
  • Slugified URLs#sneakers.the.rat-23-10-06 21:45:39  + (So idle thought, i saw someone whose instSo idle thought, i saw someone whose instance had [[Slugified URLs]] for posts, ( eg. https://neuromatch.social/@Jonny /my-post-title )</br>And it looks like it would be pretty easy to do...</br>- add a `slug` db column in the statuses table</br>- add a route using `slug` https://github.com/mastodon/mastodon/blob/3262d1f1b62a984343f0f6c67c1d18921daabb0a/config/routes.rb#L130</br>- 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)</br>- add API endpoint to check if slug exists</br>- add button in "share" dropdown to copy slugified link</br>- optionally: provide an auto-slug option that slugifies the first n unique characters in a post, or parses a leading # header</br></br>That 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</br></br>[[Mastodon/Hacks]][[Mastodon/Hacks]])
  • Social WG/Responsibilities#mannaz-23-07-07 00:50:28  + (Thank you El and welcome onboard!! woohoo!Thank you El and welcome onboard!! woohoo!! 🥳 ❤️ 💚 💜 💙 🧡 </br></br>[[Social WG/Responsibilities]] continued: with great power comes great responsibility :) </br></br>Before taking any drastic decisions, we should discuss things with the instance -- things like defederation/limiting instances and banning accounts. Also, we should be careful when speaking on behalf of the instance from our "official" accounts like the @socialwg one (this one is quite scary for me because sometime mods say something that ticks another mod/instance member off and then it leads to pile ons 😬 -- so we try to be as cordial as possible and respect people from other instances even if they choose different things for their community - that's fine. we all don't have to be an exact replica of each other :) )</br></br>we learn new things from other mods too -- I follow the #fediblock hashtag and keep an eye on anything that could affect us terribly. In the past we have blocked instances based on reports from other mods on this hashtag (see <#1055915765133488158>) </br></br>I've been on call since December https://wiki.neuromatch.io/Mastodon/Mods_On_Call. You could add your availability here. Let's get you wiki access as well if you don't have already. Create an account here: https://wiki.neuromatch.io and <@305044217393053697> can approve it when they are back from their short holiday. </br></br>Being on call means I check for new account requests once a day and approve them if there aren't any issues. Or bring the discussion to the instance. And handle any reports. We get updates from linode when a few settings cross a threshold. Usually it just means the instance has been busy. But it could also be a DDoS attack -- so I also quickly browse through our local TL and this discord to see nothings blowing up. We have an admin@neuromatch.social account that I monitor every few days. We get very few emails there. monitor every few days. We get very few emails there.)
  • Discord Messages#mannaz-23-07-07 00:50:28  + (Thank you El and welcome onboard!! woohoo!Thank you El and welcome onboard!! woohoo!! 🥳 ❤️ 💚 💜 💙 🧡 </br></br>[[Social WG/Responsibilities]] continued: with great power comes great responsibility :) </br></br>Before taking any drastic decisions, we should discuss things with the instance -- things like defederation/limiting instances and banning accounts. Also, we should be careful when speaking on behalf of the instance from our "official" accounts like the @socialwg one (this one is quite scary for me because sometime mods say something that ticks another mod/instance member off and then it leads to pile ons 😬 -- so we try to be as cordial as possible and respect people from other instances even if they choose different things for their community - that's fine. we all don't have to be an exact replica of each other :) )</br></br>we learn new things from other mods too -- I follow the #fediblock hashtag and keep an eye on anything that could affect us terribly. In the past we have blocked instances based on reports from other mods on this hashtag (see <#1055915765133488158>) </br></br>I've been on call since October https://wiki.neuromatch.io/Mastodon/Mods_On_Call. You could add your availability here. Let's get you wiki access as well if you don't have already. Create an account here: https://wiki.neuromatch.io and <@305044217393053697> can approve it when they are back from their short holiday. </br></br>Being on call means I check for new account requests once a day and approve them if there aren't any issues. Or bring the discussion to the instance. And handle any reports. We get updates from linode when a few settings cross a threshold. Usually it just means the instance has been busy. But it could also be a DDoS attack -- so I also quickly browse through our local TL and this discord to see nothings blowing up. We have an admin@neuromatch.social account that I monitor every few days. We get very few emails there. monitor every few days. We get very few emails there.)
  • Mastodon/Hacking#sneakers-the-rat-22-12-12 20:53:43  + ([[Mastodon/Mathjax]]: information in this [[Mastodon/Mathjax]]: information in this thread about different possible implementation approaches</br></br>[[Mastodon/Hacking#Dev Environment]]: Details on setting up [[Vagrant]] for local development</br></br>[[Wikibot#TODO]]: implement n-back archiving of threads and previous posts, the parser already supports itious posts, the parser already supports it)
  • Mastodon/Mathjax#sneakers-the-rat-22-12-12 20:53:43  + ([[Mastodon/Mathjax]]: information in this [[Mastodon/Mathjax]]: information in this thread about different possible implementation approaches</br></br>[[Mastodon/Hacking#Dev Environment]]: Details on setting up [[Vagrant]] for local development</br></br>[[Wikibot#TODO]]: implement n-back archiving of threads and previous posts, the parser already supports itious posts, the parser already supports it)
  • Wikibot#sneakers-the-rat-22-12-12 20:53:43  + ([[Mastodon/Mathjax]]: information in this [[Mastodon/Mathjax]]: information in this thread about different possible implementation approaches</br></br>[[Mastodon/Hacking#Dev Environment]]: Details on setting up [[Vagrant]] for local development</br></br>[[Wikibot#TODO]]: implement n-back archiving of threads and previous posts, the parser already supports itious posts, the parser already supports it)
  • Vagrant#sneakers-the-rat-22-12-12 20:53:43  + ([[Mastodon/Mathjax]]: information in this [[Mastodon/Mathjax]]: information in this thread about different possible implementation approaches</br></br>[[Mastodon/Hacking#Dev Environment]]: Details on setting up [[Vagrant]] for local development</br></br>[[Wikibot#TODO]]: implement n-back archiving of threads and previous posts, the parser already supports itious posts, the parser already supports it)
  • Discord Messages#sneakers-the-rat-22-12-12 20:53:43  + ([[Mastodon/Mathjax]]: information in this [[Mastodon/Mathjax]]: information in this thread about different possible implementation approaches</br></br>[[Mastodon/Hacking#Dev Environment]]: Details on setting up [[Vagrant]] for local development</br></br>[[Wikibot#TODO]]: implement n-back archiving of threads and previous posts, the parser already supports itious posts, the parser already supports it)
  • WikiBot#sneakers-the-rat-22-12-15 22:57:13  + ([[Mastodon/Tech WG#TODO]]: - Fix semantic[[Mastodon/Tech WG#TODO]]: </br>- Fix semantic wikilinks in the [[WikiBot#TODO]], </br>- Allow `:` prefixed wikilinks to link to a page without embedding the post in that page (and then ofc stripping the colon) - this would trade off with n-back wikilinks because it wouldn't make sense to archive a series of posts at the same time as not embedding the posts into a pageime as not embedding the posts into a page)
  • Discord Messages#sneakers-the-rat-22-12-15 22:57:13  + ([[Mastodon/Tech WG#TODO]]: - Fix semantic[[Mastodon/Tech WG#TODO]]: </br>- Fix semantic wikilinks in the [[WikiBot#TODO]], </br>- Allow `:` prefixed wikilinks to link to a page without embedding the post in that page (and then ofc stripping the colon) - this would trade off with n-back wikilinks because it wouldn't make sense to archive a series of posts at the same time as not embedding the posts into a pageime as not embedding the posts into a page)
  • Discord Messages#sneakers-the-rat-23-05-20 06:08:40  + ([[Tech WG/Ops Diary#23-05-19]]: [[TODO]] c[[Tech WG/Ops Diary#23-05-19]]: [[TODO]] check out how user-specific settings were reformatted re: config/settings.yml. See also https://discord.com/channels/1049136631065628772/1049184335514828860/1109359788602707988 and https://discord.com/channels/1049136631065628772/1049184335514828860/110936074243355854872/1049184335514828860/1109360742433558548)
  • TODO#sneakers-the-rat-23-05-20 06:08:40  + ([[Tech WG/Ops Diary#23-05-19]]: [[TODO]] c[[Tech WG/Ops Diary#23-05-19]]: [[TODO]] check out how user-specific settings were reformatted re: config/settings.yml. See also https://discord.com/channels/1049136631065628772/1049184335514828860/1109359788602707988 and https://discord.com/channels/1049136631065628772/1049184335514828860/110936074243355854872/1049184335514828860/1109360742433558548)
  • Tech WG/Ops Diary#sneakers-the-rat-23-05-20 06:08:40  + ([[Tech WG/Ops Diary#23-05-19]]: [[TODO]] c[[Tech WG/Ops Diary#23-05-19]]: [[TODO]] check out how user-specific settings were reformatted re: config/settings.yml. See also https://discord.com/channels/1049136631065628772/1049184335514828860/1109359788602707988 and https://discord.com/channels/1049136631065628772/1049184335514828860/110936074243355854872/1049184335514828860/1109360742433558548)