Hacker News Reader

Thank you, but I am more interested in what can be the system architecture. It would be an obvious choice to push this to the client side, but with lower end decides it can be slow. If we push it to the server then the stream can have delay and it would cost a fortune.

View on HN

Nothing has to be pushed to the server. Computer vision like edge recognition is done solely on the client. Client dont have to fast and can be very slow. What takes the most the computer power is the compression of the video stream. This is also done on the client side.

for that you also do not need convolutional networks or object recognition or ML, nor pretrained models. Its pure "Do pixel x change within time t, set pixel y = 1. If no change in x, then y = y-z, with z as a factor. If y < threshold, apply blur"

I am not sure because, eh, I'm not using lower end devices, but it seems that the most reasonable way would be the browser to check for the capabilities declared by the graphics drivers and then decide if they offer the option of background blurring.

I don't think doing it server side would be cost efficient.

Reply on news.ycombinator.com