okay, but, bad weather is not caused by fossil fuels. quit furthering this falsehood.

Schrödinger’s Backup. nostr:note15awgkn599ds94x9flcn7jljcah7ppy9den8re0qlsn04zm3kkl0qw6a6k9

Just sayin

?kjy_fallback_url=https%3A%2F%2Fmedia.infosec.exchange%2Finfosec.exchange%2Fmedia_attachments%2Ffiles%2F111%2F903%2F128%2F490%2F937%2F328%2Foriginal%2F06903dfa79015bc2.png

WebRTC might be the biggest scam in all the "web" (aka Google Chrome) technologies.

I don't know about the ideas behind creation of WebRTC, but the way it was sold, and has been consistently sold for the last 10 years, is that it is a thing that you can plug in your code and it will magically work.

Oh, right, it also requires a STUN server, but look, you don't have to host anything, there are dozens of free public STUN servers on the internet -- and after that the WebRTC connection is established and you can freely transfer data, voice, video, everything!

Turns out WebRTC is useless without TURN servers, which just relay the entire bulk of the data and, most importantly, are not hosted for free by anyone for anyone else.

To this day developers keep dreaming of a magic peer-to-peer web that can be powered by WebRTC and wasting their weekends writing super nice projects that rely on WebRTC -- without TURN servers -- and therefore do not work at all. The worst part is that they always work when tested locally, generally in the same computer, two different browser tabs or even two different browsers (although in the second case no always).

I'm writing this because I just saw an anonymous developer talking about doing WebRTC signaling over Nostr as if that was the hard part. There is also a WebRTC signaling over Nostr NIP proposal. These things are everywhere. I have myself written at least two projects that relied on WebRTC in the past hoping that time it would be different and p2p would work.

#meme #memestr #nostrmemes #memes 829,862 🤙💜