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

Chiang Mai, Mueang Chiang Mai District, Chiang Mai, Thailand

Great idea. Bad documentation. I think a Cosmos for Ceramic will be more successful. 

You need something a bit more customizable based on your data type. Also, it only enforces data types but not other “read/write” permissions. 

I like Tableland.xyz

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

tableland access control is definitely superior than ceramic. just don't like the fact write need to be onchain.. https://i.imgur.com/NKI1rnr.jpg

Leading research @textile. Reading, writing, arithmetic.

possible to make it such that access control is on-chain while data mutation is done offchain

example use case is, build a fc 'protocol' clone using a general data layer without using hubs

data need to be:
1. verifieable (self authenticated as coming from a certain user)
2. availabile 3. consistent 4.  could be private or public

how does the value prop of threadsdb compare to tableland? are they related in any way at all?

Hey, member of the tableland team here. Would love to hear your thoughts on alternatives to on-chain mutations. We've been exploring alternatives like ipfs hashes and other forms of verifiable off-chain data "dumps". Would love to hear your usecases for this type of thing!