(just a few thoughts I wanted to write out)
Don’t get me wrong, I love the local and federated timelines, but after thinking about it I realized that it’s also the cause for a lot of drama.
Email and Xmpp never had such a big problem with cross instance blocks. If you think about it, all federated content is blocked by default and only becomes available if a user searches for it and subscribes to it. Before that, the server has no idea what is out there unless a relay is used. But there’s two exceptions… the local timeline and the federated timeline.
These are great to get stuff started and kickstart the following process, but are forcing people to receive content that they might not want to see.
Where previously a block would only be necessary whenever a malicious user messaged me directly, now we have to deal with the need to curate content of public timelines in order to avoid problems with local or remote users.
The instance admins have full right to decide what is hosted on their instance and what not. This is not about free speech because you are not entitled to using someone’s server in a way they don’t want, but about creating complicated dilemmas and tough moderation choices by forcing together content and users that could be drastically different in beliefs or preferences by using timelines which are understandably very appealing to use.
Maybe all posts should be unlisted by default and both timelines, whether on Lemmy or Mastodon only contain whitelisted user accounts to give your instance’s users and remote users a few recommendations.
Perhaps there should be a new default feed that only features posts from communities that ‘x’ number of users have a subscription to, with ‘x’ being scalable with userbase. Also the aggregate user’s community subscription count could be used to influence the sort order for that feed and bring more popular content closer to the top. Of course there will still be diverseness amongst users in even the smallest userbase, but maintaining a blacklist of communities against a feed curated by user subscriptions would surely be easier than maintaining a blacklist against the raw feed from other instances.
One thing I worry about is finding new communities. If I understand correctly the federated feed only shows posts from communities that other users have previously searched for? If so that leaves new community discovery solely up to word of mouth or searching using external websites. Perhaps each lemmy instance could ask it’s peers for a list of their top subscribed communities from their instance by the users on that instance, and then start pulling posts from those top communities and adding them to the ‘all’ version of the federated feed. That should give existing and new users a (hopefully) mostly decent feed of the top communities from other instances to find content and communities from.