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.

Vote for as many ideas as you like but be selective. Something like upvote your top 10 ideas and downvote the bottom 5, that kind of thing.

UPDATE: Roadmap has been finalised! Thanks for your participation everyone!

https://codeberg.org/rimu/pyfedi/src/branch/main/docs/project_management/roadmap.md

To make it I went through https://piefed.social/c/piefed_2025?sort=top adding things in order until I started to doubt we’d get it all done this year. So some things didn’t make it into the final roadmap but they’re still at https://piefed.social/c/piefed_2025 so they won’t be forgotten for 2026 ;-)

Of course whether something is on the roadmap or not won’t stop us scratching whatever itches are strongest at the time but it will give us something to refer to when there is no itch…

  • OpenStars@piefed.social
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    22 days ago

    Another topic that I didn’t see in the list: a goodly fraction of the time when I click a Notification link, it does not go to whatever it seems to be trying to point at. Sometimes this is an issue with Notifications itself while other times it is a mismatch with the rules for post rendering. This is definitely one of the more frustrating things with using PieFed atm.

    The reasons that I’ve tracked such issues down to include but may not be limited to:

    • the comment being too deep, i.e. it is buried with the Continue thread link (so it takes you to the OP, but then what is someone supposed to do to find whatever triggered the notification?)
    • auto-collapsing or even auto-hiding, e.g. if you reply to a comment and then afterwards the comment you replied to receives 50 downvotes, the Notifications link will take you to the OP but you won’t be able to see the comment itself anymore, nor to find it with a browser text search: it would be helpful if going directly to a comment link should be an exception to the auto collapse/hide rules? (not merely removing the Notification in that case, bc you’ve already signaled a willingness to engage with the content, e.g. chosen to expand it if it started off as collapsed)
    • the post was removed (yet the Notification remains?); I forget if I’ve ever seen this happen with the comment itself having been removed but definitely good to check proper behavior for that as well:-) I suppose theoretically people could reply to that reply to your comment, but I don’t see much value in still being sent to read something that no longer exists.
    • your account has blocked the user, possibly even all users from a domain, but either way you are told that there is something to read and yet after clicking, the page refuses to show what that is:-|

    This and an inline comment feature would be my top priorities to see in order to be ready for a mainstream audience rather than solely those of us with an early adopter mindset :-).