Smart TVs, TV sticks, and a lot of mobile devices will not be capable of decoding AV1 in software in realtime, given their low-spec CPUs. I imagine that Netflix is only serving AV1 to devices with hardware decoding support.
Live translation is a well solved problem by this point — the translation will update as it goes, so while you may have a mistranslation visible during the sentence, it will correct when the last word is spoken. The user does need to have awareness of this but in my experience it works well.
Bear in mind that simultaneous interpretation by humans (eg with a headset at a meeting of an international organisation) has been a thing for decades.
I have the G1 glasses and unfortunately the microphones are terrible, so the live translation feature barely works. Even if you sit in a quiet room and try to make conditions perfect, the accuracy of transcription is very low. If you try to use it out on the street it rarely gets even a single word correct.
This seems like the solution getting ahead of the problem. A series of API requests over HTTP can easily use a persistent connection and will practically default to that with modern client and server implementations. A claim that a more complex approach is needed for efficiency should be accompanied by evidence that the simple approach was problematic.
MCP can use SSE to support notifications (since the protocol embeds a lot of state, you need to be able to tell the client that the state has changed), elicitation (the MCP server asking the user to provide some additional information to complete a tool call) and will likely use it to support long-running tool calls.
Many of these features have unfortunately been specified in the protocol before clear needs for them have been described in detail, and before other alternative approaches to solving the same problems were considered.
> Airpods pro: Keeps disconnecting. ANC keeps turning on and off, living its own life. Sometimes only one side has sound. But it doesn't sound bad, when it works. It doesn't happen very often though. Too bad Apple ran out of SW developers.
Given the popularity of the product you’re presumably aware this isn’t a typical experience. I certainly haven’t encountered disconnects or ANC switching off uncommanded, and the only time I get one-sided sound is if one side runs out of battery. You might consider asking Apple to replace them.
I'm guessing you're in the US? Haven't had any problems with IPv6 on ISP-supplied routers in UK, NL, DE, CN, HK, VN, TH, SG over the last 10y or so, seems like a solved problem for most of the world.
You can fix this on the AP side with minimum RSSI or data rate control. But that would probably push you over to either Ubiquiti (and the similar “cloud based” options) or the enterprise market to get those features, unfortunately.