During the migration, the relay stopped responding to IPv6. It has been fixed for https://holos.social.
This issue helped find a bug in the app (crash during tunnel creation due to timeout).

The regression when composing is also fixed (save message into drafts prompted when posting).

For TestFlight users, the app is still waiting for validation but everyone who asked to join has been added to the beta testers group.

#HolosSocial 1.3.0 should be available for everyone soon.

To people who love publishing pictures and videos, #HolosSocial allows you to connect your S3 or WebDAV cloud so your media are served directly from your own storage across the Fediverse.
As a direct consequence, there is no size limit and videos are automatically transcoded by your device (from 854p to 1920p depending on your choice).
Every feature in #Holos is built toward full independence on the #Fediverse.

#Holos is now under review for TestFlight! Once approved, I'll add #iOS testers by email invitation (no public link to avoid ghost accounts).
Regarding #AltStore: the current source works with AltStore Classic (sideloading via computer). AltStore PAL (EU marketplace) requires Apple notarization, which I haven't applied for yet.
If you'd like to join the TestFlight beta, send me your email via DM or at hello@fedilab.app. Thanks

#HolosSocial

#Holos is now available via #AltStore for #iOS users.

AltStore source: https://files.fedilab.app/altstore/altstore.json

Learn more about Holos: https://holos.social/how-it-works

#HolosSocial

#Holos 1.2.0 is available

What's new: Markdown preview in the compose screen, import followings from a Mastodon CSV file, separate S3/WebDAV storage for media and backups.

Several fixes app/relay. More https://codeberg.org/tom79/Holos-App/releases/tag/1.2.0

Small bonus for #iOS users, it's available on TestFlight.

#HolosSocial

@silverpill
The relay is a tunnel, not a middleman. It cannot read or alter the content. And with E2EE DMs, even direct messages are only readable on the device.
@jandi @jupiter_rowland

@silverpill
The relay provides a stable identity and makes the device reachable through a tunnel.
The location of keys is not irrelevant. With custom domains, the user controls the domain and the identity. Relays become interchangeable, no Move activity needed. This is an architecture choice, not marketing.
@jandi @jupiter_rowland

Tomorrow, #Holos is moving to a more powerful server. One issue identified was inactive users accumulating a large number of pending activities on the relay. The relay now detects inactive users (no connection for more than 14 days) and reduces home timeline retention to 4 hours, while all notifications (follow, mentions, DMs, etc.) are kept at their normal retention period.

#HolosSocial

Something to clarify about custom domains. This feature lets you own your identity with your domain name. No one else can create an account with it, the relay verifies domain ownership through DNS before activation.
If you want friends or family to have an identity on your domain, you can. As the domain owner, you control who gets one. For root domain identities, this is done through WebFinger configuration, without hosting a relay and even if people are on different relays.

#HolosSocial

Now it's clearly time to let iOS users give #HolosSocial a try. It's still early, but no reason to keep delaying the iOS release. The project is mature enough for both Android and iOS.

@ericbono
It can indeed be confusing at first. With Holos, you run your own server directly on your phone. It's like installing a fresh Mastodon instance: it starts empty. To get started, have a look at the Discover timeline that lets you tailor it to find content by interest. Then follow people to populate your new server.

#Holos started at the end of 2025. A full #ActivityPub server now runs on your phone, with the ability to use your own domain as your identity, #E2EE DMs via Signal Protocol, zero-knowledge encrypted backup, #ActivityPub media served from your own cloud, a tailored timeline based on your interests thanks to #HolosDiscover, and the ability to switch views depending on your mood or the content you want to browse. Thank you for your feedback and support that helped to go through these steps.

#Holos will support custom root domains tomorrow. You'll be able to use @you@yourdomain.com as your identity while #ActivityPub traffic is routed through a subdomain.
With a single user, a simple static json file will be enough on your root domain.

PS: if you already use a subdomain, it will work without extra work.

#HolosSocial

Next step with #Holos and custom domains: being able to use your root domain as your identity. A subdomain would point to the relay via CNAME, but your identity would use your root domain.
I will write a small how-to to make the setup straightforward for everyone.

#HolosSocial

@joergi@chaos.social
I did some tests. The issue only happens when the Holos account is offline (app in the background). I think Pixelfed expects an immediate Accept for non-locked accounts. When it doesn't arrive right away, it fails silently instead of showing "Follow request sent". A locked account would probably work fine since Pixelfed already knows to wait for the Accept in that case.
That's just my assumption from tests, it needs to be confirmed.
@dansup @joergi@punk.photos @joergi@holos.social