Hacker News new | past | comments | ask | show | jobs | submit login

Doing http over webrtc is how https://camect.com works to let one access cameras own private server via their ui. They have a centralized bit for auth and then use webrtc and a physical nvr to serve your videos maximally efficiently...so there is low risk of their cloud becoming a financial burden that they cancel ala google nest cams

It's a super nice architecture




So from your explanation I get that they use webrtc for videos. But then what do they use http over webrtc for? Do they serve the UI as well over webrtc?


Their ui is also hosted on the nvr, they serve ui assets over webrtc


> have a centralized bit for auth

Theoretically they could get the camera itself do auth, and then the server becomes fully 'dumb', and need not even be service specific.


Oauth is nice and convenient.


Sounds kind of similar to Frigate but packaged up ready to go, neat.


I am an early backer and have been using it for few years bow. Camect is great.


How soon do you think IT will clamp down on webrtc?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: