Conversation

Notices

1.  (mint@ryona.agency)'s status on Wednesday, 22-May-2024 08:01:31 JST 

   • nukie
   • this ad CAN be blocked, bitch
   • ruin
   @kirby @nukie @ruin Are you sure it showed with @poa.st and not @fba.ryona.agency? Because if not, the bug might lay deeper than that, working only if the proper account doesn't exist in their DB (because the domain is blocked). Though that might be an ackoma quirk which I shouldn't be concerned about; tests with pleroma proper showed that it just doesn't work on 2.4 and lower.
   •  (mint@ryona.agency)'s status on Wednesday, 22-May-2024 18:45:16 JST 

     in reply to

     • nukie
     • this ad CAN be blocked, bitch
     • ruin
     @kirby @nukie @ruin Anyway, looks like the charade is over. Seems that no one but yours truly happened to have fun with that in the meantime.
     https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4114
   • nukie (nukie@boymoder.biz)'s status on Thursday, 23-May-2024 19:17:16 JST nukie

     in reply to

     • this ad CAN be blocked, bitch
     • ruin
     @mint @kirby @ruin i think the bell/subscription is broken now, I only see replies that directly mention me in notifs. not sure if it's related tho
      likes this.
   •  (mint@ryona.agency)'s status on Thursday, 23-May-2024 19:18:34 JST 

     in reply to

     • nukie
     • this ad CAN be blocked, bitch
     • ruin
     @nukie @kirby @ruin I've cherrypicked Alex's fix before the proper MR got merged. Don't see how it can affect notifications, but won't be suprised it somehow does.
   •  (mint@ryona.agency)'s status on Friday, 24-May-2024 18:27:09 JST 

     in reply to

     • nukie
     • this ad CAN be blocked, bitch
     • ruin
     @nukie @kirby @ruin And here's the reason, merging shit that breaks previous frontend behavior.
     https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3659