Koffiepoeder

Interesting, this is the first time I've come across using a FFT for collision detection, and now that I think about it it really makes sense. Thanks for the insight!

Can confirm, one example: the company that I am currently working for put all its plans for investing in the US in the fridge and is exploring other markets now.

If I can get in once, I can do it again an hour later. I'd be inclined to believe that dumb recycling is not very effective against a persistent attacker.

I now present you: HDRbooster. The tool to boost your image to 19.99% BOOSTED highlights and 80.01% MAX brightness (99.99% of SDR white)!

Mhm, this is one of these cases I'd prefer a benchmark to be sure. Checking %2 is very performant and actually just a single bit check. I can also imagine some cpu's having a special code path for %3. In practice I would not be surprised that the double operand is actually faster than the %6. I am mobile at this moment, so not able to verify.

What I really don't like about thread/matter is that it is becoming the de-facto standard that thread border routers are connected to the internet.

This will in time result in IoT devices that actually mandate this connection (it was already stipulated in a recent version of the protocol). The end result will be that a new protocol was created, but rather than devices being able to run on their own, we end up with beds in heating mode, ie. the garbage we were trying to avoid in the first place.

So for me, zigbee it is!

It would be interesting to see a JDK happen where all these backwards compatibility quirks are ignored, and raw performance is chased instead. A thousand of these little gains can really add up over decades. In this case there was a workaround it seems, but it feels a bit contrived to me ('missing fields are ok'?).

The moment you put TOTP in Bitwarden it is no longer a 'second factor'. Pretty bad security advice to be honest. Better to use hardware tokens or a secure phone (with enclave) instead (never SMS though).

I'm not the OP, but for me their comment sparked an association to the famous Ken Thompson lecture called 'Trusting Trust'. Could be a good starting point.

Can you share the diagram? Would love to become iptables-enlightened.

If you want lots of differently styled templates, template management and editing/styling capabilites in word or excel (ie. you can just ask your customer/employer/.. to make an example document), I can really recommend Carbone [0]. I've been a happy customer for a few years now. Extra advantage is also that it also offers you excel outout generation as well, which is also often a requirement in applications. They have a SaaS offering as well if you'd like. They are open source though, so you can easily run a docker container!

[0]: https://carbone.io/

Saying the internet is not a place for children is like saying the street is not for children. Full of drug dealers, cars and danger!

Yet learning how to cross the street is an essential skill in life. They are also filled with flowers, pathways to playgrounds and much more. And that's why children are not forbidden on the streets.

My point being: let's educate instead of regulate. "Regulating the children" is silly and countereffective.

I genuinely take the effort to write em dashes quite often, certainly in formal documents or publications. So for me that's not a tell-tale sign of AI usage. Your analysis of the pacing of the article on the other hand — spot on.

If you look at their lab [0], it seems his NAS is separate from his kubernetes nodes. If he hasn't tuned his networking and NAS to the maximum, network storage may in fact add a LOT of delay on IOPS. Could be the difference between fractions of a millisecond vs actual milliseconds. If your DB load is mostly random reads this can really harm performance. Just hypothesizing here though, since it is not clear whether his DB storage is actually done on the NAS.

[0]: https://dizzy.zone/2025/03/10/State-of-my-Homelab-2025/

Wouldn't recommend applying this _everywhere_; the `body *` selector may have a significant performance impact on some pages.

If you use HDR 4k or even 5k screens and are looking for a decent framerate, the maximum cable length is quite short (on the order of 3m for an UHBR10 DP40).

There exist solutions for that with active cables or optical cables, but that quickly gets expensive and complicated.

Yes, the article is indeed a simplification. Google fonts also checks for font format (eg woff2, ttf, otf...) compatibility based on user agent and changes the files served depending on your browser.

Or your server can cache the compressed content (since it is a static page anyway).

Reminds me of Zeno's paradox. Do you have a terminating condition? Or just a fixed number of iterations?

To websites that talk about declining quality and then return a 403 for tor users: sweep your own front door first please! I have the luck to be able to circumvent via a residential IP, but users from oppressive regimes may be less fortunate.

One of the lucky 10000 on this one I guess. Thanks!

It can be hard during live performances, because it can incur large jumps in the sheet music which can be annoying to follow. Not a problem if you learned the pieces by heart or have a pageturner, but this is not always feasible or the case.

I know many, though most of them are either founders, business owners or farmers. FWIW, only one person in that list is an employee.

Well, like everything it's probably a balance to strike. Otherwise you may end up with highly golfed IOCCC-style code in production, which I would definitely not recommend.

It seems so strange to me that it is this hard to add: I wrote a userscript recently to extract titles from slides and if I recall Google slides already renders in an svg format. Wondering what's going on here.

I have the impression this is still using api.d2lang.com/render/svg as the primary source for its renders. So to me it seems that - although wasm is being loaded/used - this is maybe more for client-side processing steps, rather than the full rendering being done in wasm.

It may constitute an infringement on common law trademark rules [0], but not sure what the German legislation around that is.

[0]: https://en.wikipedia.org/wiki/Unregistered_trademark

They were working on a wasm version some time ago I believe [0]. Not sure how usable this is insofar, but it may be of interest.

[0]: https://github.com/terrastruct/d2/pull/436/files

Have a feeling this will lead to XSS vulnerabilities though.

Ip's can (easily) be hijacked by nefarious BGP requests and offer no easy SSL. You could maybe add cert pinning to fix that, but it's quite inflexible.

Another added bonus of domains is the potential for subdomains to be used. This could be usful for many purposes: as load balancing/pooling mechanism (fictive example us4.zoom.us) and for compartmentalisation (api.zoom.us).