While opening the server to multiple users during the testing phase, we discovered and fixed a bottleneck in the distribution of activities from the relay's shared inbox. Now that the fix is in place, we'll be reopening registrations on the #Holos relay soon.
holos
#Holos beta-14 is available.
New features:
- Media proxy
- Settings search
- URL truncation setting for posts
- Text selection in posts
- Poll results preview (without voting)
- Keep scroll position when collapsing posts
- Scroll to tapped post in thread
Improvements:
- Improved LoadingScreen
- Profile loading improvements
- Post recovery from inbox/outbox
Many bug fixes (see reply)
Download: https://framadrive.org/s/RZQHjY4fiGsEjq4
(1/2)
As settings become increasingly numerous and nested, we've added a search feature to help you navigate #Holos settings more easily.
We've reopened registrations on #Holos. The first phase helped us identify and fix a bottleneck. All registrations now go through the app. The web version shows where to download it at https://holos.social/signup
Currently we only have our direct download link, but #FDroid/#AltStore and Google Play/App Store (if they accept) are planned.
For push notifications, we recommend #SunUp. The #Holos beta-14 version fixes an issue we had with the #UnifiedPush library. Remember to re-register if you're not receiving push notifications.
RE: https://mastodon.social/@HolosSocial/115906304850499236
Registrations on #holos are now open. Keep in mind this is a beta, your feedback helps us build this project.
It has two components: the App (hosts its own ActivityPub server) and the Relay (provides stable identity).
For advanced users: the relay supports CNAME records, allowing you to use your own domain. This makes you independent from the relay, which becomes just infrastructure.
We fixed the crash in notifications that occurred with messages from GoToSocial. We also added a crash report system (opt-in, disabled by default). Nothing is sent automatically, but you can share the crash code by copy/pasting it. Search results are also fixed, the cache was overwriting webfinger responses for accounts. We're currently working on automatic DB restoration if it gets corrupted. Thanks for your feedback! #Holos
#Holos beta-15 is available
New:
- Crash reporting (opt-in)
- Automatic restore when database is corrupted
Fixes:
- GoToSocial notifications crash
- German language
- Handle search
- Relay outage now shows alert instead of logout
- Relationship persistence (UI bug)
Download: https://framadrive.org/s/ZePLfA5JcGnw4QH
#Holos beta 17 is available. There are several fixes, improvements and some new features to discover.
Full release notes at https://codeberg.org/tom79/Holos-App/releases/tag/beta-17
Download: https://framadrive.org/s/XrNp9m993HZrPNX
Our next goal for #Holos: end-to-end encrypted DMs Your private keys stay on your phone, relay servers can't read your messages. Works across different Holos relays using ActivityPub for transport. Falls back to standard DMs with other Fediverse apps, so servers can read these and we'll show a clear warning. E2E encryption over the Fediverse, finally.
Our dedicated account: @HolosSocial #HolosSocial
RE: https://mastodon.social/@HolosSocial/116007730441888134
We have published a new version of #Holos app (rc-1) that supports #E2EE DMs over ActivityPub.
We wrote a page that explains our E2EE implementation: https://holos.social/e2ee
If you want to discover how Holos app and relay work together: https://holos.social/how-it-works
We are entering a new step in the development of #Holos and we need more people to test.
We have reopened subscriptions through the app: https://holos.social/signup
We wrote a page explaining how we implemented #E2EE DMs over #ActivityPub: https://holos.social/e2ee
Don't hesitate to contribute and share your feedback with us. Thank you.
The #Holos account @tom79@holos.social has been migrated to @tom79 using the new Custom Domains feature.
Use your own domain for your ActivityPub identity. No instance to host, pure ActivityPub from your phone. Your identity is no longer tied to the relay. Switch anytime.
Add your domain, configure a CNAME record, verify and activate. Followers are notified via a Move activity.
More: https://holos.social/custom-domains
Fully available in the next RC release.
#Holos is designed around one device per account since each phone runs its own ActivityPub server. Currently, activities are removed from the relay once synced, so multi-device isn't possible yet. However, we could introduce trusted devices linked to an account, where activities are only removed once synced with all of them. This would also need some work on our E2EE DMs feature.
#Holos 1.0.0-rc-2 has been published. In this version, you can connect your domain to create your unique account identity. The first time, it will send a Move activity so you don't lose your followers/following. Then you will have an identity that no longer depends on the relays, and you'll be free to move between relays whenever you want.
More about custom domains: https://holos.social/custom-domains
Download: https://holos.social/signup
Release notes: https://codeberg.org/tom79/Holos-App/releases/tag/1.0.0-rc-2
Some of you noticed that @HolosDiscover is following you. It's a Fediverse search engine we built to solve a problem: when you start your own server with #Holos, your index is empty. #HolosDiscover provides a ready-to-use content catalog for everyone.
Only public posts from consenting users are indexed. Deletions and edits are reflected in real-time through ActivityPub activities.
How it works: https://discover.holos.social/how-it-works
Open-source (AGPL-3.0): https://codeberg.org/tom79/Holos-Discover
RE: https://mastodon.social/@HolosSocial/116063128397111717
Some positive news for #Holos: the relay now automatically generates SSL certificates for custom domains verified via CNAME, with a job running every 5 minutes to issue and renew them.
This means true ownership of your Fediverse identity: your domain, your name, fully working through ActivityPub. No other server needed, just your phone.
https://holos.social/custom-domains
For custom domains, #Holos currently works with CNAME, which redirects your entire domain to the relay. That's fine for a subdomain, but if you want your identity on your root domain, you probably already use it for something else.
We will add support for that. The relay will handle everything on a subdomain you dedicate to Holos, and automatically generate a webfinger file to host on your root domain. Your identity will be @you@yourdomain.com while the setup runs on a subdomain.
We're looking into implementing interaction controls in #Holos, following the approach proposed by #GoToSocial. This would let you decide who can reply, like, or boost your posts. It fits well with the Holos philosophy of giving you full control over your online presence. More details here: https://docs.gotosocial.org/en/latest/federation/interaction_controls/
We talk about #HolosSocial forgetting some of you might not know this project.
#Holos is a full ActivityPub server running on your device. Currently on Android, next on iOS.
We already introduced #E2EE DMs and #ActivityPub identity through custom domains. You own your followers, your keys, and your identity. Relays are just infrastructure.
On the footer of https://holos.social we added pages explaining the project. Have a look!
Mastodon: @HolosSocial Don't hesitate to share
Having a TTL for your messages, is that something you'd expect? We could introduce an option to automatically delete your posts after a delay (disabled by default, it would be up to you to set your default TTL). We could also allow setting a TTL when composing, so you can customize it at the post level.
The app needs to be online to send the Delete activity to other instances. That said, #Holos already supports pending offline activities.
What do you think?
The new architecture coming in the next release of #Holos allows you to get important messages like Home and Notifications much faster. Even after days offline, the full download enables fast filtering to fill important timelines immediately. This needed some adjustments to the current architecture, but we're very close to publishing rc-3.
#Holos will be available on #FDroid soon, and we hope to get more feedback to improve the project. While #Fedilab uses server APIs, here we can do much more to improve your #Fediverse experience with an #ActivityPub server running directly on your device. We already introduced E2EE DMs and personal identity. We will go further with automatic deletion, even at posting level. You decide the availability of a message. We will also work on interaction controls from #GoToSocial.
A #YunoHost package for #HolosSocial relay server is underway!
This will make it super easy for anyone to deploy their own #Holos relay on their server. We're going to contribute to the packaging effort and would love some help!
If you're familiar with YunoHost packaging, feel free to jump in:
https://github.com/YunoHost-Apps/holos_ynh/
Currently, the #Holos relay has different TTLs depending on activity type. For instance, follow requests stay longer (365 days) while public messages remain for 7 days. Each admin can change these values and they are displayed on the about page. At the app level, you can adjust this value between zero and the max set by the relay. We will also make the relay a little smarter to automatically reduce these values when accounts become inactive, as these are a lot of wasted resources.