Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Control of distribution is a problem, but control of data makes it much harder for users to switch away from them and use a different distributor.

>>For example: Spotify doesn't own any music copyrights

It has licensing agreements with numerous record labels.



Agree, owning data makes it harder to switch.

A counter example here might be Twitter and Facebook. You can export all your data just fine, but it’s useless anywhere else. Because the reason you’re on Twitter/Facebook is that everyone else is there. They own the distribution of your connections making the data itself useless without them.


True, you can export your Twitter data, but a competitor to Twitter cannot access the entire set of user data that Twitter has access to.

The real differentiator is that with Web3, the data is open, so providing an alternative is as simple as providing an alternative front-end.

What threatens the promise of Web3 are the issues that this article brings up, with decentralized projects not being able to iterate as quickly as centralized ones, leading to proprietary elements becoming the standard for some aspects of widely used Web3 technologies (like NFTs) and establishing a moat for the centralized platform that owns that element.


> but a competitor to Twitter cannot access the entire set of user data that Twitter has access to.

True, but they could make it very easy for users to transfer all their data, which makes it possible if they could convince everyone to do it mass. So the real problem is that it's not realistic to convince everyone to move; the network effect is too strong.

AFAICT, OpenSea et al have the same first mover/network advantage. The record on the chain of a url "belonging" to someone has approximately zero utility without the edifice they've built on top


How does this handle data schemas? Perhaps I’m thinking too much of an RDBMS schema but for Twitter for example. If decentra-Twitter stores my data in some schema (say a hard-coded “pinned tweet” column that only supports one) then is everyone else stuck with that forever? Or could they extend that to include, say, multiple pinned tweets?


I don't have the experience with smart contract development to have an informed opinion on this.

My guess would be that others could extend the protocol, but the challenge would be to get the extension widely adopted.

For example, ERC20 is the primary token transfer protocol on Ethereum, and there are various new token transfer protocols that are supersets of ERC20, and add useful new functionality, but they have not yet gained the widespread adoption to become useful the way vanilla ERC20 is.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: