When you're offline, the relay temporarily stores activities meant for you. Each activity type has a different default retention time (TTL):
You can reduce these durations in the app settings (between 0 and the server maximum). As soon as you come back online, activities are synced then immediately deleted from the relay to protect your privacy.
No. Traditional Mastodon clients connect to a remote server via an API. With Holos, your phone is the ActivityPub server itself: it doesn't use an intermediary API but communicates directly with other Fediverse servers. For example, when you visit a profile, your phone fetches the information directly from the source.
The interface offers multiple views based on your preference:
Holos offers several tools to control your experience:
Account actions:
Timeline filters:
What happens when you report someone?
Holos is more permissive than most Fediverse instances:
Compatibility warnings inform you that some content may not display correctly on other instances, but you can ignore them.
ActivityPub works by distribution (push), not by fetching (pull). When you post, your phone sends the post directly to each follower's inbox listed locally.
Possible causes if a follower is missing:
Solution: Ask the person to unfollow and re-follow you.
Holos offers three types of backup:
Yes. Holos supports the ActivityPub migration protocol (Move). You can import your subscriptions from another instance, and if you leave Holos, you can redirect your followers to your new account.
Migration between relays with your own domain: If you use your own domain via CNAME, you can change relays without performing an ActivityPub migration. Simply register your account on another relay and redirect your CNAME to that new relay. This option requires technical skills (DNS management).