Conversation

Notices

1. Embed this notice
    (mint@ryona.agency)'s status on Sunday, 02-Mar-2025 06:44:51 JST 

   in reply to

   • ✙ dcc :pedomustdie: :phear_slackware:
   • Phantasm
   • ins0mniak ~Hate Account~
   • nyanide :nyancat_rainbow::nyancat_body::nyancat_face:
   • Sovereign Analysis
   • Vivi Nella Verita
   @phnt @dcc @ins0mniak @nyanide @Sovereign @verita84 Password hashing type is literally defined in a field, if it's not argon2, this commit shouldn't even touch them. I only made an MR for it to facilitate proper ackoma->pleroma migration. There's been a bunch of oauth changes since, maybe those are related instead.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Sunday, 02-Mar-2025 06:44:52 JST Phantasm

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     • ins0mniak ~Hate Account~
     • nyanide :nyancat_rainbow::nyancat_body::nyancat_face:
     • Sovereign Analysis
     • Vivi Nella Verita
     @ins0mniak @dcc @nyanide @Sovereign @verita84 The whole "cannot login" thing smells like the support for the argon2 passwords that was added somewhere in the 2.7 and 2.8 cycle. Which would be a deps issue in the end.
     
     https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4257
   • Embed this notice
     ins0mniak ~Hate Account~ (ins0mniak@fsebugoutzone.org)'s status on Sunday, 02-Mar-2025 06:44:53 JST ins0mniak ~Hate Account~

     • ✙ dcc :pedomustdie: :phear_slackware:
     • Phantasm
     • nyanide :nyancat_rainbow::nyancat_body::nyancat_face:
     • Sovereign Analysis
     • Vivi Nella Verita
     @verita84 @dcc @phnt @nyanide @Sovereign yeah I know that, but it's cleary an issue with the db in this instance.
     
     I mean, I can set it aside for a while and boot up another one.
     
     no harm no foul.