Say someone makes a Web3 Twitter-like app.
To access its content, people would need an interface. Like a Web3 browser. Or a Web3-specific Web2-site.
Making and maintaining such an interface is no easy task, and this will likely be done by a centralized company.
[1/2]
Conversation
Now, what prevents this company from filtering unwanted content at the interface level? And from injecting ads while they are at it?
Unless trusted data is delivered directly into your brain, there is no way of avoiding interface owners messing with this data.
[2/2]
Replying to
Well, theoretically speaking, current (web2) browsers don't filter stuff which is requested, they mostly handle the well-defined protocol.
So if there were web3 browsers I don't see why they can't work the same way.
1
Replying to
There is no reason for this now, easier to ask hosters to remove content. When it is no longer an option, I expect that interfaces will be targeted instead. The protocol implementations can be extended to allow such filtering if there is enough pressure.