I use Quad9 where I can, but admittedly also have some reliability issues. Their local PoP will drop all requests for a couple minutes at least a few times a week. It’s a shame since it’s the closest/best recursive resolver otherwise. CloudFlare is similarly close, but they don’t support EDNS, so I’ve had problems because of that.

The vast majority of these 3d printed guns use the fact that the registered “gun” is only a small part of the actual whole gun. You can buy barrels, magazines, slides, firing pins, etc, all mail order without any fuss — it’s the part with the serial number that is actually the firearm and restricted. So if you print that part (which is often basically just a shell to hold the metal components in place) you have an unserialized gun that’s basically just as good as one from a gun store.

Bro even Macy’s sells these things in store. They’re a mass market product.

Cap LLMs to 1 Trillion parameters, can utilize no more than 384GiB of (V)RAM.

Offenders go to jail (corporations charged as a criminal enterprise), all equipment seized and destroyed.

If these AI glazers really believed that AI is the threat they claim it is, then we should treat it the way we’d treat corporations if they tried developing their own nuclear weapons.

Probably in anticipation of some serious price increases. They’d still like to get devices in people’s hands even if they can’t nominally afford them anymore.

Also worth noting that since this includes coastline, it means basically 2/3 of Americans are deprived constitutional rights.

https://en.wikipedia.org/wiki/Border_search_exception#/map/0

Where’s the pressure? Who’s making these files and trying to use them?

The standards bodies and the companies that pay their bills. That’s Netflix, Google, et al. All have a vested interest in good multimedia support in browsers. It’s why browsers have shockingly good support actually, most of the problems are downstream on clients and implementations that don’t know or care to enable these newer formats.

What am I supposed to do?

You decide what to target, and work with what you have. That’s how it’s always been with web technology.

If you need to support the barest minimal possible clients then you might not even have HTML5. Otherwise, if you have HTML5 you can use the source tag to provide clients with a choice of formats/encodings and they can pick the one they support. If the clients can’t even mange that, well, things on the internet have always been broken anyway.

And somebody’s gotta start somewhere, WebP was shoved down everyones’ throats and now it’s supported very broadly, as AVIF pick up users software devs will take notice and start supporting it.

Using a browser or third party app?

I think that’s a reasonable way to look at it.

It’s not the route I’d take, after all, the video tag in html supports specifying multiple sources (including different formats/encodings), and with full control of the stack (they vend Safari) you could have logic on devices without AV1 hardware that prefers the AVC/HEVC/VP9 sources instead — then fallback to AV1 SW if it’s the only option. That seems a better user experience than just failing to display content.

Very interesting, thank you!

I checked that app’s source code, and basically they’re doing their own avif decode call instead of relying on a browser/webview to handle it. So essentially they forgot/don’t know/don’t intend to implement animated avif. Looks like they also use the aom reference decoder instead of using something faster like dav1d.

That’s caused by bad regex in the app, it’s getting confused about domains.

e: attempted fix by using an aliased domain.

It’s an intentional behavior by Apple. Basically they just don’t support AV1 videostreams unless the hardware you’re using has a hardware decoder. They could support it using software decode (what browsers typically do for AV1 inside avif containers) but… for whatever reasons don’t.

Apple has limited support for AV1 streams (yes, even for software decode) unless on very recent hardware. Here’s an AV1 stream inside a webm container for comparison, would be interesting to see if that works over the avif container on your stack.

Can just use avif instead, it holds an AV1 stream and acts like gifs/images do WRT looping — also very broad support (more than AV1 in WebM containers).

Demonstration:

Edit: switched to an example with simpler decode requirements.

They do disclose it, it’s part of the paperwork when you purchase the vehicle.

https://support.toyota.com/s/article/Toyota-Insurance?language=en_US

Of course the dealers make it very easy to “opt-in” by accident.

The fact that it’s out in the open, literally on the car manufacturer sites, but people still deny this behavior, is a grim omen.

They sell driving habits and other informatics to insurance companies at the very least, this is publicly known.

Hiding? Modern vehicles straight up have cell modems and advertise it, look up Toyota Connected Services for example.

Yeah, just gimme the NP6 terminal, I’ll figure it out.