• 2 Posts
  • 41 Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle

  • Lol Whatsapp as a system app sounds like a nightmare.

    The usuall approach established by Samsung etc. is to bundle a few “shim” apps as system apps for Meta. One shim is used by the regular Meta apps to bypass restrictions and talk to each other, one collects data from any app that uses the Meta ad network, and some are there in case you install the corresponding user app (eg. Facebook) to give it system privileges.

    I mean it ends up technically the same as having Whatsapp bundled outright, but you gotta give props to a manufacturer so shamelss they don’t even pretend to hide it. 😃


  • The problem is that making games (and software in general) has become more high-level, and enshittification has also gotten rid of highly skilled people. So the top studios in the industry are not capable of making resource-efficient, beautiful games anymore. Not because it’s physically impossible, but because they’re not geared for the processes and decision-making that would allow those games to be made.

    When you switch from an artisan mindset to a mass-manufacturing and outsourcing mindset without exercising strict control you eventually become utterly dependent on service and product providers that will see to your costs going up so you’ll keep paying more for less.

    All the large studios will come to a breaking point eventually because it’s unsustainable, and will be acquired for the franchise rights by corporations that make their money in unrelated industries. But the PC platform is also breaking down so this might be a moot issue in 10 years from now.








  • Please note that to use “bcrypt” for htpasswd_encryption you need the bcrypt python module installed. Some distributions of radicale (eg. some docker images) don’t have it.

    It’s fairly safe to set it to “md5” instead. It does not mean plain MD5 (one iteration), it does several hundred rounds of MD5 plus a salt.

    For the curious, the advantage of bcrypt over a single-iteration, fast hash like MD5 is that bcrypt lets you set the hashing effort, while MD5’s goal is to do it as fast as possible.

    This becomes relevant when someone steals your password file and tries to brute force it by hashing a bunch of dictionary words and random strings (plus a bunch of salts) until something matches. A fast single-iteration hash like MD5 will let them do that much faster than a bcrypt hash set to a higher effort; it can mean the difference between finding a password in one week vs finding one in 100 years. That’s what the hundreds-of-iterations MD5 is trying to achieve, it’s a “poor man’s bcrypt”.







  • Here’s the AUR recipe (PKGBUILD file) for a random package:

    https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=nautilus-git

    This is a standard format for the recipe. It’s Bash code used to define variables and functions.

    You’ll notice there’s no place to sneak in a Python script. There is some brief Bash code in the functions but any major stuff would stand out immediately. So would an command that fetches a malware zip from a weird URL.

    Meanwhile, if you add node or python to the dependencies, and then run a command that installs a perfectly legit npm or pip module, nobody would bat an eye. It’s impossible to figure out that among the many upstream dependencies of that module there might be one that was subverted to discreetly run malware.

    AUR is a very bad idea tbh and should not be used by the faint of heart. It makes it entirely too easy to pull this kind of crap.


  • Add mTLS to the reverse proxy and to the Immich client app and forbid access without it.

    The mTLS certs can be self-generated. There are tutorials for generating your own CA and individual mTLS certs for each device. Then you put the ca.pem file in a place accessable by NPM and add a couple of commands to the “Advanced” tab of the Immich proxy host, and you put the mTLS cert on the phone and load it into the Immich app.

    mTLS is a super strong method, not only does it serve as great authentication for that particular device, it also checks the TLS connection for tampering so it can’t be hijacked even if somehow you get rogue certificates loaded on your phone, you can revoke certs if your phone gets lost or stolen etc.




  • InfCloud is the last and only functional, standalone, web-based CalDAV frontend currently in existence. It doesn’t really matter how crap it is because there’s no alternative. And besides CalDAV/CardDAV are not exactly rapidly-evolving anymore.

    There are a handful of alternative frontends bundled with other webapps, for example Nextcloud includes one, but if you don’t want to install Nextcloud just for that you’re stuck with InfCloud.

    I really wish someone would make a modern standalone webapp for this but no luck so far.

    Having worked at some point on some calendar interfaces I can appreciate why, because they’re super intricate and difficult.