This is especially true for public user generated content. Any public content should be accessible without limits, but that is not the case with web2(twitter, public Instagram, forums etc).
ofcourse, there are some server costs but the primary reason the walled-gardens do this is more business related than to reduce costs.
There is zero weight to the claim. Not only does it ignore an massive amount of improvements since the early 90's, it seems to completely ignore what Web 2.0 was about.
> Any public content should be accessible without limits,
This is not related to the discussion, even if I did agree with it.
> but that is not the case with web2(twitter, public Instagram, forums etc).
Twitter and "forums" are all completely accessible via a browser, which is literally what the original claim suggests we've "lost". You don't need to read twitter with a special twitter client, you read it with the any HATEOAS client.
> ignore an massive amount of improvements since the early 90's
That's not the point. having massive improvements since 90s does not imply that we are going to continue from the same path from here on.
> completely accessible via a browser
accessible via a browser is not the same as accessible / interoperable broadly.
> You don't need to read twitter with a special twitter client
YES, some people want to. or maybe I want to do some data analytics, maybe I want to create a localized twitter, or I want to do take public social graphs and do something with it.
web2.0 was about standardizing transport level protocols, web3 is(imo) about standardizing application level protocols using commitment guarantees.
When I use some web2 service, there is almost no commitment guarantees(you can get censored, your data might be access gated or deleted, banks can stop you from doing certain transactions).
Crypto and web3 is about fixing these issues. If Bitcoin promises to work in a certain way today, it will more likely than not work in the same way 10 years from now.
if "web3" works anything like crypto, there wouldn't be any rate limiting as long as you have control over your own node(it might be more expensive / harder to set one up though).
This is especially true for public user generated content. Any public content should be accessible without limits, but that is not the case with web2(twitter, public Instagram, forums etc).
ofcourse, there are some server costs but the primary reason the walled-gardens do this is more business related than to reduce costs.