I don't see where your problem comes from. It's really simple: they wanted to target Mac, likely because that's their preferred platform. So obviously they use the best fitting APIs for that purpose. Why would they develop a Linux or Windows application, if what they want is Mac? Nothing suspicious about that.
Mostly a nitpick, but for that little helper I would have stuck to the stdlib and not pulled in a dependency like echo.
Otherwise: nice idea. I did something similar but since caddy runs directly on my host, I added permissions for the other services that need the cert and then pointed them directly at it.
If the AppleTV allowed side loading, it would be my dream device. The UX and the speed of Apple devices are just so damn pleasing. But the artificial limits they impose on what you can run on them is damn frustrating.
Being whistleblower and being involved in such legal proceedings sucks and I can imagine that one might give up (like Barnett in March) or that it takes a huge toll on your body (like Dean now). But then again ... two such incidents around the same company ... reminds me a bit too much of russian windows.
Lookup if the device is supported by LocalTuya though.
I made the mistake thinking that LocalTuya somehow acts like a proxy for a generic protocol, but it actually needs to understand the devices. Now I have a doorbell I can't use with it.
Nah, explicit sync is the objectively better model if you want high performance. Android went for explicit sync right from the start and from what I gather also Intel and AMD prefer it. The problem is, that the graphics stacks on Linux have been using implicit sync for ages and so far no one dared to change the status quo. Nvidia was "simply" rejecting implementing an inferior mechanism in their driver. While somewhat understandable, it was still a decision on the back of their users.
I am not a big fan of this, because you then rely on the scanner manufacturer to produce good quality results.
I scan everything using VueScan and that has a special mode for text documents. A single page with OCR ends up being about 25kb as PDF. It removes folding edges, sharpens the letters, etc.
If that software gets new features, my scanning experience improves automatically, even though I still use the same scanner for 10 years now.
With relying on the firmware, I would have long ago stopped getting updates and I either was ok with the results or I could throw away the whole device.
Just as people here recomment to separate printing from scanning, I recomment to separate the hardware and software.
The bigger issue (IMO) is, that you now have a hard requirement on the startup order of your services. If another one happens to get the IP assigned automatically befor your service starts that requests it explicitly, you now have a conflict that you manually have to resolve.
Do you think being maintainer makes you some kind of all knowing being? That's not how that works. You write code and review code of others.
If there are multiple maintainers, you may obviously not even notice what another maintainer is doing; then you wouldn't need multiple maintainers with write access if you could handle it all by yourself.
But everyone does keep their license. A company can not really take over in the sense that you lose your old code. They can stop developing in public but keep using your code, but so can you keep using the last public version and keep developing it. Or you can take your contribution and apply it elsewhere.
There is actually a mechanism that allows distros to register the system level driver as flatpak extension, so the driver is available in the sandbox. Unfortunately, almost no distro uses that :-/
If one could "just hyperfocus" on something, AD(H)S would be a weapon, not a disorder.