Decentralized Postgres
Currently there's no way to easily write a nice client-side Web3 app with similar ease that you would in Web2. In Web2, you spin up a database on an AWS instance, and you have your client-side app call this database to read and write. There is no equivalent in Web3.

building degencast.wtf /degencast . ex-bitmain, binance

You can't just write the data into L1 blockchains, which would be too expensive for most use cases. Storage protocols like Filecoin are primarily designed to archive data, but provide no enterprise-grade performance guarantee (eg. low latency) and familiar interface (eg. SQL) for reading the data.

haha thats what s3.xyz is currently built on. super excited about ceramic 'v2'

andyjagoe.com // denim.vc // tokenizing real-world assets / onchain venture funds @fairmint

ceramic and composedb?

https://ceramic.network/
https://composedb.js.org/

Chasing Curiosity. Empathetic Accelerationist. Founding Fullstack Engineer @icebreaker. YC S16, KB7. 
icbk.me/tayyab.fc

Good and tough question. When do we need to store mutable and structured data on ipfs(or other DSNs) without paying lots of gas?

my somewhat naive wishful thinking is that this might be a better relation of production for data after twitter, reddit, stackoverflow api/data dump change. Combining with data dao/union, we might be able to create a model that is fairer to content creatord and app devs

Why even need a decentralized store? Most clients are closed-source. Build subgraphs or indexers over blockchain data.

World Builder, Prompt Engineer, Brain Compute Psychologist, AI Agent Researcher, Computer Vision Chaos Monkey, Zero Knowledge Debugger 

did w3c spec is more like a "glue".. underlying schema like did:key and did:pkh are just syntax sugar and not much difference from using key pair or chain accounts

Ceramic’s compose db is pretty cool. But who knows where DID will go