If you encounter issues with #HolosSocial, you can help by enabling crash reports. Go to Settings, search for "Crash Reports", and enable it. Reports are stored locally on your device, no data is sent externally. You can view, copy, or share them on the issue tracker:
https://codeberg.org/tom79/Holos-App/issues
holossocial
#Holos 1.5.3 is available.
New: in-app notification banner when interactions arrive while using the app. Tapping a DM notification now scrolls to and highlights the message.
Leading mentions are no longer shown in DM conversations.
It also brings a fix for a UI freeze during inbox cleanup.
#HolosSocial will soon reach #Fdroid official builds and also be available on Google Play. For #iOS, it is already on TestFlight and #Altstore.
The relay has been reduced to its minimum of dependencies, but remains necessary. Currently, only https://holos.social exists.
You could host a relay in a different region (currently Europe). The goal is not to have one big relay with smaller ones around it.
Please share. More about it: https://holos.social/how-it-works
Account: @HolosSocial
RE: https://pdx.social/@kenjen/116466693065651278
For Android users on #Obtainium, this link adds #Holos in one tap, with updates pulled from the custom #FDroid repo:
https://apps.obtainium.imranr.dev/redirect?r=obtainium://app/%7B%22id%22%3A%22social.holos.app%22%2C%22url%22%3A%22https%3A%2F%2Ffdroid.fedilab.app%22%2C%22author%22%3A%22Fedilab%20Apps%22%2C%22name%22%3A%22Holos%22%2C%22preferredApkIndex%22%3A0%2C%22additionalSettings%22%3A%22%7B%5C%22appIdOrName%5C%22%3A%5C%22Holos%5C%22%2C%5C%22pickHighestVersionCode%5C%22%3Afalse%2C%5C%22trySelectingSuggestedVersionCode%5C%22%3Atrue%2C%5C%22trackOnly%5C%22%3Afalse%2C%5C%22versionExtractionRegEx%5C%22%3A%5C%22%5C%22%2C%5C%22matchGroupToUse%5C%22%3A%5C%22%5C%22%2C%5C%22versionDetection%5C%22%3Atrue%2C%5C%22releaseDateAsVersion%5C%22%3Afalse%2C%5C%22useVersionCodeAsOSVersion%5C%22%3Afalse%2C%5C%22apkFilterRegEx%5C%22%3A%5C%22%5C%22%2C%5C%22invertAPKFilter%5C%22%3Afalse%2C%5C%22autoApkFilterByArch%5C%22%3Atrue%2C%5C%22appName%5C%22%3A%5C%22%5C%22%2C%5C%22appAuthor%5C%22%3A%5C%22%5C%22%2C%5C%22shizukuPretendToBeGooglePlay%5C%22%3Afalse%2C%5C%22allowInsecure%5C%22%3Afalse%2C%5C%22exemptFromBackgroundUpdates%5C%22%3Afalse%2C%5C%22skipUpdateNotifications%5C%22%3Afalse%2C%5C%22about%5C%22%3A%5C%22%5C%22%2C%5C%22refreshBeforeDownload%5C%22%3Afalse%7D%22%2C%22overrideSource%22%3A%22FDroidRepo%22%7D
Thanks @kenjen for sharing.
#Holos 1.5.4 is available.
Activity delivery now goes through the relay proxy, which fixes boost and like failures on #iOS. Sync performance is also improved.
It also brings several fixes: images disappearing after posting, the iOS "No valid public key" error during setup, and the custom relay tunnel URL being ignored.
#HolosSocial 1.15.0 is available.
This release brings moderation tools for the relay staff, and an account standing page where everyone can see if they have strikes from a relay, with the possibility to appeal. A post preview is now shown in grouped notifications.
It also brings several fixes, including boosts not reaching all followers servers, blocked accounts in hashtag tracking, and a stuck sync notification draining the battery.
Release notes: https://codeberg.org/tom79/Holos-App/releases/tag/1.15.0
Recently I tagged the #Holos relay 1.0.0. Some of you were interested in the numbers behind it: how much memory it needs, how much disk space, and so on. I wrote a short blog post about that.
Beta-17 of #HolosSocial brings improved speed and stability, especially for the database. We've identified and fixed the issue causing crashes and slowdowns. S3/WebDAV backups are functional, you can even use both simultaneously. An automatic cleanup tool is available, customizable to your needs. Just search "backup" or "cleanup" in settings to check these options.
With #HolosSocial, we introduced the same feature that is on #Fedilab to discover videos from the Fediverse thanks to #SepiaSearch (https://sepiasearch.org).
#PeerTube devs offered this option, which is really helpful for discovering new content on their platform.
We might introduce peer-to-peer streaming soon when watching PeerTube videos, with an option to disable this behavior.
Their API is used to display the content, then actions work through ActivityPub.
Regarding the critical PHP vulnerability, only two projects were affected and have been shut down (I will update them tomorrow): #Fediplan and the MediaWiki.
All other projects, such as #HolosSocial, #HolosDiscover, #Fedihood and #Pawfed, were not affected.
Concerning #HolosSocial, I still believe it's an interesting project because it brought something new to the #Fediverse.
Not only because you run your #ActivityPub server on your device, but mainly because you can own your identity with your own domain name.
My mistake was making it easy to run the server on your device, but not to get your own identity.
That will be my challenge in the coming months.
PS: I have no funding for this project and I work alone, so yes, it takes time :)
#HolosSocial is not abandoned. I've put too much work into it to give up.
During this time, the relay has proven very stable without any intervention. The sync process (a Bloom filter based on the following list) has greatly reduced the amount of synced data.
It can still be improved by allowing some background syncing over Wi-Fi, to avoid long syncs after being offline for days.
I should be able to publish the next release in November (Android, iOS, Mac and Linux).
The next #Holos release will support reactions. Long press the like button to pick one. It will be compatible with other software that supports reactions like Pleroma, Akkoma, Misskey, Sharkey, and Firefish. Can be disabled in settings.
#HolosSocial is now accepted on the iOS store. Verification emails aren't being delivered at the moment. I will approve subscriptions manually and fix this shortly.
With #HolosSocial, your account lives on your phone. Your keys, followers and posts stay with you. The relay only holds incoming activities with a TTL, so your device can catch up when it reconnects.
The cost of that privacy: lose the phone or uninstall without a backup, and the account is gone.
Cloud backups exist for those who set them up. For everyone else, an encrypted backup through the relay is offered as a last resort. You pick a passphrase, the relay stores a sealed copy it cannot open.
The next release of #HolosSocial will fix the update issue for Apple.
It will also let you write personal notes on profiles, along with many other fixes, enhancements and additions that will improve your experience with the app.
In a few days, the last brick of the relay server will be published for an official release and a tag.
A lot of stress when you are alone, but after a few weeks the work has paid off, it is really stable.
Running your own #ActivityPub server on your phone will be as simple as using any other app. You will not be limited to a lookalike: micro-blogging, media, videos, all you want in a simple tap.
A new version of #Holos has been released (1.5.5).
It introduces support for "web+ap://" links (fedilinks), so profiles and posts can now be opened directly in Holos. The sync experience is also smoother with less UI freezing, and post deletion is more reliable: posts are kept locally until all remote instances confirm removal, with automatic retry on failure.
Release notes:
https://codeberg.org/tom79/Holos-App/releases/tag/1.5.5
Now #Fedilab and #HolosSocial use "web+ap://" to open messages or profiles inside the app, like Conversations does (https://github.com/tuskyapp/Tusky/issues/5027).
#HolosDiscover now has a dedicated button to open messages in apps supporting it.
#HolosSocial should not take too much space on your device. First, it has automatic cleaning features that you can tailor to your needs. It also uses bloom filters that automatically remove unwanted activities from the relay. On my own server, almost 14k posts take only 225 MB, less than a few photos.
Today, I updated the documentation for installing a relay (Docker, manual, automatic script).
Behind the scenes, I reproduced each installation to adapt and fix the doc.
Yes, the official #HolosSocial relay is coming to production after a long 10 months of work. The #YunoHost package will come next.
Around 800 users on a relay is a small number of GB, everything is optimised, and it can run on a small VPS.
I am quite proud of this work. Thank you for making it possible with your support.
The next release of #Fedilab will handle refreshes correctly with reversed timelines, especially the pull to refresh.
The #HolosSocial PR has also been merged on #FDroid, so the build is coming very soon.
A hypothetical about chat control and #HolosSocial
Say a law one day required client-side scanning. The relay only ever sees encrypted data, so a scan would catch nothing. To read content, it must run in the client, before encryption. A closed client could add it silently in an update. An open one cannot: the code is public, anyone can recompile without it.
Would an open source #E2EE messenger on the #Fediverse like Holos be breaking the law if it did nothing? I am not sure. Your opinion?
We are now in a stabilization phase for #Fedilab. We are waiting for the green light from beta testers before releasing 3.36.0.
We will work on #HolosSocial (@HolosSocial) for a few days to fix issues and bring E2EE for DMs.
#Holos is available on #FDroid
https://f-droid.org/packages/social.holos.app/
A huge thank you to the F-Droid team for their invaluable help!