I'm currently trying to delete my Pixelfed account (for now at https://pixelfed.de/Jena) and here is the warning I get:
Warning: Some remote servers may contain your public data (statuses, avatars, etc) and will not be deleted until federation support is launched.

Sooo it this a server issue? A Pixelfed issue? is this just to cover someone's ass, or shall I be worried?
#pixelfed #pixelfed_de

Jena Warrior Princess (@[email protected])

161 Posts, 16 Following, 35 Followers · Femme trans bi polyamoureuse mariée maman et très occupée

Pixelfed
@jena it’s the way the Fedi works. Some copies of your posts may stay alive for some time on other servers and no one can provide any guarantee that it will be removed everywhere. It’s not really Pixelfed-related.
@ombremad ok thanks! The wording means "federation support is not launched". Dammit.
@jena this sounds like an old leftover honestly. I’m not sure what else it could mean
@ombremad @jena the discourse around pixelfed rn is so confusing, like some people say there is a security problem on their side and so on, others that it’s just the way fedivers (activitypub) works and we should actually understand this better, because we have a misguided notion of privacy on fedi as a whole. I’m quite LOST 🤯
@PeacefulEdna @ombremad I feel this post is quite didactic about what the problem is, security wise, and from a leadership point of view. https://fokus.cool/2025/03/25/pixelfed-vulnerability.html
Pixelfed leaks private posts from other Fediverse instances - fiona fokus

@jena @PeacefulEdna I agree it’s definitely helpful. About the bigger picture and context leading to the point everyone’s fed up with Pixelfed’s founder, I’ll add this: https://dansup-open-letter.github.io/appendix/
A recounting of dansup's hostility

@PeacefulEdna @jena I get that it’s probably confusing. Basically the problem is that Pixelfed had a flaw that allowed it to exploit another flaw in the Activitypub protocol, but the way it was handled made public the whole Activitypub flaw, which is highly frowned upon in the security field when we talked about a flaw that wasn’t disclosed previously (a « 0day »). Usually devs give enough time to each other to fix the vulnerability before disclosing it publicly, out of respect and a general sense of not giving away a huge security issue to potential attackers before it’s actually fixed.

Though you should also note this is only the last of a long streak of mismanagement, miscommunication, and overall fuckery by Pixelfed’s founder.