We’ve got a lot of Lemmy app options rolling out soon—it’s exciting!
What do you wish was better about the current way you browse Lemmy, and what features do you hope to have down the road?
A wishlist for two categories, in each sorted from very important to less important:
Technical:
- Open all links relative to my home instance (I want to stay logged in)
- Make community discovery easier and consistent. One method, which always works.
- Move account to another instance, complete with subscriptions and notifications when older comments receive replies
- Clarity: I’m often confused in which community a post lives, or where it originated. Or what a user’s home instance is. It is fine to display relative information (Post X from instance Y as seen from instance Z), if clearly less emphasized
- Indicate who can see a post or comment. From what instances is that content visible?
- Display the same community stats regardless from which subscribed instance they are viewed (subscriber count varies wildly)
View:
- Allow to hide selected posts
- Expand and collapse images in threads
- Lock my feed: Please don’t add posts to the top while I’m browsing the thumbnails at the bottom
- Display post/comment live preview below input field, so I can see the preview while editing. Currently I must switch view.
- Search within a community (without leaving the community page)
- Customize your feed: Control how much of each community is displayed (I want posts from some small communities to always show, and posts from others to only show rarely, or only those with votes/comments)
This was meant with the web/browser in mind. I expect apps and clients to work similarly, unless a characteristic necessitates exceptions (screen size, touch, …).
keyword filters, so you can avoid posts about “trump” or “hitler” and other things that annoy you
For web: better theming, for app: i18n, for both: much smoother subscription to other instances.
I’m mostly waiting for marking posts as read as you scroll by and hiding read posts (but only in your feed). I think this is especially important with the federated content that might come in later than when I “scrolled past” the point in time it would appear in my feed.
No.
But say, I’m currently looking at my Subscriptions sorted by New. I doomscroll until I see stuff that is 10 hours old. While I do that posts could come in that are 5 hours old. But the next time I doomscroll I wouldn’t go that far back because I think I’ve already seen stuff that old.
If what I have seen already was automatically marked as read and not showing for me, I would still see the 5 hours old stuff because that wouldn’t have been marked as read.
Being able to jump back a page without snapping to the top is the only issue I have with the PWA set up I’ve got. Otherwise it’s great as is.
