@erebion I think the cardinal sin of a lot of these projects is append only operation logs that demand sequential processing for the system to work. It's a beautiful design for database replicas but awful for clients which have a lot of downtime and need catching up periodically.
@baibold Oh wow this is so good, thank you for the link!
Pretty sure it was how I found "stuffonmycat.com" and articles about populating cell matrices with animal cells with the goal of making replacement organs.
@caten Brutal 💀 Not unexpected sadly.
@Aaron_Davis I don't think it's been a thing for over a decade now. :P
@suricrasia i could imagine a 2 hour videoessay on the topic
@erebion Yeah I feel a bit sad that the core of it requires processing so much data on the client side to function. I kinda wish the client-server API was more focused on sparse loading to enable thinner clients.
@suricrasia ty for making this! It is a very good set of feelings for my brain stem.
@taq Nope! Entirely hand written :P
I used it a bit to remember the syntax for camera capture for some of the example apps though.
@taq Yeah I'm trying to see the smallest possible option to work accross devices while being able to generate usable code snippets.
Mozilla #pocket shutting down is exactly why we should be building on top of #p2p data trasfer foundations. Depending on cloud services means it's just a matter of *when* the service will shut down or make your usual flows inaccessible.
The thing is, with tools like #agregore it's way easier to make and distribute small apps that are local to your or your friend's devices.
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Exploring what a local-first cyberspace might look like in my spare time.