Post
This post will not appear in the timeline of most Pixelfed users.
Because considered at "not pretty enough" for them (despite the great illustration by @davidrevoy )
It worth asking the question:
Is Pixelfed sawing off the branch that the Fediverse is sitting on?
https://ploum.net/2025-12-04-pixelfed-against-fediverse.html
@ploum I really don't understand why it's an issue.
If all #Fediverse platforms do the same things, what's the point to have many? If all Fediverse platforms are "like #Mastodon, but a different UI/flavor/look" the only thing that will happen is Mastodon will remain too dominant in the Fediverse and the rest will remain anecdotical.
This is what I like about #Pixelfed. That it is about pictures and pictures only.
It sounds like you're asking for all platforms to do the same things. Why?
I think you are making a correct observation here:
Place or Recipe.From a technical standpoint: This is expected. From a user perspective, it's weird. A lot of work will be needed to get the Fediverse to be more user friendly here.
I do not know what the exact solution would be. Parts of it would certainly be being able to determine if an application can parse something. FEP-67ff: FEDERATION.md being adopted by pixelfed could be a first step towards it. In particular, if somebody would implement my plan to parse all these files.
@ploum @davidrevoy Please see my response here:
A space for Bonfire maintainers and contributors to communicate
