Liang @ degencast.wtf 🎩
@degencast.eth
gm! thought on ceramic.network ?
4 replies
0 recast
0 reaction
Tayyab - d/acc
@tayyab
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
6 replies
0 recast
0 reaction
Liang @ degencast.wtf 🎩
@degencast.eth
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
1 reply
0 recast
0 reaction
cjqf
@carsonfarmer
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!
4 replies
0 recast
0 reaction
Liang @ degencast.wtf 🎩
@degencast.eth
how does the value prop of threadsdb compare to tableland? are they related in any way at all?
1 reply
0 recast
0 reaction
cjqf
@carsonfarmer
Not really in any practical sense. Two very different approaches to the problem of distributed data. ThreadDB was designed for pure p2p sync, whereas Tableland network will end up being more federated. ThreadDB relies on peers to make data available, whereas Tableland relies on blockchains for data availability...
2 replies
0 recast
0 reaction
Liang @ degencast.wtf 🎩
@degencast.eth
interesting tradeoff there
0 reply
0 recast
0 reaction
