Table of Contents
Solo instances cannot effectively utilize the timeline.
Mastodon has three timelines.
- federation timeline
- local lime line
- Home timeline
Each has the following characteristics,
federation timeline
A timeline where all posts with a public scope of “Public” from the server you are logged in to and the federated server are displayed.
local timeline
Posts whose public scope is “Public” on the server you are logged in to
A timeline in which
Home timeline
Your own posts, posts by users you follow, posts with hashtags you follow, and posts boosted by users you follow.
A timeline in which
Reference: Various Mastodon timelines [Fedibird]
The solo instance is a little different.
Only the home timeline works for solo instances
For solo instances,
The federation timeline and home timeline will have the same information.
The details are as I checked in the past on Federated timeline on Mastodon’s solo server.
So, since the local timeline is a solo instance, it only contains your own posts.
In other words, it is no different from the list of posts you see on your account page.
As a result, only the home timeline works in solo instances.
I felt that it was a waste, so I looked into whether it could be used and found that RSS I discovered an instance that is being used as a feed.
Turning your local timeline into an RSS feed
Indeed, by doing so, your local timeline becomes a useful timeline with interesting RSS and your own posts.
Apparently there is also a tool for that.
Monesi, a bot that turns Mastodon into a shared feed reader
However, it didn’t seem to have been updated, so I implemented it myself this time.
- Added new user to solo instance using Mastodon image on XServer VPS
- I created a Mastodon bot using PM2.
As a result, I am very satisfied,
Nowadays, there are more opportunities to visit the local timeline than the timeline.
The remaining tasks are customizing posts, converting the RSS URL list to an external file, and quitting PM2.
We will continue to improve.
