Discussion
I opened in 2025 9 pixelfed bug ticket, one is closed plus one I wrote one privacy vulnerability report by email (as suggested on Github) which is still opened.
One of my PR is merged, another one is open where I have to change little stuff to get it going.
2/4
@hiphopheaven @mastodonmigration @tchambers @pixelfed @nlnet @dansup
just to be transparent, the Pr is now merged, thx @dansup
@pixelfed_is_broken@mastodon.social
The main thing I don't understand is:
There are a lot of bugfixes merged by @dansup. but there are no releases. For me, the branch should be always releaseable. Maybe nightly releases would be a trick to make us more happy.
I wrote a long thread about it, but unfortunately @dansup has not responded
https://chaos.social/@joergi/115018043955423916
3/4
@hiphopheaven @mastodonmigration @tchambers @pixelfed @nlnet
@joergi dude, the activity pub issue has existed for a year, and you can still accidentally nuke your account on the pixelfed.social instance - it is broken, why is it still available to use?
This is insane, that alone should warrant folks asking some hard questions.
None of this is excusable for a project this size, I cannot trust him or the project and neither should anyone else at this point.
And there are some devs helping @dansup but still, he has to review and does most of the coding alone. His day has also only 24h, ...
So i just hope that 2026 will be better.
But as i said in the beginning: I can 100% understand the frustration. And I would love to see not new features but taking care of the open bugfixes and all the broken Fediverse promises in #pixelfed.
4/4
@pixelfed_is_broken
@hiphopheaven @mastodonmigration @tchambers @pixelfed @nlnet
