You follow a hashtag on your phone but it does not show as followed on your desktop computer. Mastodon hashtag following sync across devices can lag by several minutes or even hours. This delay happens because Mastodon uses a pull-based federation model rather than instant push notifications for metadata changes. This article explains the technical cause of the sync lag and shows you how to force a refresh on any device.
Key Takeaways: Mastodon Hashtag Following Sync Delay
- Pull-based federation: Mastodon instances check for new follower metadata from upstream servers at intervals, not instantly.
- Manual refresh with F5 or pull-to-refresh: Forces the client to re-request the list of followed hashtags from the instance server.
- Server-side cache TTL: The instance caches your followed hashtags for up to 5 minutes before checking for updates.
Why Mastodon Hashtag Following Sync Lags Across Devices
Mastodon is built on a federated architecture where each instance operates independently. When you follow a hashtag on one device, the action is sent to your home instance server. The server records the follow and updates your account metadata. However, this metadata change is not broadcast to all connected clients in real time.
The sync delay has two main causes:
Pull-Based Metadata Distribution
Mastodon clients such as the official web app, Tusky, and Mastodon for iOS do not receive push notifications for metadata updates. Instead, each client periodically polls the instance API to fetch the current list of followed hashtags. The polling interval varies by client. The official web app polls every 60 seconds. Third-party apps may poll every 30 seconds or every 5 minutes. If you follow a hashtag on your phone, the desktop client will not see it until its next poll cycle completes.
Server-Side Cache
The Mastodon server caches the list of followed hashtags for performance reasons. When a client sends a request for the hashtag list, the server returns the cached data. The cache time-to-live (TTL) is typically 300 seconds (5 minutes) in default configurations. This means that even if the client polls immediately after you follow a hashtag on another device, the server may return stale data. The cache is invalidated only after the TTL expires or the server receives a write request from the same session.
No Cross-Device Session Awareness
Mastodon does not maintain a shared session state across devices. Each client uses its own OAuth token and session. When you follow a hashtag on device A, the server updates the database entry for your account. Device B, using a different session, has no way of knowing that the database changed until it sends a fresh API request. There is no WebSocket or Server-Sent Events channel for metadata changes.
How to Force Hashtag Follow Sync Across Devices
You can reduce or eliminate the sync delay by manually refreshing the client or by using a workaround that triggers a server-side cache invalidation.
Method 1: Manual Refresh on the Web App
- Press F5 or Ctrl+R
This forces the browser to reload the entire page. The web app will re-fetch the list of followed hashtags from the instance API, bypassing the browser cache. - Check the hashtag list
Open the hashtag list by clicking the hashtag icon in the left sidebar or by navigating to Preferences > Hashtags. The new follow should appear immediately after the refresh. - Repeat if necessary
If the hashtag still does not appear, wait 30 seconds and press F5 again. The server-side cache may still be valid from a previous request.
Method 2: Pull-to-Refresh on Mobile Apps
- Open the hashtag list
In Tusky, tap the hashtag icon in the bottom navigation bar. In Mastodon for iOS, tap the search icon and then tap the Hashtags tab. - Swipe down from the top of the list
Perform a pull-to-refresh gesture. This sends a new API request to the instance and updates the list of followed hashtags. - Wait for the spinner to disappear
The list will reload. If the follow still does not appear, close the app completely and reopen it. This forces a full re-login and re-fetch of account metadata.
Method 3: Unfollow and Re-Follow the Hashtag
- On the device where the follow is missing
Navigate to the hashtag page. For example, if you followed #tech, go to https://yourinstance.social/tags/tech. - Click the Following button
This unfollows the hashtag. The server immediately removes the follow from the database and invalidates the cache for that hashtag. - Click the Follow button again
This adds the follow back. The server writes the new follow to the database and updates the cache. All clients will see the follow on their next poll cycle.
If Mastodon Hashtag Following Still Lags After Manual Refresh
The hashtag follow sync takes more than 10 minutes
This indicates a server-side caching issue beyond the default 5-minute TTL. Some instance administrators increase the cache TTL to reduce server load. You cannot change this setting from the client side. Contact your instance admin and ask them to reduce the FOLLOWED_TAGS_CACHE_TTL value in the Mastodon configuration file from 300 to a lower value such as 60 seconds.
The hashtag follow sync works on one device but not another
This typically happens when one client is using an outdated OAuth token or is logged into a different account. Verify that both devices are logged into the same Mastodon account. Check the username displayed in the app settings. If the accounts match, log out of the problematic device and log back in. This generates a fresh OAuth token and forces a full metadata sync.
The hashtag follow sync works on the web app but not on a third-party app
Third-party apps may implement their own caching layer. For example, Tusky caches the hashtag list locally for up to 2 minutes. Clear the app cache in the system settings. On Android, go to Settings > Apps > Tusky > Storage > Clear Cache. On iOS, uninstall and reinstall the app. After clearing the cache, the app will fetch fresh data from the instance.
Mastodon Hashtag Following Sync: Web App vs Third-Party Apps
| Item | Official Web App | Third-Party Apps (Tusky, Mastodon for iOS) |
|---|---|---|
| Default poll interval | 60 seconds | 30 seconds to 5 minutes depending on app |
| Local caching | Browser cache, cleared on F5 | App-level cache, cleared on app data reset |
| Server cache bypass | Not possible from client side | Not possible from client side |
| Manual refresh method | F5 or Ctrl+R | Pull-to-refresh or app restart |
| Session awareness | Single browser session | Independent OAuth tokens per device |
Mastodon hashtag following sync across devices lags because of pull-based metadata distribution and server-side caching. You can force a refresh by pressing F5 on the web app or pulling to refresh on mobile. If the delay persists beyond 10 minutes, contact your instance admin to adjust the cache TTL. For consistent cross-device sync, log out and log back in on the affected device to generate a fresh session.