planede

Maybe the problem is that it is "lib"systemd, meaning it doesn't really have control over when the process forks, it's the application code's responsibility. Although I would probably also avoid this design, but that would probably make the library interface a bit unfriendly, with the application needing to pass its own pid to library functions where appropriate.

The question is how much unrestricted donations would the Linux Foundation get if they offered directed donations as well. They might not get enough unrestricted funds to pull this.

It might also not look good on them if they used the unrestricted donations in a very unbalanced way to counter restricted donations the way you describe, so they might get less unrestricted donations in the future.

As an individual where do I click and say donate $20 towards the development efforts of the Linux kernel?

It looks like one can donate towards the LF as a whole [1], but the LF manages a ton of other projects besides Linux. So if was possible to restrict small donations towards the development of the Linux kernel, that would be great.

[1] https://www.linuxfoundation.org/about/donate

The distinction is between using APIs (documented or undocumented) vs using and distributing 3rd party libraries and SDKs.

It's likely that in order to avoid distributing Apple IP one would need to reverse engineer some undocumented APIs, but that's coincidental.

Sure enough, it is Arial.

https://imgur.com/a/WAdo55M

I might play with imageworsener to see if I can figure out the exact downscaling method.

edit: ah, you beat me to it. I just played with Inkscape and word spacing to match that line. The scanned document looks very lightly slanted, but I don't think it matters too much.

I wonder if the redacted versions are available in higher resolution.

I think the downscaled version could potentially be deciphered if the exact font is identified.

Using APIs is fair use. If you can avoid using Apple code to do so, or only minimal ones, like headers, then I think you would be in the clear. See Google vs Oracle. IANAL of course and personally I wouldn't pursue this.

It sounds closer when it's sped up.

Hang on there, array of strings? Environment variables can't handle that either without quirks.

How does it compare to dhall?

Do yourself a favor and get a silicone replacement gasket instead of the Bialetti one.

It was basically the same idea as WSL1, i.e. running the Linux kernel (or equivalent) in Windows userspace.

It actually worked decently when I tried it back then.

Even if the set is infinite, there surely is a smallest non-negative interesting integer.

I read this as "there were a lot of buggy implementations of the C standard, so we imported the bug into the standard". Crazy. Don't make the language less defined going forward.

When those implementations eventually pick up C23, they surely could fix the bug as well. At best this should have been an errata/defect for the previous standard, so that the previous standards document behavior of implementations of said standards.

You can't fully disable fast-math per-library, moreover a library compiled with fast-math might also introduce inaccuracies in a seemingly unrelated library or application code in the same executable. The reason is that fast-math enables some dynamic initialization of the library that changes the floating point environment in some ways.

Another PSA is that dynamic libraries compiled with fast-math will also introduce inaccuracies in unrelated libraries in the same executable, as they introduce dynamic initialization that globally changes the floating point environment.

On a somewhat similar note, don't use std::lerp if you don't need its strong guarantees around rounding (monotonicity among other things).

https://godbolt.org/z/hzrG3s6T4

The thing to be checked are the installed GPG keys that are trusted for package signing.

While I'm not familiar with the black market, I refuse to believe that an arbitrarily modified pytorch binary release has zero value.

The catch seems to be delivering only 100 microwatts. Very far from powering a phone.

Fortunately these kind of accidents never happen, so nothing to see here. /s

This is going to be possible with CRIU and Wayland applications. I saw a PoC with Qt that did this.

You are better off with CRIU at this point, IMO.

Couldn't the parliament pass some generic law that could make the work easier? It's clear that many people are convicted on the basis of evidence coming from the same faulty source, yet the convictions need to be reviewed case-by-case. The goal could be to reduce this friction for similar scenarios, not just for the Horizon convictions.

Are court documents routinely analyzed by computer forensic experts, or only when there is suspicion of tampering?

PDF being Turing complete doesn't mean that the program embedded within can access the bytes of the document.

> the real document won't have hash colliding artifacts in it

I don't think that hash colliding artifacts would necessarily be obvious. They could be in part of a file that ends up being ignored by parsers of the file format. Or it could be some low level noise in pixel values in scanned documents.

> That's inevitable in my opinion, because this modular interface has been used for a very long time.

I wonder how widely it's actually used and if making this an exposed modular interface was worth it.

I think the main mistake here is that it was made to be a public interface instead of an internal implementation detail. Now you can expect that some people are relying on custom specs. Migration to a saner configuration language is still possible, but it probably needs to be done with deprecating and phasing out the old DSL concurrently to introducing a new language. Bonus points for providing a tool for converting old specs to the new language.

Correlating with water and electricity bills could raise suspicion, but yeah, it's probably harder.