I think I copied pasted that in there from one of the github issues. I didn't mean to.
PumpkinDrama
joined 1 year ago
I had to toggle between show and hide read posts all the time for the same reason but I don't think having a read posts section would be any simpler than toggling the setting.
All I know about it is that Mastodon offers this feature and is one that users have requested in a few very popular issues.
Federating communities is a manual process so in smaller instances you don't see as much content as in larger ones since there aren't many users subscribing to external communities.
The Scaled sort on the Subscribed view, it's essentially the same as the New sort.
Profile Privacy Settings #4223: Allow users to control who can view their profile feed/activity, with options like public, visible only to friends/followers, or completely private.
- Moving user profile to a new instance #1985: Provide the ability for users to migrate their account and all associated data (posts, comments, moderation actions, saved posts, etc.) from one Lemmy instance to another. This would allow users to move freely between instances without losing their online identity, history, and credibility built up over time on a previous instance.
It's crazy when I see this super popular issues closed without completion by the main devs. It makes me feel like they don't care at all about user feedback.
It certainly doesn't help that Lemmy had and still has absolutely no sensible way to actually surface niche communities to its subscribers. Unlike Reddit, it doesn't weigh posts by their relative popularity within the community but only by total popularity/popularity within the instance. There's also zero form of community grouping (like Reddit's multireddits) - all of which effectively eliminates all niche communities from any sensible main view mode and floods those with shitty memes and even shittier politics only. This pretty much suffocated the initially enthusiastic niche tech communities I had subscribed to. They stood no chance to thrive and their untimely death was inevitable.
There are some very tepid attempts to remedy this in upcoming Lemmy builds, but I fear it's too little too late.
I fear that Lemmy was simply nowhere near mature enough when it mattered and it has been slowly bleeding users and content ever since. I sincerely hope I'm wrong, though.
@PurpleTentacle@sh.itjust.works https://sh.itjust.works/comment/4451602
The Lemmy community is here not on GitHub, and discussions on GitHub issues without a threaded, tree-like structure suck.