Property:Contains text
D
[[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 +
[[Mastodon/Tech WG#TODO]]: Change the favicon i have way too many instances open in my tabs for this +
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? +
this week is a good week to finish our rules, instance description, invite statement and make a mass coordinated announcement ♥️♥️♥️😘😘😘
in cooperation, towards information liberation!!!!!
pls join us in conversations in <#1050561894752198706> if you are so inclined 🙂
[[Mastodon/Seed Council#TODO]]
https://open.spotify.com/track/0fEasSvs63eKApKfYbi2uD +
[[Mastodon/Tech WG#Project Ideas]]: Collapse long lists of @'s in posts. see https://scholar.social/@neuralreckoning/109501954921707960 +
[[Mastodon/Mathjax]]: information in this thread about different possible implementation approaches
[[Mastodon/Hacking#Dev Environment]]: Details on setting up [[Vagrant]] for local development
[[Wikibot#TODO]]: implement n-back archiving of threads and previous posts, the parser already supports it +
[[Mastodon/Tech WG#TODO]]
[[Mastodon/Storage#TODO]] investigate [[Wasabi]] for storage 🙂 +
[[Mastodon/Tech WG#TODO]] change default email notifications to turn off new follow notifs +
[[Mastodon/Social WG#TODO]]: Once we have rules and about and more of a mod team set up we should ask to be put on fediscience's instance list [[Fediverse Indexes]] +
[[Mastodon/Tech WG#TODO]]:
- Fix semantic wikilinks in the [[WikiBot#TODO]],
- 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 page +
[[Mastodon/Rate Limits]]: For the record the rate limits are
- Per account and per IP: 300 requests per 5 minutes
- Upload media: 30 times in 30 minutes
- Delete posts: 30 times in 30 minutes
- Creating accounts: 5 times in 30 minutes.
https://docs.joinmastodon.org/api/rate-limits/
and a lot of methods through the UI call the API under the hood +
For the moment, until we decide on a different model, neuromatch bears the costs of the instance. Though we trust neuromatch to not abuse that power, one question we should answer as a community is whether we want to move to a fully cooperative model where the members of the instance support its costs so it is truly member-owned and operated. That would likely look like some sliding scale model where members are encouraged to pay what they can, a rough guideline based on nothing but vibes might be:
- $0/mo for students/people making <$50k annually
- $1/mo for postdocs/people making <$75k annually
- $5/mo for PIs/people making >$75k annually
though this would be something we would determine based on how many members we have and how much the instance costs to run. If we were to do this, then we would use opencollective to make our finances transparent.
We could also do a hybrid model where neuromatch kicks in some defined contribution and the members donate the rest, or if we establish a financial working group we could collectively apply for grants with neuromatch as a fiscal sponsor.
Another benefit is that by having some financial surplus we would be able to pay stipends to people who volunteer for mod duty/being on call for tech emergencies.
In the meantime though, mostly so the <#1049184335514828860> knows what it's working with: what kind of costs is neuromatch willing to bear? eg. upgrading to a 16GB ram node with 8 dedicated CPUs would be $120/month but would probably be as much scale as we need for the indefinite future. Currently we are going to upgrade to an 8GB ram node at $60/month, which is already $720 annually (just for the instance, we are also running another node that will host the wiki and loomio)
<@215274946560131074>
[[Mastodon/Finances]] +
OK [[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] +
[[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 +
[[Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram]] Mission accomplished. by god we've done it +
[[Mastodon/Tech WG#TODO]]: increase the size of collapsed messages: https://neuromatch.social/@PessoaBrain/109530080695260906 +
[[Mastodon/Tech WG#TODO]] [[Translation]] services! can we do something like Kolektiva does: https://kolektiva.social/@subMedia/109531114768269437 isn't there some fancy new offline/self-contained translation network thing??? I don't want to make any calls to Google from the instance but translation would be great +
[[Mastodon/Tech WG#TODO]]: why are follow buttons not present for all instances for user accounts on the notification feed? +
so! the "local" feed is the one that shows all the toots from our instance, the "federated" feed shows all toots from everyone that everyone on the instance follow. "local-only toots" are a special feature of glitch-soc where you can make your post *only* visible to the other members of the instance (in base masto you can only limit to mentioned accounts or followers). Local feed also will show you boosts from people on our instance, I'm not sure if there's a way to turn that off but if there isn't there should be bc that would be nice
[[Mastodon/Social WG#TODO]]: guides on how the different [[Mastodon/Feeds]] and [[Mastodon/Post Visibility]] work +
[[Paper Thread Bot]] the thread is here +
[[Paper Thread Bot#Resolving URLs]] https://github.com/CrossRef/event-data-reverse +