neuromatch

Discord Messages: Difference between revisions

Discord Messages (view source)

Revision as of 17:38, 10 April 2024

21,168 bytes added ,  10 April
→‎24-04-10: new section
(→‎23-08-01: new section)
(→‎24-04-10: new section)
 
(21 intermediate revisions by the same user not shown)
Line 908: Line 908:
|Text=[[Server Costs and Invoices]]: Invoice for July, 2023 - USD 106.00
|Text=[[Server Costs and Invoices]]: Invoice for July, 2023 - USD 106.00
|Link=https://discord.com/channels/1049136631065628772/1060187061811945542/1135939081914830928
|Link=https://discord.com/channels/1049136631065628772/1060187061811945542/1135939081914830928
}}
== 23-08-16 ==
{{Message
|Author=mannazsci
|Avatar=https://cdn.discordapp.com/avatars/540104559079456770/12ce492294d6a3cd6f1ea00cbe8edb04.png?size=1024
|Date Sent=23-08-16 04:11:30
|Channel=technical-wg
|Text=[[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;`
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1141222683388956812
}}
== 23-08-27 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=23-08-27 22:00:20
|Channel=technical-wg
|Text=Also saw you boosted this,  seems like a great idea for [[Translation]]
https://frontrange.co/@raineer/110959799057137486
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1145477929812361237
}}
== 23-08-30 ==
{{Message
|Author=mannazsci
|Avatar=https://cdn.discordapp.com/avatars/540104559079456770/12ce492294d6a3cd6f1ea00cbe8edb04.png?size=1024
|Date Sent=23-08-30 08:45:21
|Channel=Technical Working Group - membership rules, roles, responsibilities, access levels
|Text=[[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
|Link=https://discord.com/channels/1049136631065628772/1146361083251138702/1146365031152369704
}}
== 23-09-01 ==
{{Message
|Author=mannazsci
|Avatar=https://cdn.discordapp.com/avatars/540104559079456770/12ce492294d6a3cd6f1ea00cbe8edb04.png?size=1024
|Date Sent=23-09-01 12:43:01
|Channel=Server costs and invoices
|Text=[[Server Costs and Invoices]]: Invoice for Aug, 2023 - USD 106.00
|Link=https://discord.com/channels/1049136631065628772/1060187061811945542/1147149614374453291
}}
== 23-09-20 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=23-09-20 02:55:44
|Channel=techwg-ops
|Text=[[Tech WG/Ops Diary#23-09-19]] - Upgrading to 4.2-RC2 while trying to write the [[Upgrade Mastodon]] docs. currently doing the merge from upstream and noticing db migrations for exclusive lists failing, but not fixing now because that would put the fixes in the `glitch-soc-main` branch which is a local mirror of upstream which gets force pushed. Seems like that should happen in the `merge-upstream` branch after upstream is merged
|Link=https://discord.com/channels/1049136631065628772/1052452072806686751/1153887188946268211
}}
== 23-09-21 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=23-09-21 21:37:59
|Channel=technical-wg
|Text=Btw I noticed we don't have [[Unattended Upgrades]] turned on to automatically keep system-level packages up to date. I usually do that with servers I manage because i have been told by security ppl that keeping up to date is like most of what matters with day-to-say security probs, but i mean it seems like it could uh accidentally break a package one day and kill the instance, so idk if there's a reason to not do that but thought i'd ask
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1154532004071747664
}}
== 23-09-26 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=23-09-26 21:29:58
|Channel=questions
|Text=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
|Link=https://discord.com/channels/1049136631065628772/1049184383220846693/1156341922357579796
}}{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=23-09-26 21:34:40
|Channel=questions
|Text=BTW since we have lotsa new people here, when I make a [[Wikilink]] we have a bot that copies your message to the wiki so we can capture discussion contextually and refine it later. Eg. In this case that previous message went here: https://wiki.neuromatch.io/Consensus#Discord
|Link=https://discord.com/channels/1049136631065628772/1049184383220846693/1156343105289719838
}}
== 23-09-27 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=23-09-27 23:54:40
|Channel=honorary members
|Text=I 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?
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.
If I dont hear anything in a day or so ill invite them!
|Link=https://discord.com/channels/1049136631065628772/1156740725564784731/1156740725564784731
}}
== 23-10-01 ==
{{Message
|Author=mannazsci
|Avatar=https://cdn.discordapp.com/avatars/540104559079456770/12ce492294d6a3cd6f1ea00cbe8edb04.png?size=1024
|Date Sent=23-10-01 07:44:40
|Channel=techwg-ops
|Text=[[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.
|Link=https://discord.com/channels/1049136631065628772/1052452072806686751/1157946171432632383
}}
== 23-10-06 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=23-10-06 21:45:39
|Channel=technical-wg
|Text=So idle thought,  i saw someone whose instance had [[Slugified URLs]] for posts, ( eg. https://neuromatch.social/@Jonny /my-post-title )
And it looks like it would be pretty easy to do...
- add a `slug` db column in the statuses table
- add a route using `slug` https://github.com/mastodon/mastodon/blob/3262d1f1b62a984343f0f6c67c1d18921daabb0a/config/routes.rb#L130
- 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)
- add API endpoint to check if slug exists
- add button in "share" dropdown to copy slugified link
- optionally: provide an auto-slug option that slugifies the first n unique characters in a post, or parses a leading # header
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
[[Mastodon/Hacks]]
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1159969748226953216
}}
== 23-10-27 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=23-10-27 02:29:48
|Channel=elasticsearch
|Text=OK yet again starting thread on getting [[ElasticSearch]] running
|Link=https://discord.com/channels/1049136631065628772/1167287930742652958/1167289017205792969
}}
== 23-12-05 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=23-12-05 06:58:02
|Channel=onboarding and instance docs
|Text=OK <@318247805124870145> i'm doing a little wiki gardening rn and here i'll narrate a little of what i'm doing as i do it to give you a sense of what that looks like:
first i am reading this and wondering how i could offer part of this to you, and with this set of prompts and with ur previous comments about 'where do i even start with this thing' which are extremely justified i want to make a 'how to get started with masto as software' page, so I go to where we have previously put such things on the Tech WG page (https://wiki.neuromatch.social/Tech_WG ) and add a link there to a new [[Intro To Mastohacking]] page ( https://wiki.neuromatch.social/Intro_To_Mastohacking ) since i figure "intro to mastodon" is too much like our general getting started on fedi pages. idk we can always change it later.
So then i do a search for "docs" to see where else we might have written stuff like this and lo and behold there's also a page for that, so i add a link from there too: https://wiki.neuromatch.social/Mastodon/Docs
then i start my new page by adding categories and backlinks. Don't worry about the syntax for right now, but what i'm doing here is making this page findable in a few different ways - by navigating from related pages, formally through the semantic relationship `Part Of`, and then also via the category system (which we can also query to eg. display a list of all pages in the "hacking" and "guide" categories if we want to make some automatic index, but i digress).
nothing on the page yet but that? fuck it, save page. we can keep saving as we update, no need to be shy on wiki
(sorry for notifs el i'm going to split this up into a few messages so i can intersperse images)
|Link=https://discord.com/channels/1049136631065628772/1179563696830292069/1181489645989666916
}}
== 24-01-09 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=24-01-09 02:48:18
|Channel=technical-wg
|Text=quick aside for <@540104559079456770> if she gets a second, can u add some DNS records for meeeee???
- `A` record pointing `feeds` subdomain to `45.56.100.144`
- `A` record pointing `dev.feeds` subdomain to `45.56.100.144`
- `AAAA` pointing `feeds` subdomain to `2600:3c03::f03c:93ff:feca:b20f`
- `AAAA` pointing `dev.feeds` subdomain to `2600:3c03::f03c:93ff:feca:b20f`
That's the [[Linode/Loomio]] node, not the [[Linode/Mastodon]] node, so i won't be draining resources. want to start running a dev version of [[paper-feeds]] to test against actual RSS readers and also test federation when we get to activitypub. https://github.com/sneakers-the-rat/paper-feeds/
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1194110371468955779
}}{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=24-01-09 04:53:38
|Channel=technical-wg
|Text=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)
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1194141912433692802
}}
== 24-01-15 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=24-01-15 03:31:15
|Channel=social-wg
|Text=i can't remember where we left off w.r.t. enabling [[trends]] on the instance, i can't think of a strong reason to leave them disabled, but does anyone have feelings about this?
|Link=https://discord.com/channels/1049136631065628772/1049184264832417823/1196295509913112658
}}
== 24-01-17 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=24-01-17 10:58:31
|Channel=Sticky Posts & Discussions
|Text=ok 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.
here's one idea of what that might look like:
v1
- 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.
- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post
- sticky posts come from an autofollowed @ discussions account
- ... are local only posts
- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed
- ... 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
questions:
- can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'
- should stickies have a time limit? or just a mechanism to close them in governance process?
v2
a) The threading interface on the web interface is awful,
b) it would be nice to be able to show a title on a minimized sticky post
c) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike way
so
- posts can have titles
- titles are declared with a special "title" field in the web ui
- or with a first line beginning with a # from other clients, a la markdown
- replies with titles can be minimized too
- replies with titles are sorted first (bc they can be minimized)
[[Hacks]]
|Link=https://discord.com/channels/1049136631065628772/1197132841901899827/1197132841901899827
}}
== 24-01-20 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=24-01-20 05:20:06
|Channel=Path to independence - setting up a coop/legal entity
|Text=Also that reminds me that I did get the announcement notif but the interface opened starting with the first announcement not the most recent one so [[TODO]]
|Link=https://discord.com/channels/1049136631065628772/1195038837865451600/1198134840290197634
}}
== 24-02-02 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=24-02-02 01:16:50
|Channel=techwg-ops
|Text=[[Tech WG/Ops Diary#24-02-01]] - Patching some mysterious critical security vuln thread
|Link=https://discord.com/channels/1049136631065628772/1052452072806686751/1202784662397911150
}}
== 24-02-16 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=24-02-16 23:01:41
|Channel=technical-wg
|Text=ok so they refactored all the css, and it was pretty hard to track down what in the heck was changed, so here is another [[Lessons We Gone And Learned From Maintaining A Fork Of A Fork]] - patching is good, editing in place can be fragile. i moved the custom styles from better code blocks and expanded status previews to their own set of stub scss files that then get imported at the end of the scss index, so they should override conflicting rules set previously. that keeps them nice and separate and survivable in the case of big refactorings. this is similar to the "flavours" system which takes whatever isn't overridden from base masto. i can't run the dev server rn bc my brother is in town but since these are just css changes we can uh test in prod i think
https://github.com/NeuromatchAcademy/mastodon/commit/8e54a6bf891ff855104225032dd9ccfb0163acea
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1208186470678929448
}}
== 24-02-17 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=24-02-17 22:16:31
|Channel=techwg-ops
|Text=[[Tech WG/Ops Diary#24-02-14]] - Patching two more security bugs thread!
|Link=https://discord.com/channels/1049136631065628772/1052452072806686751/1208537492802904064
}}
== 24-04-10 ==
{{Message
|Author=sneakers.the.rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=24-04-10 21:38:20
|Channel=technical-wg
|Text=Also lets do dis [[robots.txt]]
https://darkvisitors.com/
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1227734440357269504
}}
}}
Retrieved from "https://wiki.neuromatch.social/Special:MobileDiff/841...1223"