@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
@MoeBritannica same for giving back starcrafts code to activision|blizzard(microsoft) without leaking it online for a con ticket and some overwatch merch
@dcc@kirby do the two update queries i posted yourself, rename the fake account to some unique value first, like fake.graf, then restore the main account
@dcc@kirby restart pleroma, or remote into it via pleroma_ctl remote or iex by: giving the process a name in the service ExecStart=/usr/bin/elixir --sname pleroma -S /usr/bin/mix phx.server sudo -Hu pleroma iex --remsh pleroma --sname dev and then Cachex.del(:user_cache, "nickname:graf@poa.st") or clear the whole thing Cachex.clear(:user_cache)
@mint@pernia@Rocc right, looks like they started off from some paas offerings starter template reimplementation, which is what also pnut.io did, and so their libraries/clients just seem like forks of what people did for that
honestly a complete mess that wasn't going anywhere