Conversation

Notices

1. Angry Sun (sun@shitposter.world)'s status on Tuesday, 17-Dec-2024 07:16:07 JST Angry Sun
   If you want to federate with misskey.io, UPDATE YOUR PLEROMA/AKKOMA
   • :blank: (i@declin.eu)'s status on Tuesday, 17-Dec-2024 07:16:03 JST :blank:

     in reply to

     • kirby
     @kirby @sun https://git.pleroma.social/pleroma/pleroma/-/commits/v2.7.1
   • kirby (kirby@freerobuxextremist.com)'s status on Tuesday, 17-Dec-2024 07:16:07 JST kirby

     in reply to
     @sun what's the commit I have to cherrypick to fix this one
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: repeated this.
   • † top dog :pedomustdie: (dcc@annihilation.social)'s status on Tuesday, 17-Dec-2024 07:16:58 JST † top dog :pedomustdie:

     in reply to
     @sun :alex_lol:
   • † top dog :pedomustdie: (dcc@annihilation.social)'s status on Tuesday, 17-Dec-2024 07:18:11 JST † top dog :pedomustdie:

     in reply to

     • † top dog :pedomustdie:
     @sun No i will keep my ability to follow (i also have a custom node info)
   • :blank: (i@declin.eu)'s status on Tuesday, 17-Dec-2024 07:20:17 JST :blank:

     in reply to

     • † top dog :pedomustdie:
     @dcc @sun develop and the new hot fix already fix the follow issue
     † top dog :pedomustdie: likes this.
   • Phantasm (phnt@fluffytail.org)'s status on Tuesday, 17-Dec-2024 07:22:30 JST Phantasm

     in reply to

     • kirby
     @kirby @sun
     https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4220 and https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4253
     
     The first one should truncate the offending user fields as Misskey allows a stupid amount which would cause a reject and a refetch
     The second makes the "refetch" jobs unique meaning it prevents a flood of requests in the future.
     † top dog :pedomustdie: likes this.
   • Phantasm (phnt@fluffytail.org)'s status on Tuesday, 17-Dec-2024 07:23:04 JST Phantasm

     in reply to

     • † top dog :pedomustdie:
     • :blank:
     @i @dcc @sun 2.7.1 does not fix the follow stuck pending issue.
     † top dog :pedomustdie: likes this.
   • † top dog :pedomustdie: (dcc@annihilation.social)'s status on Tuesday, 17-Dec-2024 07:23:12 JST † top dog :pedomustdie:

     in reply to

     • :blank:
     @i @sun (i also don't plan to rebase for devop) i need to figure out a better way to patch before i upgrade again.
   • † top dog :pedomustdie: (dcc@annihilation.social)'s status on Tuesday, 17-Dec-2024 07:26:58 JST † top dog :pedomustdie:

     in reply to

     • :blank:
     • Phantasm
     @i @phnt @sun Never upgrade unless needed.
   • :blank: (i@declin.eu)'s status on Tuesday, 17-Dec-2024 07:26:59 JST :blank:

     in reply to

     • † top dog :pedomustdie:
     • Phantasm
     @phnt @dcc @sun ah right, the other patch is still in develop, fucking lain
   • :blank: (i@declin.eu)'s status on Tuesday, 17-Dec-2024 07:31:01 JST :blank:

     in reply to

     • † top dog :pedomustdie:
     @dcc @sun export your diffs to some folder, pull in a fresh copy, and reapply them
     
     even my mess of changes takes a few minutes to reapply
     † top dog :pedomustdie: likes this.
   • Phantasm (phnt@fluffytail.org)'s status on Tuesday, 17-Dec-2024 07:32:55 JST Phantasm

     in reply to

     • † top dog :pedomustdie:
     • :blank:
     @i @dcc @sun It's also funny that they want to block Pleroma and Akkoma because of this, because they already mitigated this flood of requests issue months ago by sending 429s.
     
     The issue they talked about a week or two ago as the reason is an increase in traffic when it comes to custom emojis. Which also makes complete sense as Pleroma and Akkoma are basically the only mainstream servers that support them. And Pleroma already stores the emojis in a media proxy cache.
     
     Instead of fixing their own issues they themselves created (more custom emoji than there are kanji), they try to pin it on others.
     † top dog :pedomustdie: likes this.
   • Phantasm (phnt@fluffytail.org)'s status on Tuesday, 17-Dec-2024 07:42:59 JST Phantasm

     in reply to

     • † top dog :pedomustdie:
     • :blank:
     • Phantasm
     • kirby

     @i @dcc @sun Also worth noting that they block it automatically by version number instead of activating the block only when they get flooded. Everyone that has it patched manually must apparently also change the version string.

     Complete clown world.

     fluffytail pleroma.sh[]: [error] Object rejected while fetching https://misskey.io/notes/a1uz0fx8ipq219pz {:fetch, {:error, :forbidden}}

     cc @kirby

     
     image.png
     † top dog :pedomustdie: likes this.
   • Angry Sun (sun@shitposter.world)'s status on Tuesday, 17-Dec-2024 08:05:31 JST Angry Sun

     in reply to

     • † top dog :pedomustdie:
     • :blank:
     • Phantasm
     @i @dcc @phnt hear me out what if http just isn't good for the amount of traffic servers shit around
     † top dog :pedomustdie: likes this.
   • :blank: (i@declin.eu)'s status on Tuesday, 17-Dec-2024 08:05:32 JST :blank:

     in reply to

     • † top dog :pedomustdie:
     • :blank:
     • Phantasm
     @phnt @dcc @sun not using the shared inbox for everything on this fuck ass network and it's consequences, this shit is never going to be email
   • :blank: (i@declin.eu)'s status on Tuesday, 17-Dec-2024 08:05:33 JST :blank:

     in reply to

     • † top dog :pedomustdie:
     • Phantasm
     @phnt @dcc @sun posts don't have the associated emoji included, but emoji can have dozens of tagged profiles that pleroma will try to pull if you're downstream of the thread
     
     select count(*), jsonb_array_length(data->'tag') from activities where data->>'type' = 'EmojiReact' group by jsonb_array_length(data->'tag') order by jsonb_array_length(data->'tag') desc;
     
     and yes the pinned post fetching is problematic too, because it's another area where you have a persistent retry loop whenever the profile caches out for a refetch
   • Phantasm (phnt@fluffytail.org)'s status on Tuesday, 17-Dec-2024 08:05:34 JST Phantasm

     in reply to

     • † top dog :pedomustdie:
     • :blank:
     @i @dcc @sun I think it was the other way around. A profile got fetched, ReceiveWorker started to pull the pinned posts which included a stupid amount of custom emoji (usually the full post was made of them), it failed and added the job back to the oban queue, and repeated the same thing again until it got a 429 which still didn't kill the constantly adding jobs.
     
     At least that's what I think happened when I ran into this months ago.
   • :blank: (i@declin.eu)'s status on Tuesday, 17-Dec-2024 08:05:35 JST :blank:

     in reply to

     • † top dog :pedomustdie:
     • Phantasm
     @phnt @dcc @sun sending a 429 from javascript instead of cloudflare has a cost too, it's not their fault pleroma is stuck in a development ditch either
     
     emojis pull in profiles, those profiles create an infinite amount of duplicate jobs, pleroma spin locks on them, while the emoji itself is never seen
   • :blank: (i@declin.eu)'s status on Tuesday, 17-Dec-2024 08:47:45 JST :blank:

     in reply to

     • † top dog :pedomustdie:
     • Phantasm
     @sun @dcc @phnt the big word here is supports, the network doesn't do any batching at large, but it could
     
     https://github.com/mastodon/mastodon/blob/main/app/services/activitypub/process_collection_service.rb
     
     we could be syncing hundred of posts a time from a shared outbox with a cursor abstraction, but instead it's hope the other party knows they're on a federated network and honors your follow request and also never messes up anything
   • Angry Sun (sun@shitposter.world)'s status on Tuesday, 17-Dec-2024 08:47:46 JST Angry Sun

     in reply to

     • † top dog :pedomustdie:
     • :blank:
     • Phantasm
     @i @dcc @phnt I wasn't aware Mastodon did this, I'm actually a little confused, it just bundles multiple sharedinbox posts into one post? what's the benefit if you're using http/2?
   • :blank: (i@declin.eu)'s status on Tuesday, 17-Dec-2024 08:47:47 JST :blank:

     in reply to

     • † top dog :pedomustdie:
     • Phantasm
     @sun @dcc @phnt it's fine, but only mastodon supports ingesting a collection instead of a single activity at a time
     
     we could have eventual sync or streaming api instead, but that's too close to nostr/bluesky
   • Angry Sun (sun@shitposter.world)'s status on Tuesday, 17-Dec-2024 08:48:08 JST Angry Sun

     in reply to

     • † top dog :pedomustdie:
     • :blank:
     • Phantasm
     @i @dcc @phnt oh I see, so you suggest that there's one endpoint and an entire server subscribes to all its follows on the other server, which the remote server keeps track of and like batches up every request in the last 30 seconds or something and posts at once.
   • 御園はくい (hakui@tuusin.misono-ya.info)'s status on Tuesday, 17-Dec-2024 10:38:31 JST 御園はくい

     in reply to

     • † top dog :pedomustdie:
     • :blank:
     • Phantasm
     • kirby
     @phnt @dcc @i @kirby @sun ok well at least they didn't outright block every single server like they threatened to do previously
     † top dog :pedomustdie: likes this.