Unfortunately, it's realty hard. The US giants have offerings that no one in EU has and I am investing huge amounts of time into working around them (e.g. Windows and MacOS CI runners on Github - try to get this for free in EU). I'm fine with paying a bit for this, but even then it's a huge hassle to set it up to be able to get CI checks for my projects on Windows/MacOS. And it's not cheap either. I can afford it, but it is still very expensive.

The only thing I can imagine is the story would get spoiled on the internet, but that's about it.

KDE's Plasma will popup a notification every once in a while asking for donation. When you close it, you won't hear from it again until the next fundraiser. I almost always donate as well.

If a software asks in a non-obtrusive way, ideally after I used it (either for a while or like in case of Jellyfin2Samsung after doing the one thing it's supposed to do), I don't mind at all.

I dislike apps (mostly websites) that keep asking for money, regardless of whether you already donated or not every single time you visit them.

[0] https://www.dvratil.cz/2015/12/git-trick-%23628-automaticall...

The main lesson we took from this was: you absolutely need monitoring for cert expiration, with alert when (valid_to - now) becomes less than typical refresh window.

It's easy to forget this, especially when it's not strictly part of your app, but essential nonetheless.

I always thought about metal shows and festivals as a "safe space", where people can really be themselves, because you don't have to suffer judgmental remarks about what you wear, what you look like or what you listen to. And most people there get this and feel this as well, which is why the community feels so welcoming and chill. Plus as someone else posted here, it's also all a bit silly and I think most people get that as well.

In real world, the futurelock could occur even with very short locks, it just wouldn't be so deterministic. Having a minimal reproducer that you have to run a thousand times and it will maybe futurelock doesn't really make for a good example :)

I was also a huge fan of BlackBerry phones (having used Q5 and Z10 as daily drivers). The system was solid and had some really cool ideas. Too bad it didn't work out...

Even Claude Code lets you approve each change, but it's already writing code according to a plan that you reviewed and approved.

With Rust I have one job that runs tests and another that runs cargo build --release and I'm done...

I have an older car with an old stereo where the only external input is via jack. Worked perfectly fine with my old phone. When I got a new Samsung, I went through the hassle of trying several "combined usb-c charger and audio jack adaptor" only to eventually find out they can only work in on mode or the other, not both at the same time. I ended up throwing away my old phone holder and spending even more money on one with built-in wireless charging so I could both listen to a damn music and charge my phone at the same time while driving.

Then you top it on with `?` shortcut and the functional interface of Result and suddenly error handling becomes fun and easy to deal with, rather than just "return false" with a "TODO: figure out error handling".

As mentioned in the article, pi-hole complements a browser ad block, doesn't replace it.