The desktop interface of #HolosSocial will be quite simple and #E2EE already works great.
holossocial
Change of plans for this week, and I apologise for moving things around. I was supposed to get back to #Fedilab mid week for the 3.40.2 release, but I will postpone it. I am very focused on #HolosSocial at the moment, and stopping now to come back a few days later would cost too much in context switching, both in time and in concentration. Fedilab 3.40.2 will follow right after the next #Holos milestone (end of the week). (1/5)
The fundraiser for a new computer is still ongoing.
This machine is what keeps #HolosSocial, #Fedilab, #Castlab and #Fediplan moving forward on Android, iOS, and soon #Holos on macOS, Windows and Linux, from a single codebase. The current setup is reaching its limits.
Full story:
https://ko-fi.com/post/A-new-computer-to-keep-building-for-every-platform-B0B61ZONP2
Every contribution helps, and sharing helps too :). Thank you.
#Holos 1.3.0 is available on #FDroid and #AltStore
What's new: Quote posts from other Fediverse clients are now supported.
Several fixes on timelines, notifications, tunnel stability, and compose screen.
https://codeberg.org/tom79/Holos-App/releases/tag/1.3.0
For AltStore: https://files.fedilab.app/altstore/altstore.json
We made so many improvements with #HolosSocial, an ActivityPub server running on your phone. Big thanks to our beta testers who help us identify issues and suggest enhancements.
For tech folks: imagine pointing your domain with a CNAME to a relay and having your own ActivityPub identity with keys and data on your phone. The relay becomes just infrastructure, and you're free to move to another relay whenever you want.
That's the crazy bet we're working on!
More are at @HolosSocial
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
I built #HolosSocial for Linux (AppImage and deb files), and it works just fine on my Raspberry Pi.
#Holos 1.6.0 is available!
This release introduces desktop support with Electron on macOS and Linux. Syncs now use a sequenced bloom filter with WebSocket filtering that will avoid timeouts when starting the app.
The media viewer should be smoother, with instant thumbnails and a transition from the thumbnail position.
Full release notes: https://codeberg.org/tom79/Holos-App/releases/tag/1.6.0
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 has been migrated to @tom79@holos.fedilab.app 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.
#HolosSocial relay is confirmed to be very stable. I will officially tag it soon so admins can run their own relay with a script to easily install it on their VPS.
Using Holos with a custom domain and a cloud for media allows you to own your portable identity on the #Fediverse. Relays become only an infrastructure for it. Your device runs the #ActivityPub server and works as smoothly as any other app. Micro-blogging, media, and video, all from a single account. Switch with a simple tap.
#HolosSocial isn't bringing something new to the #Fediverse, especially not to #ActivityPub. It builds on what exists, without mimicking any platform.
Every social network has been given its fediverse clone. Asking people to hold a separate account on each is taking the problem backwards.
If the fediverse keeps mirroring the GAFAM, it loses. The point was never to rebuild their world, but to offer something else: one identity across every content.
HolosSocial is simply a try. But we can do it.
#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
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.
Most people know about messages, photos and videos on the #Fediverse. But the #ActivityPub protocol actually defines several object types, each one distinct and more or less compatible across apps:
- Note: short post (Mastodon)
- Article / Page: long text or shared link (WriteFreely, Lemmy)
- Image (Pixelfed)
- Video (PeerTube)
- Audio (Funkwhale)
- Event with date and place (Mobilizon)
(1/4)
Multi-device support is progressing well for #HolosSocial. The tricky part: each device runs its own #ActivityPub server, with its own local data, signing its own activities. Keeping several servers in sync both ways, without duplicating everything, without losing actions on the way, and without two of them handling the same activity at the same time, was the main problem to solve. It also had to stay reliable when a device goes offline for hours or days.
(1/3)
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/
In #ActivityPub, once a post is federated, you lose control over how remote instances handle interactions on it. Some servers like #GoToSocial are working on interaction controls, but non-compatible instances simply ignore your rules.
With #HolosSocial, we're considering a "safe mode" available at publishing time. Your post would only be delivered to followers on instances that respect interaction controls. Not enabled by default, but there for those who need it.
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.