←back to thread

WebSockets cost us $1M on our AWS bill

(www.recall.ai)
362 points tosh | 1 comments | 06 Nov 24 18:50 UTC | HN request time: 0.215s | source
Show context
cosmotic ◴[06 Nov 24 19:25 UTC] No.42067844[source]▶
Why decode to then turn around and re-encode?
replies(3): >>42068029 #>>42068118 #>>42068185 #
pavlov ◴[06 Nov 24 19:42 UTC] No.42068118[source]▶
Reading their product page, it seems like Recall captures meetings on whatever platform their customers are using: Zoom, Teams, Google Meet, etc.

Since they don't have API access to all these platforms, the best they can do to capture the A/V streams is simply to join the meeting in a headless browser on a server, then capture the browser's output and re-encode it.

replies(1): >>42068689 #
MrBuddyCasino ◴[06 Nov 24 20:18 UTC] No.42068689[source]▶
They‘re already hacking Chromium. If the compressed video data is unavailable in JS, they could change that instead.
replies(2): >>42068828 #>>42069540 #
1. moogly ◴[06 Nov 24 20:28 UTC] No.42068828[source]▶
They did what every other startup does: put the PoC in production.