Property:Contains text
A
[[Access_Policy]] for
- Server shell access : root, user
- Git repo access: admin, maintain, write, triage, read
- email accounts: admin@ noreply@
- Mastodon Admin portal
- Mastodon @admin account
- Mastodon @techwg account
- Sendgrid
- Loomio
- Wiki
- DNS (neuromatch.social)
- Discord mod chat : discord roles until we move away from discord
Based on the access policy we decide, we would need to update access and note that on this page: https://wiki.neuromatch.io/Administrators +
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]] +
[[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Following the instructions to
* [[Resizing Linode]] [[Linode]]: https://www.linode.com/docs/guides/resizing-a-linode/
* [[Mastodon/Admin#Shutdown]]: https://docs.joinmastodon.org/admin/migrating/ from the migraing docs +
@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 ❤️ 🙏 +
[[Autofollow]]: Make all new accounts follow a a comma-separated list of account handles given in the .env file 🙂 +
B
ok [[Tech WG/Ops Diary#23-03-29]]: going to pull in dev branch and deploy to tha server: https://github.com/NeuromatchAcademy/mastodon/pull/13
I thought this had fetch all replies in it but i need to rebase it and also now that we know how to write them i want to write some tests....
It does have [[Better Code Blocks]] in it from <@485848481995423755> : https://github.com/NeuromatchAcademy/mastodon/pull/9
wish e luck +
C
NMA is from July 10-28, [[Climatematch Academy]] [[CMA]] is for 2 weeks from July 17-28. Not sure about NMC dates for this year. +
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 ) +
NMA is from July 10-28, [[Climatematch Academy]] [[CMA]] is for 2 weeks from July 17-28. Not sure about NMC dates for this year. +
<@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]] +
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
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.
A block means something different than voting in a few ways, including that blocks should be rare: consensus sort of inverts the decisionmaking process, where care should be taken to discuss with the membership and refine a proposal before, rather than after making the proposal - so in a majoritarian system one might make a proposal and make an argument in favor, people discuss in the comments and then make up their minds there. The purpose of requiring discussion beforehand is to make more space for everyone to craft the proposal in the first place, register concerns, etc. So if people are blocking a proposal, that is a sign that the process has failed (as opposed to in a majoritarian system that the proposal has failed).
Blocking also typically enjoins the person blocking to help remedy the reason for their block: if a proposal is being made in good faith, we assume that it is meeting some unmet need by the proposer/other members. If someone blocks a proposal, that will mean that it might cause them or the organization harm, but those unmet needs still remain - so it's basically like conflict res at that point. Ofc there are exceptions like not making marginalized ppl do additional labor, etc. +
Yes! Good question!!!!! Thats one of the basic [[Consensus]] questions - good for me vs. Good for the group. Good for both is ideal ofc, but "bad for me, good for the group" is the real meat of the problem. There's a couple of different flavors there. Is bad for me something thats actively bad, something that will have negative felt effects on me, or is it something that just isnt good for me, something I wont feel the positive effects of? Also, is "bad for me" a symptom of "bad for the group" in that the decision is exclusionary/the negative impacts predominately fall on a particular group? In this case, does being able to opt out alleviate concerns you have, or is there something larger you're objecting to beyond that? Few decisions are universally good for everyone, so were your concerns heard and weighed as part of the discussion? How that translates to a vote can be a little tricky/subjective, but in general if there are no active harmful effects, just absence of benefit for you then that would be a vote yes with caveat. Other consensus systems have a "stand aside" which is "if the rest of the group thinks this is good then I'll go with it, but I have some problem with the decision as a whole beyond how it impacts me" where a certain number of stand asides equal a block - doing something everyone feels lukewarm about is not great consensus. We could make abstentions mean that if that makes sense, altho an abstain means something slightly different ("I dont have enough information here but that wasnt the fault of the process" or "this us wholly irrelevant to me" or "I have some conflict of interest"). If you feel like this would have negative impacts on you that you feel like weren't seriously addressed during the discussion, or arent reflected in the outcome, then vote no.
Thats all my interpretation, not gospel or True, and the "meaning of votes" being somewhat up to interpretation and variable between systems is one of the things that makes consensus messy
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) +
D
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]] +
re: [[PaperBot]] we also had talked about [[DOI Search]] and resolving urls to DOIs and embedding them in the [[JSON-LD]]. the DOI Search should actually be super easy if we do it by altering the hashtag regex. doing it by making it an additional search type would take a little more, as would doing automatic dereferencing, but all those sound like fun to me +
[[Mastodon/Tech WG#TODO]] [[Mastodon/Social WG#TODO]] Look into setting up Relays https://neuromatch.social/@manisha/109523786200081610 +
[[Mastodon/Tech WG#Done]] changed default email notifications in config/settings.yml to turn off new follow notifs and restarted services +
[[Tech WG/Ops Diary#23-01-20 Installed NTP to sync system clock]] This was done to resolve a 2FA issue involving Authy (a TOTP app) https://discord.com/channels/1049136631065628772/1049184335514828860/1065990577381974067 +
NMA is from July 10-28, [[Climatematch Academy]] [[CMA]] is for 2 weeks from July 17-28. Not sure about NMC dates for this year. +
[[Tech WG/Ops Diary#23-04-25]]: restarted systems services as we were hitting swap limits https://neuromatch.social/@manisha/110259466647197417 +
[[Mastodon/Social WG]] Getting hit with a lot of crypto spam reports from mastodon.social today. Some instances are temporarily limiting m.s till their mods wake up. +
Those are great ideas!! We'd shared some of these on the NM conference channel as well and there is definitely some interest around it. So this is exciting!
> forum mode! one thing I would love is for NMS to be a place where non-neuroscientists can come and ask questions of neuroscientists...
Yess! I've also been thinking of how to break down the barriers between scientists and non-scientists in general and for the NM and climatematch communities. Currently if anyone wants to be a part of the NM/CM community they need to be actively involved with it somehow -- as a student/TA/conference presenter/organizer/mentor/volunteer/... but with NMS anyone whose interests and values align is welcome to join us and hang out with a bunch of scientists. NMS is a low barrier entry to the community and expands the scope of the community!
I think forums would be great for the [[Knowledge Group]] [[Knowledge Club]] that we've discussed [here](https://discord.com/channels/1049136631065628772/1049184264832417823/1106307113359265932) and looks like there is interest for it in even outside of neuroscience (on the same thread that Jonny linked earlier -- https://weirder.earth/@dessertgeek/110460194256055941 and my response https://neuromatch.social/@manisha/110463002047148596).
The only thing with forum mode is we'd need to figure out how to basically take lemmy's code and make it work with masto. Easiest would be to host it as a separate forum.neuromatch.social subdomain but it would be awesome if folks didn't have to create a separate account for that. We could ask for funding to implement the forum mode with DIY stuff where we hack it to make it work with masto accounts?? does that seem feasible? +
[[Server Costs and Invoices]]: Invoice for May, 2023 +
[[Tech WG/Ops Diary#23-06-27]]: restarted systems services as we were hitting swap limits https://neuromatch.social/@manisha/110616054514875151 This time I remembered to take a screenshot before and after +
[[Server Costs and Invoices]]: Invoice for June, 2023 +
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 +
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 PII +
Thank you El and welcome onboard!! woohoo!! 🥳 ❤️ 💚 💜 💙 🧡
[[Social WG/Responsibilities]] continued: with great power comes great responsibility :)
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 :) )
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>)
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.
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. +
[[Tech WG/Ops Diary#23-07-07]]: masto 4.1.3 update -- security patch. Jonny's on the road so Lina and Manisha are going to give this a try. If we muck something up, please be kind 🥺 starting by making a linode backup and then following instructions on ...
oh wait! dang they already released 4.1.4 just an hour ago
https://github.com/mastodon/mastodon/releases/tag/v4.1.4
4.1.3 from yesterday: https://github.com/mastodon/mastodon/releases/tag/v4.1.3 +
@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 ❤️ 🙏 +
[[Tech WG/Ops Diary#23-07-09]]: Updating reverse proxy config to the recommended one
as root
`cd /etc/nginx
cd site-enabled
vim mastodon`
search for "system"
added the following two headers in that block as per the release notes:
`add_header X-Content-Type-Options nosniff;
add_header Content-Security-Policy "default-src 'none'; form-action 'none'"; `
save
test nginx configs are valid or not (w/o running)
`nginx -t `
all looked good
`nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
`
Reload nginx +
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 again +
[[Server Costs and Invoices]]: Invoice for July, 2023 - USD 106.00 +
[[Mastodon/Setup]] useful commands to improve disk usage:
`# Prune remote accounts that never interacted with a local user
RAILS_ENV=production /home/mastodon/live/bin/tootctl accounts prune;
# Remove remote statuses that local users never interacted with older than 4 days
RAILS_ENV=production /home/mastodon/live/bin/tootctl statuses remove --days 4;
# Remove media attachments older than 4 days
RAILS_ENV=production /home/mastodon/live/bin/tootctl media remove --days 4;
# Remove all headers (including people I follow)
RAILS_ENV=production /home/mastodon/live/bin/tootctl media remove --remove-headers --include-follows --days 0;
# Remove link previews older than 4 days
RAILS_ENV=production /home/mastodon/live/bin/tootctl preview_cards remove --days 4;
# Remove files not linked to any post
RAILS_ENV=production /home/mastodon/live/bin/tootctl media remove-orphans;` +
[[Access_Policy]] for
- Server shell access : root, user
- Git repo access: admin, maintain, write, triage, read
- email accounts: admin@ noreply@
- Mastodon Admin portal
- Mastodon @admin account
- Mastodon @techwg account
- Sendgrid
- Loomio
- Wiki
- DNS (neuromatch.social)
- Discord mod chat : discord roles until we move away from discord
Based on the access policy we decide, we would need to update access and note that on this page: https://wiki.neuromatch.io/Administrators +
[[Server Costs and Invoices]]: Invoice for Aug, 2023 - USD 106.00 +
[[Tech WG/Ops Diary#23-10-01]] I am ready to deploy v4.2 but I encountered a few issues while following the process mentioned in [[Upgrade_Mastodon]]. I'll update the wiki with the steps I took. +
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 😊 +
[[Testing Wikibot]] +
[[Testing Wikibot]] +
beepalabeep da beep beep [[Here We Go]] +
Beepalabeep da da deep [[Here We Go#Section]] +
Beepaleepalabeep da deep deep [[Here We Go#Theme Song]]: https://youtu.be/7hT04AB1JU4 +
So anyway [[TODO]] Document the [[WikiBot]] +
<@827519038120132608> also re: memory and bridging between the garden and the stream or whatever metaphor ya want, you should check out [[WikiBot#Purpose]] +
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 good +
up to y'all but all I'll say is we did indeed already start one and [[The Wiki Is Happening]] feat. [[The Wiki Waits For No One]] [[WikiParables]] +
[[Wiki/TODO#Onboarding]] Document account migration process, re: https://fediscience.org/@dbarack/109483724167917771 +
[[Wiki#TODO]] Clean up link to [[Wiki/TODO]] and write some docs on [[Wikibot#Usage Patterns]] +
[[Mastodon/Social WG#TODO]] - discuss the [[Defederated Instances#Instances To Discuss]] - decide what we want to do with edge cases/cases where we already had a number of people following people from these instances +