Can it detect when it itself is down

No, you will need another layer of down detector.

That'll be HN indeed.

normalizing flow might be unpopular but definitely not a forgotten technique

Note that it's very likely that Veo models are based on "Flow Matching" [1]

[1] https://arxiv.org/abs/2210.02747

I just pre-ordered a Bigme 13-inch color e-ink monitor with a 30Hz refresh rate. At $499, it's much cheaper than the Dasung, though the quality and e-ink display algorithms might not be as good

I've been using a BOOX Tab Ultra C Pro (with the Kaleido 3 color e-ink) for a year. The colors are quite dim, to the point where I sometimes forget it's a color e-ink display. The Colorsoft display looks significantly better in comparison (even seems to have better contrast than ClearInk?), so I'm curious how it works.

Slightly off-topic: Is there a library in JAX that supports post-training quantization, similar to the one mentioned?

https://developers.googleblog.com/en/tensorflow-lite-is-now-... tries.

https://github.com/google/aqt is more explicit and preferable IMO.

Neither are as user-friendly as what Torchao has presented here.

The post was moderated within 10 minutes of being submitted: https://news.social-protocols.org/stats?id=40710417

Those were user flags. (I just checked. A mod didn't do anything until 38 minutes later.)

pure css without background-image also works: https://css-shape.com/film-strip/

Seems that pasteurization cannot completely inactivate H5N1

> In addition to the mice studies, the researchers also tested to determine which temperatures and time intervals inactivate H5N1 virus in raw milk from dairy cows. Four milk samples with confirmed high H5N1 levels were tested at 63 degrees Celsius (145.4 degrees Fahrenheit) for 5, 10, 20 and 30 minutes, or at 72 degrees Celsius (161.6 degrees Fahrenheit) for 5, 10, 15, 20 and/or 30 seconds. Each of the time intervals at 63℃ successfully killed the virus. At 72℃, virus levels were diminished but not completely inactivated after 15 and 20 seconds

`import jax.numpy as np`, then we also get a jax implemention after certain modifications: e.g. remove in-place index assignment, replace unsupported functions, etc

JAX requires a bit more work to maintain fixed-size buffers as required by XLA, especially in case of caching and rotary embeddings. But yeah, overall the code can be pretty similar [1].

[1]: https://github.com/dfdx/fabrique/blob/main/fabrique/llama/mo...

...which should be much faster also on CPU, I assume.