Conversation

Notices

1. Embed this notice
   Puniko ? (puniko@mk.absturztau.be)'s status on Wednesday, 16-Aug-2023 21:22:56 JST Puniko ?

   if you got affected by the federation killer by akkoma on your *key or firefish instance, there are 2 tables, you'll need to fix the shared inbox on.
   
   one is "sharedInbox" on the "user" table. you can adapt floaty's query quite easily with it, just use "inbox" instead of "ap_id" and map the other fields accordingly
   
   the other place (which is the more important one) is to reset the field "followerSharedInbox" in the "following" tables. i don't have a good query for that, since i only had a couple of entries there which needed fixing. but i'm sure you can figure one out to make the update using a join on the user table or something.
   
   after the fields are updated, federation should work again

   • cool_boy_mew likes this.
   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Wednesday, 16-Aug-2023 21:23:16 JST Puniko ?

     in reply to

     floaty's query here: https://ihatebeinga.live/notice/AYljxEU1p1Z55LwVSS

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Wednesday, 16-Aug-2023 21:26:13 JST Puniko ?

     in reply to

     my adapted query for the "user" table
     
     update "user" set "sharedInbox" = 'https://' || split_part("inbox", '/', 3) || "sharedInbox" where "sharedInbox" = '/inbox';
     
     don't have a general one for the "following" table tho. this is the select i used to check which fields needs changing
     
     select "following"."followerSharedInbox", "following"."followerId", "user"."username", "user"."inbox" from "following" inner join "user" on "following"."followerId" = "user"."id" WHERE "followerSharedInbox" = '/inbox' OR "followeeSharedInbox" = '/inbox';
     
     (yes, i know. i'm a messy query writer)

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Wednesday, 16-Aug-2023 21:27:28 JST Puniko ?

     in reply to

     i actually dont know, if the akkoma bug might also affect the "followeeSharedInbox", i didn't have any result on it

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Wednesday, 16-Aug-2023 21:45:44 JST Puniko ?

     in reply to

     • tastytea

     @tastytea@very.tastytea.de if you don't federate, you are affected. if you federate, you are ok.
     
     also this happens on user by user basis, depending on who is following and stuff. so one user might be able to federate, while another user on the same instance can't.

   • Embed this notice
     tastytea (tastytea@very.tastytea.de)'s status on Wednesday, 16-Aug-2023 21:45:46 JST tastytea

     in reply to

     @puniko@mk.absturztau.be how do i know if i'm affected by the federation killer by akkoma? :neocat_think_googly:

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Wednesday, 16-Aug-2023 21:47:00 JST Puniko ?

     in reply to

     • tastytea

     @tastytea@very.tastytea.de also you can check using psql directly on the database using the second query in this post
     
     RE: https://mk.absturztau.be/notes/9ih9t9vtyxippfgy

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Wednesday, 16-Aug-2023 21:49:02 JST Puniko ?

     in reply to

     • tastytea

     @tastytea@very.tastytea.de no, it wouldn't show up at all in queue. at least it was the case for me. its like your post will never generate jobs

   • Embed this notice
     tastytea (tastytea@very.tastytea.de)'s status on Wednesday, 16-Aug-2023 21:49:03 JST tastytea

     in reply to

     @puniko@mk.absturztau.be it would show up in the delayed queue, right?

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Wednesday, 16-Aug-2023 22:06:23 JST Puniko ?

     in reply to

     • tastytea

     @tastytea@very.tastytea.de :neocat_think_woozy: i mean, your posts federated to here, so i didn't expect anything else

   • Embed this notice
     tastytea (tastytea@very.tastytea.de)'s status on Wednesday, 16-Aug-2023 22:06:24 JST tastytea

     in reply to

     @puniko@mk.absturztau.be 0 rows :blob_relieved:

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Wednesday, 16-Aug-2023 22:11:39 JST Puniko ?

     in reply to

     • Hazelnoot ALT

     @hazelnoot@enby.life the issue is, that posts made by users who are affected by this will not even get to the queue in the first place.
     
     and no, jobs are not retried for forever, there is a limit (which you can reset in your config yaml) at which the jobs is gonna get dropped all together

   • Embed this notice
     Hazelnoot ALT (hazelnoot@enby.life)'s status on Wednesday, 16-Aug-2023 22:11:40 JST Hazelnoot ALT

     in reply to

     @puniko@mk.absturztau.be Wait, is there actually no mechanism at all to remove a delivery job after an exception? It really just retries forever??? Please tell me I misread that code :neofox_shocked:

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Wednesday, 16-Aug-2023 22:35:36 JST Puniko ?

     in reply to

     • tastytea

     @tastytea@very.tastytea.de yes, its not running akkoma. the akkoma bug caused an akkoma instance to announce a users shared inbox with an invalid url (/inbox in this case). it gets updated like that user does a profile update, causing remote instances to reset the shared inbox for that user to this invalid url

   • Embed this notice
     tastytea (tastytea@very.tastytea.de)'s status on Wednesday, 16-Aug-2023 22:35:38 JST tastytea

     in reply to

     @puniko@mk.absturztau.be but mk. is not running akkoma? :neocat_confused:

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Wednesday, 16-Aug-2023 23:10:51 JST Puniko ?

     in reply to

     • [Yaseenist] Nikola Orsinov [Joseph Grimaldi]

     @orsinov@our.unknowing.dance one of the recent commits in akkoma have accidently set the shared inbox to an invalid url. and this url federated, causing remote instances problems with federation

   • Embed this notice
     [Yaseenist] Nikola Orsinov [Joseph Grimaldi] (orsinov@our.unknowing.dance)'s status on Wednesday, 16-Aug-2023 23:10:53 JST [Yaseenist] Nikola Orsinov [Joseph Grimaldi]

     in reply to

     @puniko@mk.absturztau.be what's the federation killer?

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Thursday, 17-Aug-2023 00:46:16 JST Puniko ?

     in reply to

     • [Yaseenist] Nikola Orsinov [Joseph Grimaldi]

     @orsinov@our.unknowing.dance idk, it probably would resolve itself over time. but i don't wanna wait, so i tried to fix it on my end

   • Embed this notice
     [Yaseenist] Nikola Orsinov [Joseph Grimaldi] (orsinov@our.unknowing.dance)'s status on Thursday, 17-Aug-2023 00:46:17 JST [Yaseenist] Nikola Orsinov [Joseph Grimaldi]

     in reply to

     @puniko@mk.absturztau.be
     Hm dint actors get refreshed semi regularily so that the issue should gradually resolve itself?
     
     Or is it genuinely broken until i run the commands