PieFed 2025 Roadmap prioritisation

Ideas for road map items were gathered from the PieFed community and each idea now has it's own post here. Now I need to prioritize them so to assist me with that, please upvote those ideas that are important to you, ignore those that do not and only downvote when an idea seems like a counter-productive waste of time and energy.

If I want to comment on something I’m redirected to a new page where a lot of the context is missing. I would rather just inject the simple form with help of JavaScript where it would show up later. This way I can scroll up and down in the page to see the whole context, not only the post and the comment I’m answering to.

I understand that cross posting is not always desirable, but it has it’s benefits also. You can find new communities, you can easily post a post which someone else posted into a more appropriate community where more people will be able to read it. For that it would be nice to consolidate cross posted posts in the view so they don’t show up over and over again but also have a way to cross post in a simpler way.

Add a favourites to communities and a filter to only show articles from the favourites. Some communities are more important than others and the notification button for new posts in those communities feels out of place.

I think along with an hypothetical version 1.0 (and maybe attracting new users and developers) we could clean/tidy a few other things as well, write some more developer documentation, where to look up how ActivityPub works, write down a few things from the video tour through the codebase as text, write some glossary about the terminology. Do a bit of cleanup work and delete old and unused CSS classes. Suppress the confusing exceptions in the maintenance task and fix the timeouts. Maybe gather stats from Celery and tie it into the admin interface.

Loops videos need to be displayed as a video post type and embedded in the page. Same as how youtube videos currently work.

Copy PeerTubes way of remotely subscribing to communities, where you have a [Subscribe] button and it offers you to “Subscribe with an account on this instance” by logging in into it Subscribe via RSS by linking to the RSS feed Subscribe with a remote account by letting you add your own instance URL and then redirecting to the /community/add_remote page with the community pre filled so it can be joined

Use PieFed for announcements, discuss ideas and Pull-Requests. The things that spill over from Codeberg into the Matrix chat and would benefit from a threaded conversation. It's a two-edged sword. We'd be approachable more easily and grow a community within the software we use. Of course that'd be open to lower quality and random interactions. Either we're fine with that, or we better skip that idea. Main benefit: We'd be forced to implement something that makes PieFed better at that kind of task. Like limit communities to trusted or PieFed instances, do some membership handling, and/or mark accepted answers like on StackOverflow/Discourse, use tags/flairs to indicate open/closed/archived threads(issues) … (We could just test the waters and see if that’s a better way to communicate and in doubt switch back to the current setup which works well.)

current implementation makes identifying the main account trivial (piefed.social/u/zIM40YKd is banned from lemmy.ml), and risks bloating the DBs of remote instances if the option is toggled.

Continue efforts to integrate HTMX, to help transform an old-school multi-page application into something more modern. Where feasible, anything that currently results in refreshing the entire page (such as changing the sort order, or adding a reply when in the post), should just refresh the relevant section.

Image hosting with per-user quota. These would be inserted into posts and comments. Users would need to be able to manage their media collection.

The notification icon (the bell) isn’t showing notifications are waiting unless the screen is refreshed. It would be nice if it were more actively checking notification status.

This issue https://codeberg.org/rimu/pyfedi/issues/107 has some good ideas, we could pick a few and work on the design/implementation

Possible functions:

On masto this is used a bunch of ways - hide/show nsfw, hide/show political posts, hide/show tough discussions, etc. Not sure if its an exact fit, but I figure i’d bring it up for discussion

Federate with Mobilizon and Friendica