• 0 Posts
  • 53 Comments
Joined 1 month ago
cake
Cake day: June 16th, 2025

help-circle




  • When people complain about software being monetized and closed instead of everything being FOSS and I say people want to put food on their tables… This is exactly why. Most of the projects that have a good deal of recurring donations are some form of productivity software. Companies or freelancers use them to make money on a daily basis and decide to give back a bit, to ensure that their software continues being developed (large corporate donors sometimes also get a say in what features are prioritized).

    Nobody sets up a recurring donation for a neat bit of software that makes life easier, but isn’t making the user any money.

    It’s GPL, just like the Fediverse prefers it. Single most recommended launcher in the Linux gaming community in recent years. And the owner makes €100 a month off it. AND there are people in this very thread saying people shouldn’t donate to it because you could instead fund Wine development by buying a Crossover license (yay, proprietary software). Then another unrelated comment pointing out you can donate directly to Wine too. Then another comment saying they don’t like how FOSS projects often don’t disclose where the money’s going.

    Well guess what, open source devs want money so they’d no longer be dependent on their soul-sucking corporate day jobs and have more time to develop neat open source software. Open source devs are often overworked and some receive a lot of abuse for not spending more time on their open source projects. Orchestrated abuse for not spending enough time on his open source project is how the author of xz was pressured to give maintainer status to what turned out to be a nation state level actor trying to integrate a backdoor into everyone’s Linux systems.

    The open source community is abusive towards open source maintainers, really. I’m honestly glad I only have some small contributions to my name, and no large projects to maintain.

    To be clear: No, I’m not any better when it comes to donations. I’m more likely to pay for proprietary software than to donate to an open source project I use. Same goes for most people I reckon. That’s why, while open source is awesome, actually being an open source dev sucks.



  • I liked YouTrack. Only used it as a dev, not a manager or tech support though. But from what I saw, everyone seemed at least OK with it and some people were downright happy to use it.

    It’s free for up to 10 users and available as a docker image, in case you want to try it out before committing, or pitching it to higher-ups. Cloud version is available too of course.

    They are raising prices in October though. Not sure how it’ll compare to Jira or how it does now, I’ve never had to pay for either myself.


  • Yes. They (cellebrite) don’t mention GrapheneOS support very loudly because it’s poor. They can’t decrypt one that’s BFU (Before First Unlock), not even by brute force if it’s a 6 digit passcode apparently. Don’t know if they can get data from an AFU GOS pixel. A year ago when their internal docs leaked, they also had no support for latest iOS at the time, but had brute force support for older versions as long as phone itself wasn’t too new and had AFU access without brute force for even older versions.

    Moral of the story: if there’s a chance police might take your phone to investigate for a crime you hopefully didn’t even commit, shut down your phone completely - the 5x power button trick on iOS disables biometric unlock, but the device itself stays decrypted and thus more vulnerable. Also keep your OS up to date.

    If you’ve got a phone that’s neither iOS nor GrapheneOS, it’s probably pretty much Swiss cheese anyway. IOS isn’t as good as GrapheneOS either, but it offers some protection against Cellebrite if up to date and BFU. But if they keep your phone for long enough (months, years), they’ll get it unlocked because you can’t install updates that would patch any newly discovered vulnerabilities and one day they’ll find a BFU unlock for it, probably.











  • Java 8 to 21 + spring boot 2 to 3 brought the need to change a lot of dependencies, but often they were drop-in replacements. That was mostly Jakarta stuff. On the Spring side, a lot of things we used were deprecated, but that was not related to the Java version.

    Did not take a huge amount of time to upgrade anyway. But maybe our systems weren’t the most complex in the first place, a lot of our applications were pretty small.