this post was submitted on 28 Nov 2024
1483 points (99.5% liked)

Science Memes

11448 readers
961 users here now

Welcome to c/science_memes @ Mander.xyz!

A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.



Rules

  1. Don't throw mud. Behave like an intellectual and remember the human.
  2. Keep it rooted (on topic).
  3. No spam.
  4. Infographics welcome, get schooled.

This is a science community. We use the Dawkins definition of meme.



Research Committee

Other Mander Communities

Science and Research

Biology and Life Sciences

Physical Sciences

Humanities and Social Sciences

Practical and Applied Sciences

Memes

Miscellaneous

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] MystikIncarnate@lemmy.ca 1 points 4 weeks ago (1 children)

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.