(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.
Users are empowered to set what they want their default homepage view to be (“Subscribed” , “All”, or “Local”). I am unsure what the default is, but mine is set to “Subscribed” which I think it makes the most sense for most users.
Unless you are on a heavily moderated/defederated server (such as beehaw) whose moderation policies, politics, etc. you are aligned with it is very likely that “All” is going to contain something that someone doesn’t like. I am personally not in favor of over-policing what users do outside the confines of their home instance, it’s a fine line that I haven’t had to define too clearly yet so perhaps my thoughts here will change.
If you don’t like what’s in “Local”, then to me that is a sign that the instance isn’t for you. Local is a reflection of the sort of content that users on that instance want to see more of. The admin allowing such content is not necessarily an endorsement (unless they were the one to actually post it), but is tacit acceptance of that content and the community that content exists in.
I think some way to make a “Curated” feed of posts only from certain approved communities would be a welcome feature and present a useful middle ground allowing for a moderatable discovery experience, like the default subscriptions provided on that other site.
Calckey and at least some Mastodon forks have this ability. The admins set up a timeline that is made up of local and federated content, but only from instances that they have explicitly chosen. It allows for a firehose of content more likely to be relevant to new folk before they follow lots of people
We could call it a “front page”.