@mint@feld yeah big pain of values as errors in the land of untyped pattern matching, too many things accidentally shaped wrong in the spaghetti of case fallthroughts
@feld@mint that's what i did in march after getting tired of pulling up psql, really handy even if it's a bit lackluster in that you can only order the table instead of filtering on the state/queue/worker you'd want to focus on
@feld@tusooa@lain@lanodan@izaya multinode would honestly not do much help, big deployments are always DB timeout death spiral bound
also hate how half the pleroma developers have locked their instances down enough that i need to read this thread off @hj instance not to miss half the replies
@PurpCat@lina@Lunarised@p@Cocoa@mint@lunarised for rebased, i don't think there's even been breaking changes to the DB schema, worth trying to just run pleroma off the same DB with no rollbacks
@jesu@phnt@mint the same reason AP has sections full of "lol do whatever", and servers like mastodon ignore half the spec anyway because they got the privilege of being the implementation that barely got it approved by the w3c in the first place
if you don't want the follow relationship, you send out the undo's for that, and store an export to resend them later
@jesu@phnt@mint don't think it stops the other servers from sending you activities, since the other server already has the user json in the db with what it thinks is a valid subscription relationship
@blockbot@admin@lain people have done it, most of the hassle involves adding in argon2 hashing or forcing everyone to do a password reset and some schema rollbacks
also the blockbot bit is funny because akkoma deliberately removed activities it did not approve of from reaching the MRF flow