@silverpill @apps You both should collaborate. And Mike and all others with the spirit, too. We need a Mitrazillafedihublab thing. On LAMP stack and android. *freaks out*

silverpill@mitra.social it does sound like the exact use case for C2S. Phone client would use it to communicate with the stable identity server which uses S2S to federate.

Missed the mark there I think.

apps@toot.fedilab.app

@morph @apps I am open for a collaboration, but their implementation might be too different from what I am building. It may use Mastodon API instead of ActivityPub for client-server interactions

@silverpill Yeah I know. Can't these complicated things ever merge somehow in the future? To find an intersection than just the limited Mastodon API standards. You all know that it is not the shiny, fancy things that are missing. Speaking for myself of course.
@apps

@morph Yes, I think convergence is possible.

@apps

Can it viably run on a self-hosted home server as well, as a relay or a backup? How do you handle data restoration in case the phone breaks down or is stolen? And does it allow for multiple devices with the same account?

@apps data storage: databases, files, or some combination thereof?

@apps What kind of bridge?

Like this one? https://codeberg.org/silverpill/activity-connect

@silverpill
Different architecture. Activity Connect bridges actors that can't communicate directly (blocked instances, different networks).

The Holos relay provides stable identity for mobile servers. Your phone runs the actual ActivityPub server, and the relay simply proxies requests to your current tunnel URL. It doesn't bridge or store content - just maintains a permanent address while your phone's IP and tunnel change.

apps@toot.fedilab.app said in We're building something for the Fediverse.:
> Activity Connect bridges actors that can't communicate directly (blocked instances, different networks).

This... sounds potentially problematic at first pass.