Skip to main content

The official Mastodon app really needs to add support for the "Local" timeline.

It was (presumably) left out because on larger servers it's an overwhelming firehose and seems useless.

However, on smaller servers it's a really important way to build a sense of community.

Instances like put a lot of work into making their local timeline pleasant for their members, and they have withdrawn from the directory in protest at the lack of Local support in the official app. This is a bad sign, it shows something has gone wrong in relations with smaller instances.

Small servers are really good for Masto, because the more small servers there are, the harder it will be for any amoral billionaires to try to buy up the network.

If you agree that the Local timeline should be added to the official app, please add thumbs up to the relevant issues on GitHub:

## # #
Screenshot of the desktop Mastodon web interface with the local timeline button highlighted
Screenshot of the Mastodon mobile web interface with the Local timeline button highlighted
we can use the browser or wait to groups coming in.
Or even another temp solution, follow all local users we want updates from.
I also need federated timeline @Gargron
It also needs to allow custom servers.
I agree that the โ€œfirehoseโ€ argument is valid, so my proposal is to have Local and Federated timelines built into the official iOS and Android apps, but have them *disabled by default*.

New users donโ€™t get overwhelmed and those who have a clear idea what they want will need to explicitly enable it.
Without other timelines I get much less content than on tusky or in the browser.

As someone else also suggested, the timelines could be made optional and new users wouldn't get overwhelmed with too many timelines.
using Mast (on Apple devices, donโ€™t know if thereโ€™s an android-version) you can have a local timeline. You can even add other instances as โ€žlistsโ€œ in order to read their timelines.
Federated to me was the firehose with different languages.
not really an issue IMO. This is the fediverse, there are tons of apps to choose from.
riddiculous, they remove the federated and local timeline, but the explore tab itself is broken.

I'm on a small server, and all i can see is just 404 not found when opening explore tab ๐Ÿ˜‚
thanks for reminding. I added my recent experience with new users where I needed some time and some incomprehensible 'why'... to Identify the official app as the problem, not the user, when I tried to tell 'the' unique selling points of a federated multi instance network.
For me, the local timeline is the most important thing. That's why I'm here. A kind of home, where the fireplace glows, good music plays and I know all the people.๐Ÿค˜
Of course, I also go out sometimes and then I am on the timeline of all my contacts (following, followed). There it is a little rougher, but I have it under control.๐Ÿค“
Rarely, very rarely I go out into the world and visit the Federation. Maybe once a month. But that's enough and after that I appreciate my fireplace again.๐Ÿ––
I agree in principle but this is a reasonable argument for starting with a limited set of # features: ยซWith # and # historically holding apps accountable for content users can access through the app, even when the app could be reasonably classified as a browser, showing unfiltered content is a ticking time bomb for the appโ€™s presence on the major app stores.ยป
These are interesting arguments, it would be good if they were discussed in the issues raised in the githubs.

The problem seems to be that on smaller instances the risks from the Local timeline are small while the benefits are high. On larger instances, it's exactly the other way around.
I think that the solution at least for the moment is on the large number of third apps on the stores that allow those timelines :mastodon: # # #
p.s. To make clear: the Local timeline is still there on Mastodon, it's just you can't see it from the official Mastodon app.

To access Local, use Mastodon through your web browser, and/or install an unofficial app instead of the official one. The unofficial apps have been around for a lot longer, and include more features in general.

You can see the unofficial apps in the "third party" section of, and the Android unofficial apps are also on @fdroidorg.

FediTips reshared this.

Totally agree. At least local, but I would prefer federated also.
@FediTips Since when do we need to re-centralize and de-federate to be a community????
No no, no one is defederating!

Federation isn't affected, you can still follow people on other servers and their posts will show up on your timeline. That is all totally fine on all apps, including the official one.

The only issue I'm raising is that the official app doesn't show the "Local" timeline where you see posts from everyone on your server including people you don't follow.
@FediTips Yes .. and that is actually a re-centralizin feature..

Over here in the fediverse, we don't necessarily join to get just the bubble of one particular server...

And as i understand it, mastodon has this 'explore' feature, which shows you other _local_ users to follow possibly..

So overall .. mh

I have a stream with all the ppl i follow ... and from time to time i look into specific # or similar.

I don't really get why you would need to have a stream just for ppl "with you on the same virtual home right now". ;)
Tying moderation and community to the implementation detail that is an instance is not ideal, but until we have p2p fedi with the ability to join free-floating posting communities and moderating communities, in today's federated fedi instances and their communities are pretty important to many people.
This entry was edited (4 months ago)
Good news! A "Local Timeline" string just added into Mastodon for Android app. I think we should calm down and waiting for new changes.
So, why do people want a native app when the web app works as well as it does? I guess you could argue that it's easier on resources (assuming it's not an electron app). Are there other reasons?

This website uses cookies. If you continue browsing this website, you agree to the usage of cookies.