1,035
edits
Discord Messages: Difference between revisions
→24-04-10: new section
(→23-10-06: new section) |
(→24-04-10: new section) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1,074: | Line 1,074: | ||
[[Mastodon/Hacks]] | [[Mastodon/Hacks]] | ||
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1159969748226953216 | |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 | |||
}} | }} | ||