Hello Friends,
I started working on a Rotonde client for iOS. It's read only for now because DAT doesn't run on a phone. Dat is also only single writer so a truly distributed system just isn't possible. This requires a new approach to getting a fully featured mobile Rotonde client working. Push notifications for mentions and Direct mentions would also need a conventional Push Notification server.
I see 2 possible solutions to overcoming these limitations on iOS in particular, and perhaps in facilitating richer services for other mobile clients.
Proxy Publishing: Manage your Rotonde DAT on a server and send commands to the server to then commit. This could be accomplished with a simple API. This method would also be compatible with any generic client. The downside is that now the DAT is on the server and a local Rotonde client would be necessary to truly get it off of your computer.
Feed mirroring: A worker process would monitor changes to an external feed and replicate them on your local feed. The Remote feed would be a feed that you post to from a mobile device through proxy publishing. Mirroring would have to be 2 way, the remote feed "mirror" would then also have to replicate your local changes.
I would prefer to figure out a solution that stays distributed while making it ultra easy to start your own Rotonde. The Repeater server seems necessary.
I plan on using Hashbase to automatically persist any DAT created on the Repeater.
Please let me know what ya'll think, or if you have any ideas about how I should structure this.
Hello Friends,
I started working on a Rotonde client for iOS. It's read only for now because DAT doesn't run on a phone. Dat is also only single writer so a truly distributed system just isn't possible. This requires a new approach to getting a fully featured mobile Rotonde client working. Push notifications for mentions and Direct mentions would also need a conventional Push Notification server.
I see 2 possible solutions to overcoming these limitations on iOS in particular, and perhaps in facilitating richer services for other mobile clients.
Proxy Publishing: Manage your Rotonde DAT on a server and send commands to the server to then commit. This could be accomplished with a simple API. This method would also be compatible with any generic client. The downside is that now the DAT is on the server and a local Rotonde client would be necessary to truly get it off of your computer.
Feed mirroring: A worker process would monitor changes to an external feed and replicate them on your local feed. The Remote feed would be a feed that you post to from a mobile device through proxy publishing. Mirroring would have to be 2 way, the remote feed "mirror" would then also have to replicate your local changes.
I would prefer to figure out a solution that stays distributed while making it ultra easy to start your own Rotonde. The Repeater server seems necessary.
I plan on using Hashbase to automatically persist any DAT created on the Repeater.
Please let me know what ya'll think, or if you have any ideas about how I should structure this.