what do you mean refuse by principle to fix it? the solution that comes to mind is for a whitelist that is implemented either in federation broadly or lemmy specifically for certain categories (think TLDs) which are agreed to have a certain focus, like on literature or video games or music, where the instances themselves can join or link to.
kinda bypass a community being held hostage (or kept isolated) by an instance, the whitelists can be determined through a simple majority (first past the post) or any other method by members of communities rather than instance moderators/admins.
i get that many folks don't like hexbear and i have nothing against them, i certainly don't want to force them to see content they don't want; giving granular control over specific content (not just a blacklist like per-user instance blocking) seems ideal.
When you go to "/c/books" on any server, the default should be an agglomeration of all /c/books on all federated servers (notwithstanding the already ongoing defederation wars)
The -USER- then decides if they want to filter by whitelist or blacklist, the user decide what server or community@server goes on the list.
Realistically, users will just follow other user's lists, which should be sharable easily. You might even subscribe to someone else's blacklist/whitelist and get updated automatically.
But none of that is possible if the baseline view is not the ability to "see all /c/book on the entire fediverse in its raw unedited form". You can filter out data you can't access.
Whitelists, of course, are poison were just just deem everything to be garbage except "the chosen ones", usually handed down from above by your betters.
A public blacklist model would be much better. You could then build your own blacklist by scanning all user profile for what is on their blacklist and use that as a basis for building your own blacklist, this is mostly how spam filters work. Because in the world of email, if you say "everyone I don't already know is garbage" well, then you might as well just abandon email entirely.
what do you mean refuse by principle to fix it? the solution that comes to mind is for a whitelist that is implemented either in federation broadly or lemmy specifically for certain categories (think TLDs) which are agreed to have a certain focus, like on literature or video games or music, where the instances themselves can join or link to.
kinda bypass a community being held hostage (or kept isolated) by an instance, the whitelists can be determined through a simple majority (first past the post) or any other method by members of communities rather than instance moderators/admins.
i get that many folks don't like hexbear and i have nothing against them, i certainly don't want to force them to see content they don't want; giving granular control over specific content (not just a blacklist like per-user instance blocking) seems ideal.
what do you think?
When you go to "/c/books" on any server, the default should be an agglomeration of all /c/books on all federated servers (notwithstanding the already ongoing defederation wars)
The -USER- then decides if they want to filter by whitelist or blacklist, the user decide what server or community@server goes on the list. Realistically, users will just follow other user's lists, which should be sharable easily. You might even subscribe to someone else's blacklist/whitelist and get updated automatically.
But none of that is possible if the baseline view is not the ability to "see all /c/book on the entire fediverse in its raw unedited form". You can filter out data you can't access.
Whitelists, of course, are poison were just just deem everything to be garbage except "the chosen ones", usually handed down from above by your betters.
A public blacklist model would be much better. You could then build your own blacklist by scanning all user profile for what is on their blacklist and use that as a basis for building your own blacklist, this is mostly how spam filters work. Because in the world of email, if you say "everyone I don't already know is garbage" well, then you might as well just abandon email entirely.