[Closed] Moved to [email protected]
This community has moved to [email protected]
Original sidebar info
To discuss how to grow and manage communities / magazines on Lemmy, Mbin, Piefed and Sublinks
Resources:
- https://lemmy-federate.com/ to federate your community to a lot of instances
- [email protected] to organize overall fediverse growth
- [email protected] to keep tabs on where new users might come from :)
- [email protected]
- [email protected]
Megathreads:
- How (and when) to consolidate communities? (A guide)
- Where to request inactive or unmoderated communities? (A list)
Rules:
- Be respectful
- No bigotry
@[email protected] as I know you like the topic
@[email protected] as we discussed it just now
discuss.online would be a good candidate, but you'd want to get buy-in from @[email protected] as well
Me liking printed books more than ebooks is already a political matter, so... that would be difficult to offer political-free content.
I think I already mentioned it, but my idea would be to have nothing for newcomers (so they don't get to see even a single political, or low effort post) beside a few tags/keywords/categories they could click in order to start having content displayed in their feed that they actually want to see, no matter how good or how bad it would be ;)
edit: typos
By default new users could be sent to their Subscribed feed and see nothing, but then how do they know how to find content?
The keywords/categories is a nice idea (similar to what https://piefed.social/ does with its "topics"), but would require modifications to the Lemmyy codebase. The approach I suggested is doable with the tools we have now (defederation, community-blocking at instance level)
By default new users could be sent to their Subscribed feed and see nothing, but then how do they know how to find content?
the tags/categories I mentioned would do that. Nen users are supposed to know what they're interested in or what they're curious about so they would select those.
The approach I suggested is doable with the tools we have now (defederation, community-blocking at instance level)
I have little to no understanding of the technical considerations but I would think that if a technique involves defederation/blocking it also means it won't be bulletproof because, well, shit content does not always come from the same source(s).
I would counter and suggest that Lemmy implements a "default block" system that admins can set on their instance, i.e. the 3 you've mentioned, plus any others they want. When the account is created, the default blocks are applied (either instance or communities or ideally flexibility to add both).
Users can then choose to unblock these if they want to engage with that content without moving instance.
While portability is kind of a feature of the lemmyverse, your posts don't come with you so likely people wouldn't want to move off the "default" instance, which would create another problem with centralized instances.
I would counter and suggest that Lemmy implements a “default block” system that admins can set on their instance, i.e. the 3 you’ve mentioned, plus any others they want. When the account is created, the default blocks are applied (either instance or communities or ideally flexibility to add both).
The issue is that requires development on Lemmy. The proposal in the OP can be done with the existing tools. Otherwise, I agree with you, what would be more elegant.