The current list of ways something can get into the federated timeline:
- someone from your server is following that user
- someone from your server replied to that user
- someone from your server is following someone who replied to that user
- someone from your server liked/boosted it
- someone from your server copy/pasted the link into the search box, causing the server to load it
@nightpool Hold on a second!
If I reply once to a user, all it's toots will be visible to my instance? Or just it's answers to the discussion?
@chindit If you reply to a user, only the post you reply to will be included in the federated timeline. (not just for your server, but for all the servers where people follow you)
@crecca Correct. this is a common misconception. The federated timeline is the union of every user on that instance's timeline, plus the exceptions above. It's every user followed by anyone on your server.
@nightpool …and from then on, no matter which of those events fired, that user’s toots appear on your fedline?
@babelcarp No, no, only the toots involved in one of those events appear on the federated timeline.
Another way to think of it is that the federated timeline is a feed of "all the toots your server knows about". The main way for your server to find out about a toot is if someone follows a user on a another server—then it will get notified for every toot that user makes. There are other ways for it to find out about a toot though, which is what I listed above
Or maybe mega-instances should have guest accounts: no passwords, no timelines even, just searching?
I’m aware that wouldn’t be a clean solution, just a hack. But *something* is needed soon, I think, if Mastodon is gonna be as useful as Twitter.
I think the concept of trying to see "everything" happening on ""mastodon"" is flawed in a ton of different ways. What does the concept of "all of mastodon" even mean in a federated environment? Focus on yourself, and your community. Searching isn't required. There are a ton of reasons people don't want full-text searching.
@nightpool I *think* you’re saying you reject searching even on the local instance. If so, maybe you should try to fork a version of the Mastodon client that omits search and then install it on your instance.🙃
@babelcarp the mastodon server does not have full text search—it only searches hashtags and usernames. This is intentional, and you can read elsewhere why they made this decision
@nightpool Understood. But here, posting from the small instance where I live, I want to meet people interested in tea. There aren’t any such people here. The chance of finding them on other instances, even if they habitually use the hashtag #tea, is tiny. Global hashtag search is precisely the way I’d like Mastodon to learn from Twitter.
@dBu_fs small instances are always going to have unique federated timelines. Large instances less so.
@nightpool it is absolutely required for you to be able to view conversations without leaving your instance
I absolutely agree. But the original toots without context shouldn't *show up in the federated timeline* on their own. The federated timeline should JUST be toots made by people followed by the server or boosted by the same. Others should be excluded because their relationship to the server is tenuous at best, and invariably drags down the quality, readability, and usefulness of the timeline
@gargron I understand that the current implementation of the federated timeline is "ever toot known about by the server". Users find this very hard to reason about though.
@gargron yes but it adds a LOT of statuses, and, anecdotally, every time I saw a really obnoxious or boring toot in my timeline, it was because of this effect.
Plus it increases conflict, because any arguments get spread across the entire fediverse, to instances that are PREDISPOSED to disagree with them, but that CAN'T see that there are already people arguing about them
@nightpool @babelcarp @gargron
"it's not a bug, it's a feature"
seriously, i miss posts from people i follow and who are following me on another instance
for me, it's simple : local is the ghetto you chose, federated is the universe
with a setting if you only want original posts, and not replies or reposts
@nightpool you forgot : someone from your server follows an user that boosted that post (unless this user set his posts to be "unlisted" by default which modify boosts status, according to my tests)