9029

It was serving static html https://news.ycombinator.com/item?id=50224916#50234806

Not to be confused with CrowdStrike, a serious [0] security company

[0] https://en.wikipedia.org/wiki/2024_CrowdStrike-related_IT_ou...

Another post suspects Nvidia drivers: https://davidjusto.com/articles/m2p-latency/#results

You can replace it with a generic one to hopefully blend in https://madaidans-insecurities.github.io/guides/linux-harden...

Related: "How I made a 60fps Eink Monitor" https://www.youtube.com/watch?v=nHbA2-_qzH4

I'd recommend reading the post, it's not that long

Is it possible to reason or prove the correctness of an LLM?

Not gp but I really like the sound of my GK Kuntens and 7Hz Zero2s. Both have a rather V-shaped sound signature, some like it and some don't. Though unfortunately the Zero2s feel a bit uncomfortable in my ears when using them for longer

I'd guess the speed improvement in those cases likely came from learning a better technique, like touch typing and using more of your fingers. Afaik a lot, if not most, of the fastest typists are still on qwerty.

That "officially supported" comes with a huge asterisk though. Security bulletins for old android versions already only include backports of high severity patches. On top of that the device also gets no security patches for firmware or kernel, as the hardware and kernel are eol. The FP5 is also on an eol kernel after less than 3 years, not that they were providing kernel updates in the first place. https://discuss.grapheneos.org/d/24134-devices-lacking-stand...

I thought it worked just fine on LTSC 2021 (21H2)

I think it could be interesting to explore Universal Blue based distros such as Bazzite for this kind of use cases. The OS comes from a standard OCI container image, which means you can create your own customized one by layering changes on top of an upstream base image.

I feel bad for the unsolicited distro plug though especially since you already have a solution that works well and you are familiar with, but I thought it might still be useful to mention it. I'm not sure if uBlue would even be better vs your current setup. Seems like netboot would still be needed to get the latest version without an extra reboot.

It seems this vuln was already publicized in june, or is that interview from earlier?

> For a lot stuff on my local network I don’t want the hassle and there are loads of use cases in local networks for normal people to just have port 80 no certs on something like 192.x.x.x because there is no easy way to set up public certificates for that and I don’t want everything hostem on cloud - some stuff I want to still host for myself in my local network.

Tbh I don't see what's hard about this. All you need is an A record pointing to your 192.x.x.x, acme capable dns host and a modern reverse proxy. You can even use a free ddns service if you want. Wouldn't bother with this for development, but anything hosted for longer than a few days absolutely yes. Imo not getting browser warnings is alone worth the few minutes it takes nowadays.

> But also, rewriting history only works if you haven't pushed code and are working as a solo developer.

Weird, works fine in our team. Force with lease allows me to push again and the most common type of branch is per-dev and short lived.

I like that Zig allows using relaxed floating point rules with per block granularity to reduce the risk of breaking something else where IEEE compliance does matter. I think OpenMP simd pragmas can be used similarly for C/C++, but that's non-standard.

C++ lambdas can be used to achieve a similar result, not as pretty though https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines... But in general I agree!

Tangential but funnily enough calling std::expected::error is ub if there is no error :D

This is exactly where Bazzite is convenient since it comes with the latest drivers (including 32-bit) out of the box.

I have used this setup for 6 years or so with KeePassXC and it's fine. Just being mindful of not editing stuff on other devices before the first one has had the chance to sync has been enough to avoid pretty much all sync conflicts. I have only had to resolve those a few times so far, iirc my android client was misconfigured at the time or something.

I still recommend Bitwarden for password management for any "laypeople" since it will just work. Also worth noting that the basic functionality is free.

Seeing such pivotal announcement be poorly vetted slop doesn't really inspire confidence in the quality of their product.

Do you have an opinion on the keyboard firmware ZMK? They seem to use LESC but MITM during pairing is still a concern: https://zmk.dev/docs/features/bluetooth

While we are at it, here are some more useful warning flags I have used: https://github.com/cpp-best-practices/cppbestpractices/blob/.... Some C++-only though, some are a bit opinionated (like -Wsign-conversion) and some useful C-only flags might be missing.

Few C-specific references I found just now, but haven't tried myself yet:

https://github.com/systemd/systemd/blob/0885e4a6e7ca93d3aef8... https://github.com/airbus-seclab/c-compiler-security

Also a good idea to regularly run the program with sanitizers, using them in tests is a good way to do that I think. Why not during development as well if the performance is acceptable for that specific program.

It has now been changed to

  if (rtt < 0.0)
  {
      fprintf(stderr, "Warning: Negative RTT detected (%.3f ms) - clock issue?\n", rtt);
      rtt = 0.0;
  }

https://github.com/davidesantangelo/fastrace/blob/e8b19407a4...

Is this vibe coded or is it just the readme that's AI-generated?

> a parser may reject the document entirely if it occurs

Ah, that's what I was missing. Thanks! The relevant part of the spec:

> user agents, while parsing an HTML document, may abort the parser at the first parse error that they encounter for which they do not wish to apply the rules described in this specification.

(https://html.spec.whatwg.org/multipage/parsing.html#parse-er...)

Maybe a dumb question but I have always wondered, why does the (authoring?) spec not consider e.g. "doctypehtml" as valid HTML if compliant parsers have to support it anyway? Why allow this situation where non-compliant HTML is guaranteed to work anyway on a compliant parser?

> I am curious what their editing process was

They said:

> I typed in the new code as that's faster than modifying the existing code

Update on power draw for anyone interested: measured with a cheap AC power meter, I get 2.8-4.2W idle with occasional jump to up to 8W on my M720q with i5-8400T, 16GB ram and a single nvme drive. This is on Debian 13 with ASPM enabled for everything and a few containers running (home assistant, esphome, bookstack, tailscale). According to powertop stats on C-states, it's mostly in package C9 and core C10.

Used Intel 8th gen based mini PCs seem like a pretty good value. 100-150 bucks for a pc from a somewhat reputable brand (lenovo, dell, hp) with slightly better multi core than N150 and ~6W idle if you manage to get it to stay in C10. Some of them have a low profile pcie slot, like M720q and M920q. Also the CPU is socketed so you could technically upgrade it to e.g. i9-9900K, at least the M920q is known to take one as long as you use a powerful enough PSU. Few of them (at least M920q) also support coreboot due to an Intel Boot Guard vuln which could be fun, I'm planning to look into whether it could be ported to my M720q as well.