So the one thing on my #BetterInternet wishlist is browser support for better client-side protocols that decouple apps from services.

Example in thread... 1/n

Suppose I wrote Wordle. I want to sync my stats across multiple devices. Rather than stand up my own server to do this, I just implement something like a SyncedStorageConsumer API.

Meanwhile, Dropbox (or Box or Google or a DIY home-grown solution) implements a SyncedStorageProvider API that sync generic bits of data. When I sign up for a Dropbox account, the browser lets me register Dropbox as one of maybe many storage providers. 2/n

As a user, when I visit my Wordle, the browser then *asks* me where I want to store my stats. It could be the NYT or also Dropbox or Box or whatever. It puts me in control of my data.

Decentralization and data sharing, all in the original Web 2.0 vision of the world without any of the crypto-token Web3 stuff. 3/n

@andy @aftd yeah evaluating Solid for these usecases would be a great thing to do

@danbri @andy Yup, someone posted this just a sec earlier. It looks very promising. Do you know if an app dev needs to stand up a server for this? Or can web JS clients talk directly to Solid Pods?

Follow

@aftd @danbri @andy Yes, apps can talk directly to Pods.

Actually, in my opinion, that's how most (if not all) Solid Apps should behave :).

In case you want to play around with some, I've made a couple that behave this way:

- noeldemartin.github.io/media-k
- umai.noeldemartin.com/

Sign in to participate in the conversation
Noel's Mastodon

This is an instance-of-one managed by Noel De Martin.