Libp2p or similar stack could be used to provide the phone instance an address, caching could be distributed among peers. Of course, as long as other servers also support libp2p.

What would be the up/downsides?

you are viewing a single comment's thread
view the rest of the comments

[–] PrincipleOfCharity@0v0.social 11 points 1 year ago (7 children)

ActivityPub is all about pushing content around to subscribing servers. It sort of expects the subscribers to always be online which would not work for a phone. Servers could resend missed events, but essentially you would miss every event that occurs while the phone is asleep or doesn’t have the app running.

Also, every event that occurs needs to be processed and stored whether or not you are actively looking at it so it would be a huge battery drain while it was running.

It is definitely a service best run on an always-on server with a client application in a phone just asking the server for the latest stuff on-demand.

[–] lalo@discuss.tchncs.de 2 points 1 year ago (6 children)

Events could be cached on the p2p network, so the phone only pings its peers for new content (mind the existing servers would be peers on the network).

[–] Lustucru@sh.itjust.works 2 points 1 year ago (1 children)

“Could be”? I mean yes almost everything is possible but you’re talking about a completely different protocol.

[–] lalo@discuss.tchncs.de 2 points 1 year ago

Not a completely different protocol when the changes are additions to the existing one. The same protocol would still exist and be supported.

load more comments (4 replies)