The fediverse now has a mobile-first personal server called Holos by @HolosSocial (via @appsFedilab Apps). It's a full ActivityPub server that runs on your Android device (iOS coming soon). You own your identity with a custom domain and your followers live on your device.

Project URL: holos.social

Key features:
✅ Your server on your phone – Your identity, keys, and followers live on your device, not a giant shared server.
✅ Custom domain identity – Permanently own your handle (@you@yourname.com) and take it anywhere.
✅ True E2EE for DMs – Real end-to-end encryption for private conversations, a major privacy upgrade.
✅ Relay-based connectivity – Connects to the wider fediverse via relays, so a personal server is practical on mobile.

Open source, privacy-focused, and built to give you real ownership in the fediverse. The Android version is available now.

Donations:
fedilab.app/page/donations/

Open Collective:
opencollective.com/fedilab

@i47iR. P. Scott

There is some terminology used by @HolosSocial that may lead to confusion and needs clarification.

The term "full server" seems to refer to a full server-to-server (S2S) implementation and then hosted client-side, which communicates with the Holos relay server through websockets in order to be able to federate. You might call it a "full server on the client" implementation.

But that is different than what the spec calls a "ActivityPub conformant Federated Server" which also implements the client-to-server (C2S) Social API. I don't see C2S mentioned, and perhaps @appsFedilab Apps can improve the docs here to avoid confusions.

w3.org/TR/activitypub/#specifi

0

If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116079226204223393 on your instance and quote it. (Note that quoting is not supported in Mastodon.)