Discord Messages: Difference between revisions
(→23-01-02: new section) |
No edit summary |
||
| Line 415: | Line 415: | ||
[[Mastodon/Tech WG#TODO]] | [[Mastodon/Tech WG#TODO]] | ||
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1059601450793173042 | |Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1059601450793173042 | ||
}}{{Message | |||
|Author=sneakers-the-rat | |||
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024 | |||
|Date Sent=23-01-02 22:39:57 | |||
|Channel=technical-wg | |||
|Text=<@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]] | |||
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1059601974028423230 | |||
}} | }} | ||
Revision as of 18:39, 2 January 2023
22-12-09
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
sneakers-the-rat#This is a test. Forum channels are new to discord. Let's test the features together!22-12-09 12:07:42<@827519038120132608> also re: memory and bridging between the garden and the stream or whatever metaphor ya want, you should check out WikiBot#Purpose
sneakers-the-rat#This is a test. Forum channels are new to discord. Let's test the features together!22-12-09 12:10:47as 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
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 😊
22-12-10
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
22-12-12
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/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
22-12-14
Mastodon/Tech WG#TODO Mastodon/Storage#TODO investigate Wasabi for storage 🙂
22-12-15
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
22-12-16
Mastodon/Tech WG#TODO Mastodon/Social WG#TODO Look into setting up Relays https://neuromatch.social/@manisha/109523786200081610
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
22-12-17
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
Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram Following the instructions to
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
22-12-18
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?
22-12-21
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
22-12-22
Mastodon/Tech WG#TODO: Secrets manager/password manager so we can have shared accounts better 🙂
22-12-24
Mastodon/Tech WG#Done changed default email notifications in config/settings.yml to turn off new follow notifs and restarted services
22-12-25
OK Tech WG/Ops Diary#22-12-24 going to pull in a few upgrades: https://github.com/NeuromatchAcademy/mastodon/pull/7
- Mathjax
- Larger Post Previews
- Default false notifications for new follows
- Autofollow accounts
And also pulling in updates from upstream glitch-soc, which in my test run means that we have to upgrade node from 14 to 16
22-12-26
22-12-27
Mastodon/Tech WG#TODO Make a Hacking Masto guide including setting up a Mastodon/Dev Environment and a Hack Merging Policy
also need general Ruby dev stuff, like a Masto Code Structure overview, which I'm feeling more and more capable of doing, and I have been doing on my personal wiki and could export over. still need to figure out how to write tests but yes I think I have gotten the big chunks of how stuff works. the Rails <-> Redux <-> React stuff still sorta eludes me, esp how it's "supposed" to be done in the program because I have more experience with react and you can do a lot of uh web app stuff with it that could also be done with rails (tho a lot of their components are a) written in the old object style which I find sorta clumsy after converting to the function style and b) actually pretty imperative for a declarative framework, which makes stuff difficult)
22-12-29
the DOI thing I think will only take an hour or two more, and then yeah will be adapting some of the WikiBot code that runs on this discord already to do an agora-like thing. I've talked to flancian about this as well a bunch of times, unifying the agora bots and making a general framework for that kind of cross platform linking
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.
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 )
23-01-02
<@540104559079456770> I think you should have permissions to do a code review on the PR itself, do you know how to do one of those? we should add that to the Hack Merging Policy - a guide on how to do code review. Mastodon/Tech WG#TODO
<@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