1440
Give us your best infodump.
(mander.xyz)
A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.
Rules
This is a science community. We use the Dawkins definition of meme.
webrtc is close to being ok, however there are two primary issues i have with it, one, it's a web standard, so it's implemented into the web, meaning you need a browser to use it. (unless you magically invented an external implementation at which point use a custom one lmao)
outside of that, it uses things like stun and turn, which are nice on the global net, but not something i want, and a potential security concern as well.
idk much about the backend implementation of it, but in most of the applications i've used it, it's complete dogshit and barely passes as functional in most cases. It also comes with this really cool bug where you can't use it cross browser, for some reason, idk what that's about.
Literally all i want is webRTC, but without the dogshit implementation, and just raw-dogging IP traffic so i can point it to a hosted server. I don't want the web features, i don't want to use web traffic, i most certainly don't want to be using TLS and web encryption because it's a required feature to use webRTC on the browser, making it yet more annoying.
It's so close to being a neat and cool standard, but the overly integrated design of it makes it useless for anything that isn't already a thing, like zoom, or discord. Which have pretty ok implementations of it.