Removing film crew, boom mics, and missed props from a scene would surely be useful to studios. It may even enable some shots that previously would have been impossible due to the positioning of cameras, etc.

Windows has a native (cloud-based) dictation software built-in[1], so there's likely less demand for it. Nonetheless, there are still a handful of community options available to choose from.

[1] https://support.microsoft.com/en-us/windows/use-voice-typing...

Bazzite KDE picked up my 8BitDo controller immediately, with no prior configuration. I didn't even have to manually pair the Bluetooth. I was very impressed.

Many people will likely be watching this show for the first time based on this thread. Please don't spoil major plot events for them.

This thread is already filled with spoilers, so it feels odd that you're singling mine out and especially given how long the show's been out.

Just in case you missed it, your quote was referring to encoding requirements. Decoding (eg. Netflix users) will have a different set of requirements. The situation will also improve over time as dedicated hardware encoders and decoders become available.

For the moment, I don't really mind if it requires more GPU power to encode media, since it only needs to happen once. I expect it will still be possible on a weaker card, but it would just take longer.

Contextual permissions are a big improvement over early and uncertain prompts. I will never agree to grant my permission when first loading a page, however, I may do so if intentionally activating a map widget. At least then I understand the context by which it's being asked, and can make a more informed decision.

Well, because it means that other energy generation sources like oil, gas, and coal aren't being used there instead. Since they cause far, far more harm than nuclear waste does, it's a net win.

The same is true for solar and wind energy but without nuclear water. She cause far less harm than nuclear waste, even bigger win.

Our main problem isn’t energy production it‘s storage and quick reaction to consumption spikes. Nuclear energy doesn’t help with that.

Note that a checkbox's indeterminate state can only be set via JavaScript, so that lessens the elegance of a CSS-based approach.

I agree that using radios would be better. Or just prefers-color-scheme, which sidesteps the FOUT issue that often occurs when storing theme settings in localStorage.

Not having looked at the extension, I would assume they use the chrome.scripting API in MV3.

https://developer.chrome.com/docs/extensions/reference/api/s...

https://developer.chrome.com/blog/crx-scripting-api

No, this can't be used for remote code. Only existing local code.

Thanks for clarifying. It looks like I needed to refresh my memory of the browser APIs.

Reading further, this API only works remotely for CSS via chrome.scripting.insertCSS. For JS, however, the chrome.scripting.executeScript JS needs to be packaged locally with the extension, as you said.

It seems the advanced method is to use chrome.userScripts, which allows for arbitrary script injection, but requires the user be in Dev Mode and have an extra flag enabled for permission. This API enables extensions like TamperMonkey.

Since the Claude extension doesn't seem to require this extra permission flag, I'm curious what method they're using in this case. Browser extensions are de facto visible-source, so it should be possible to figure out with a little review.

> "probably should’ve added a disclaimer"

It's a violation of the Amazon Associates program to not have one.

Also, it's illegal in the US and many other countries to not disclose that you're earning money from a recommendation.[0]

[0] https://www.ftc.gov/business-guidance/resources/ftcs-endorse...