Scuttlebutt [1] - a server-less (p2p) protocol for async feeds publication - looks really interesting. Primarily designed for social platforms, but many other uses come to mind (camera/sensor feeds, serverless git)
[1] ssbc.github.io/scuttlebutt-pr
Conversation
Patchwork seems to be the most popular reference implementation of a client app which provides a social platform service on top of this Scuttlebutt protocol.
There is also an Android Manyverse app by which looks v. promising.
Sadly no iOS app (...seriously?)
3
3
6
Probably because iOS limits a lot of P2P apps, DHT usage is going to be problematic, especially the ability to get notifications when the app isn't in focus. Have to proxy via a home node, or else it will be difficult to maintain connections.
1
To expand on this, Android apps can run as a foreground service and request a battery optimization exception from the user to implement their own push, rather than using FCM. On iOS, there's no alternative to using the platform's push messaging to wake the app for notifications.
1
If it's important for it to stay connected in the background, especially if it takes some time to get initialized, that forces it down the path of a foreground service + asking user for battery optimization exception. iOS apps don't have an escape hatch to keep running like that.
I think the early limitation was that there was no nodejs implementation on iOS, and a lot of the underlying platform libs (handshake, wire formats, rpc etc) were JS/npm modules. However that is changing now with Rust/C core libs - all in various stages of beta.
1
1
Show replies