Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Web3 – An Arrogant and Treacherous Successor Doomed to Fail

g147.medium.com

Post reply on HN
Print view View original

1–10 of 267 posts

Re: Web3 – An Arrogant and Treacherous Successor Doomed to Fail

#5

Post by bhhaskin »

ugjka wrote: post #3

I seriously do not see and never saw how "Web 3.0" is a follow up from web 1 and 2. The whole thing was a hijack by ponzi schemers or just another way to get someone to get their life savings into some crypto nonsense.

It's all just marketing.

Re: Web3 – An Arrogant and Treacherous Successor Doomed to Fail

#7

Post by plopz »

superkuh wrote: post #6

Web3 is irrelevant. Actual Web 3.0 isn't anything blockchain based. Web 3.0 is the total corporate take-over of the entire web by Google/MS/Apple requiring CA based TLS in the HTTP/3 (QUIC) implementations in their browsers.

i just want to be able to use udp without the headache of webrtc

Re: Web3 – An Arrogant and Treacherous Successor Doomed to Fail

#8

Post by roody15 »

ugjka wrote: post #3

I seriously do not see and never saw how "Web 3.0" is a follow up from web 1 and 2. The whole thing was a hijack by ponzi schemers or just another way to get someone to get their life savings into some crypto nonsense.

Exactly… NFT’s blah blah .. blockchain everything .. came off as like a sales pitch and never seemed to resonant as where the web was headed

Re: Web3 – An Arrogant and Treacherous Successor Doomed to Fail

#9

Post by superkuh »

plopz wrote: post #7
superkuh wrote: post #6

Web3 is irrelevant. Actual Web 3.0 isn't anything blockchain based. Web 3.0 is the total corporate take-over of the entire web by Google/MS/Apple requiring CA based TLS in the HTTP/3 (QUIC) implementations in their browsers.

i just want to be able to use udp without the headache of webrtc

Webrtc websockets implementations (and spec!) are corrupted too. They require TLS even for localhost. But at least you can still use self-signed certs so it's not as bad as HTTP/3.

It's kind of crazy to think that smartphones' inability to hold open a TCP connection (and thus the desire for UDP) are managing to ruin the entire (non-commercial) web.

Post reply on HN