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)
Post
Replies:
4
Boosts:
1
Two things are done on Holos this week. First, the desktop client is ready for a first release. It shares the same codebase as the mobile app (react-native-web + Electron), with a full ActivityPub server running in the desktop process: OAuth, tunnel, timelines, E2EE DMs, everything works. Going further without user feedback would be premature. (2/5)
Second point, about the bloom filter sync. It had a known limitation: after a long offline period, the relay had to filter a huge queue in one shot. The client was timing out after 60 seconds and was falling back to the legacy mode, which syncs everything without any filter. (3/5)
This is now fixed with a sequenced bloom sync: the relay filters the queue by chunks, and the app consumes each batch before asking for the next one. No more timeout, and no more fallback to the unfiltered mode, even for accounts with more than 100k pending activities. (4/5)
That is where I am now: focusing on the Holos issues open on Codeberg to bring everything together for a 1.6 release, available on both mobile and desktop. (5/5)
