Search
Items tagged with: Holos
RE: mastodon.social/@HolosSocial/1…
Root domains are now available with #Holos.
The account @tom79 is an example. It uses the subdomain holos.fedilab.app with a CNAME to holos.social and it only contains a static JSON file to serve the WebFinger response (codeberg.org/tom79/website/src…).
Holos Social (@HolosSocial@mastodon.social)
#Holos 1.1.1 has been published. You can now use your root domain as your identity with a simple TXT DNS record. If you have only one user, a static JSON file is enough. #HolosSocialHolos Social (Mastodon)
RE: mastodon.social/@HolosSocial/1…
With #Holos, you can have your identity on your own domain. No server? A simple CNAME record is enough. Already have a server? Point a subdomain to handle #ActivityPub traffic and serve a static JSON file on your root domain.
This is a step toward the same sovereignty #Nostr offers with cryptographic identities, but staying in the #ActivityPub ecosystem you already know.
Holos Social (@HolosSocial@mastodon.social)
#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.Holos Social (Mastodon)
RE: mastodon.social/@HolosSocial/1…
The next step with #HolosSocial will be to let you use your root domain as your identity while still using a subdomain for the relay.
Yes, #Holos is kind of like #nostr but with #ActivityPub. The main difference: your data lives on your device, not on a server, and relays remain completely dumb.
Holos Social (@HolosSocial@mastodon.social)
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.Holos Social (Mastodon)
#Holos 1.1.0 has been released.
Account recovery is now available: optionally back up your account data with a passphrase and restore it after a reinstall (strongly recommended if you have no cloud backup configured).
The relay stores your backup but cannot read it, it is encrypted on your device before upload (zero-knowledge).
Recovery is managed in Settings > Data & Backup.
Release notes: codeberg.org/tom79/Holos-App/r…
Release 1.1.0 - tom79/Holos-App
## Added - Account recovery: back up your identity with a passphrase so you can restore it if you reinstall the app - Recovery management in Settings > Data & Backup - Push notifications now work even when the app is in background ## Fixed …Codeberg.org
RE: mastodon.social/@HolosSocial/1…
#Holos 1.0.0 is available! With this release, Holos moves from release candidate to production. Your phone becomes your server. With custom domain support, your identity can truly be yours, independent from any platform. Your DMs are end-to-end encrypted. Your data stays yours. This is the core principle behind Holos, and the goal is to make all of this accessible to everyone.
#HolosSocial (1/4)
Holos Social (@HolosSocial@mastodon.social)
Attached: 1 image #Holos 1.0.0 is available! With this release, Holos moves from release candidate to production. This version adds a reverse timeline option to display posts oldest-first.Holos Social (Mastodon)
RE: mastodon.social/@HolosSocial/1…
We will introduce the #HolosDiscover API in #Fedilab. It allows to tailor a timeline with up to 20 tags. It can be really useful for small instances.
However, unlike the #Holos app where posts from blocked or muted accounts are filtered out, Fedilab won't be able to apply these filters.
In the next release of #Holos, Bloom filters will be enabled by default (can be disabled). This allows the relay to deliver only activities that matter to you, without ever knowing who you follow. In practice, this reduces data transfer around 97%, since only about 3% of activities are typically relevant during a sync.
The public timeline is replaced by a discover timeline tailored to your interests.
In the next #Holos release: post expiration. When composing, you can set a lifetime for your post, from 1 hour to 90 days.
The post will be deleted at minimum after the chosen time, since the app needs to be open and connected to send the Delete activity to other instances.
Still a handy tool if you don't want your posts to last forever.
