Post B5fJGsU04W9RckaWHY by apps@toot.fedilab.app
 (DIR) More posts by apps@toot.fedilab.app
 (DIR) Post #B5fHLcJjP2YH1iuujQ by apps@toot.fedilab.app
       0 likes, 0 repeats
       
       #HolosSocial is a project that lets users run their own #ActivityPub server on a device (Android/iOS). Would a desktop version interest you? For purists, dynamic DNS could replace the relay entirely, which is simply not realistic on mobile.Main account: @HolosSocial Your opinion?
       
 (DIR) Post #B5fIfjzwegImaup0q0 by fox@hostnetwork.xyz
       0 likes, 0 repeats
       
       @apps @HolosSocial in my opinion this entire project is stupid. If the relay goes down you're still going to find a new one and you aren't directly connecting to stuff anyways. Also the amount of bandwidth a instance needs isn't too mobile friendly
       
 (DIR) Post #B5fJGsU04W9RckaWHY by apps@toot.fedilab.app
       0 likes, 0 repeats
       
       @foxAny instance can go down, that is not specific to Holos. With a custom domain, switching relay loses nothing because data lives on the device. The relay is not a proxy: activities are signed locally, and a bloom filter limits sync to what concerns the user. Bandwidth on mobile is precisely what this design addresses.@HolosSocial
       
 (DIR) Post #B5fNRfP9R6vm44ihpQ by deutrino@mstdn.io
       0 likes, 0 repeats
       
       @apps @HolosSocial relay support would be one way to support laptops. if you spend the effort to build a desktop release, ideally it should support both relay and direct operation for 3 modes of connection: relay, direct (with port forwards), and direct (reverse proxy)