Now-a-days, I want to have conversations about the merits of one routing protocol over another in various contexts, and see/build a spine and leaf network infrastructure that’s nearly infinitely scalable.
bro i just want screensharing that isn’t using the hell that is webrtc.
How hard is it to send video packets over IP, it can’t be that difficult. Half the job is already done, and i can’t imagine building a reliable networking protocol, even if you had to do it from scratch would be particularly hard.
See, I only recently came into awareness that web RTC was a thing. I have a lot of learning to do on how it even works as a protocol.
I’m sure it runs on top of IP, so I think web RTC meets your curriculum here. Regardless of that, I think I know what you mean, and if I knew enough about the protocol, I might even agree.
I need to brush up on the new protocols that are getting to be very common. I’m almost entirely up to date on the 802.11 specs, but there’s so much to keep track of… Yikes.
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.
bro i just want screensharing that isn’t using the hell that is webrtc.
How hard is it to send video packets over IP, it can’t be that difficult. Half the job is already done, and i can’t imagine building a reliable networking protocol, even if you had to do it from scratch would be particularly hard.
everything is webrtc, it always has been.
See, I only recently came into awareness that web RTC was a thing. I have a lot of learning to do on how it even works as a protocol.
I’m sure it runs on top of IP, so I think web RTC meets your curriculum here. Regardless of that, I think I know what you mean, and if I knew enough about the protocol, I might even agree.
I need to brush up on the new protocols that are getting to be very common. I’m almost entirely up to date on the 802.11 specs, but there’s so much to keep track of… Yikes.
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.