I will investigate the issue with #HolosDiscover. Since another bot was launched on holm.community, I have been getting several complaints:

- NoIndex/nobot in bio not respected
- Locked accounts followed
- AP flag not honored

I contacted the maintainer to ask whether the code was changed. This should never happen. These complaints only started after that bot appeared.

I am taking this very seriously. If the problem is in my code, I will fix it immediately. Sorry about that.

#HolosSocial will soon get an update (relay + app). The focus is the sync process, which will be more aggressive through the Bloom filter.

Currently, some activities aren't filtered upstream (mostly undo ones), so the device downloads and processes them for nothing. This was a kind of guardrail that's no longer necessary.

With this release, the device downloads far fewer activities (around 80% of what arrived was useless), so sync will get much faster.

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.

https://tom79.dev/posts/holos-relay-1-0-0/

#HolosSocial

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.

#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.

There are three ways to install #HolosSocial on #iOS:

- #TestFlight: join the beta here: https://testflight.apple.com/join/cpjNYF7k

- #AltStore PAL (EU only): open AltStore PAL and find Holos listed inside the app.

- Classic AltStore: use the AltStore link on the website. Do not open it in a browser, as it will only show the raw file. AltStore must open it.

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.

#HolosSocial

For #iOS, I opened #TestFlight for release 1.11.0.

The next release (1.12.0) should be available soon, but if you want to test, here is the link:
https://testflight.apple.com/join/cpjNYF7k

PS: there is a known issue where avatars and headers are not uploaded, which will be fixed after 1.12.0.

#HolosSocial

#HolosSocial is now available on #AltStore PAL

@joergi @benpate @apps Thanks for the ping, and for relaying it :) I just replied on the issue: https://github.com/swicg/activitypub-e2ee/issues/56#issuecomment-4787622299. It took me a bit to clarify my thoughts on this one. I'm on vacation next week, but happy to keep going with you after that.

@joergi @benpate @apps cc @silverpill since this builds on our earlier exchange

I am really happy with my work today, I have never seen the relay so stable and fast. The response time is now really short, around 20 ms, and hasn't moved for hours. I am really close to tagging the first version of the relay as 1.0.0.

#HolosSocial

@silverpill
@mayel @technical-discussion @julian @apps
Following a note is valid: the Activity Vocabulary defines Follow on an object, not only on an actor. ActivityPub assumes an actor, but that is the delivery layer, not a limit on the target. A supporting server tells the two apart by looking at the target: an actor means follow an account, a note means follow a thread. With the same activity, the target gives the meaning, so no need for a custom one.

Following threads will be available in #HolosSocial 1.10.0. You can subscribe to a thread and get notified when new replies arrive, even from accounts you do not follow. It works with standard #ActivityPub activities by sending a Follow targeting a post, with a polling fallback for servers that do not support it yet.

How it works: https://tom79.dev/posts/follow-a-note/

Having lists that mix accounts and hashtags is now possible in #HolosSocial 1.9.0.

To follow a topic, you often need both: a few accounts and the hashtags people use for it. Putting them in one list gives you the full picture in a single feed. It also keeps your home timeline clean, since busy hashtags stay in their list instead of flooding everything else.

@joergi
The custom domain and full account migration feature already works on Holos Social today. On Holos the keys are held by the device, so migration works even if a relay is down: nothing is lost. This is a different approach from a shared server that holds the keys for its users, and it is probably closer to the work of @silverpill on portable identity.
https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md
@dansup

#HolosSocial 1.7.0 is available.
This version adds multi-device support. You can connect a phone, tablet and desktop to the same account. To add a new device, you scan a QR code from one you already use. This transfers your key and all your account data, encrypted end to end, so the relay never sees it in clear.
It also adds bio translation on profiles, actor lists for boost and like notifications, DM filtering, and several fixes.

Full release notes: https://codeberg.org/tom79/Holos-App/releases/tag/1.7.0

#HolosSocial now has a dedicated download page with store links and direct downloads:

https://holos.social/download

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)

#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.