chameleon @ chameleon @fedia.io

i'm lizard

---

Read more

Posts

0

Comments

100

Joined

1 yr. ago

Steam for Linux is mixed 32/64, unfortunately the main executable (~/.local/share/Steam/ubuntu12_32/steam) and its associated steamclient library continues to be 32-bit only and runs with a couple of horribly dated libraries in the mix. That process does pretty much everything aside from the UI.

There's a disclaimer in the readme: https://github.com/juanfont/headscale/?tab=readme-ov-file#disclaimer

The maintainer Tailscale contributes happens to be the lead developer by commit count at the moment.

They also had a major ass security issue that a security company should not be able to get away with the other day: assuming everyone with access to an email domain trusts each other unless it's a known-to-them freemail address. And it was by design "to reduce friction".

I don't think a security company where an intentional decision like that can pass through design, development and review can make security products that are fit for purpose. This extends to their published client tooling as used by Headscale, and to some extent the Headscale maintainer hours contributed by Tailscale (which are significant and probably also the first thing to go if the company falls down the usual IPO enshittification).

I haven't seen proper reporting but the Play Integrity install source thing is accurate. There's a reasonably good overview straight from the devil himself.

Lots of things that have very valid reasons on paper that also just happen to give Google a stupid amount of control and will backfire for a somewhat small percentage of people in very bad ways. We've been at "you can't use pretty much any bank unless you agree to either Google or Apple terms" for quite some years now, now we're giving those same app developers ways to detect if their device has accessibility APIs enabled (useful to protect against bot farms, but also a functional check for "you're able-bodied") or is in security support (also a functional check for "not reliant on hand-me-downs").

Not them but between those two I'd recommend Kanboard if you're going to be the only user. Far lighter and easier to administer piece of kit, has everything you'd want from a fancy task list but not much more. WeKan is rather heavy software but does have a few features that are probably quite important for large team use.

Started Digimon World Next Order on a whim after it was on a big sale last week. Not sure I can recommend it, and definitively not at full price, but it's interesting to have a game that doesn't know if it wants to be a modern game or a 2000 era throwback game in exactly the right ways. And well, it's still about little critters that turn into big critters (and back), so I'm satisfied nonetheless.

PUID is indeed handled inside the container itself, it'll run a container-provided script as whatever the container's UID 0 happens to be first which then drops to whatever $PUID happens to be inside the container. user= is enforced by Podman itself before the container starts, but Podman will still run as root in that setup. That means Podman is running "rootful", while if you started the container manually as $uid using the regular Podman CLI, it would be "rootless". That is a major difference in a lot of respects, including security, and you can find quite a bit of documentation on the differences between those operating modes online; it wouldn't fit in a comment. Rootless is generally considered the better mode, though there are some things that still require a rootful container.

In the upcoming NixOS 25.05 or current unstable, there are some tools you can use to run containers rootless as another user more easily using a new $name.podman.user = ""; setting. From what I understand they'll still be root-managed systemd system services that require sudo to operate, but that means privileges get dropped by systemd before running Podman, instead of dropped by Podman before running the container. This stuff is recent and I haven't used it, I just happen to know it exists, relevant nixpkgs commit if you wanna dig into it yourself: https://github.com/NixOS/nixpkgs/commit/7d443d378b07ad55686e9ba68faf16802c030025

FWIW, your domain will most likely eventually get used by spammers and then it'll be an endless string of somewhat expected but unpredictable failures from there on onwards, with no actions you can take to reduce it. It's good to keep an eye on what comes in but I wouldn't invest too much effort into failure alerting.

My crappy electric Philips toothbrush from the internet of shit era. If you press the single button it has slightly wrong it goes into some Bluetooth pairing mode or whatever that you can't take it out of until it gives up 2 minutes later.

It's the usual combination of AGPL + CLA, they're allowed to relicense to any license of their choice at any moment. They've had the CLA in place since the previous SSPL license and the more-previous BSD license naturally allows that kind of stuff.

On the other hand, Wikipedia doesn't allow original research and discourages primary sources while that's very much part of what a journalist is expected to do; they write the secondary sources Wikipedia runs on. It's a much harder job to discover and vet primary sources.

There are both dumps with full history and ones that are just the current set of articles. The full dump happens once a month on the 1st, but will often take ~2 weeks to run to completion, so you probably have to look back to the April 1 2025 dump for those. The metawiki dumps page has all the info.

Darts. World champion level stuff is vaguely watchable but remove the announcer/referee's energy and it's like a bad sitcom with the laugh track removed. I was brought to a tournament as a kid and I've never been in a room where everyone was that level of bored watching random people throw a fifty or whatever for hours on end.

That's what I've been trying, yesterday ended up being a little more fruitful (internet complaining trick worked!) and luckily gave me more interesting rooms, though I'm not convinced it was any action on my part that did it.

Started Blue Prince, but to be honest I haven't gotten past the initial "RNG wall" and I'm sorta over it. I'm 5 hours in and continue to get the same rooms I've documented in detail in my notes with little new to show for it, and while I have some leads and puzzle pieces, nothing fits. Not particularly excited about a lot of the small repeat puzzles anymore either. I get the impression that I just need one or two pieces of knowledge that the game is refusing to provide to me. Kinda hoping that the good old trick of complaining on the internet will make things work out.

That's about right. That said, we also don't know how long regular Switch/Switch 2 carts are going to last. The MaskROM used in the N64/DS and earlier eras is significantly more reliable when stored for a long time than the modern NAND Flash memory as used in the 3DS/Switch+. I suspect key carts won't have any NAND Flash inside (they don't need gigabytes of capacity just to store a game name + icon) and might physically last longer.

Of course, key carts are all going to drop to zero value practically overnight when Nintendo eventually pulls the plug, while real carts will die one by one.

We won't know for sure what's actually going on under the hood until the console is cracked wide open or there's a devkit leak, but my speculative guess is that some details of the GPU are 'emulated'/recompiled. PC AAA games tend to include lengthy shader pre-compilation wait times, console games don't have that wait time because the shaders are pre-compiled by the developers when building the game, specifically for one piece of hardware. The games themselves then fully rely on those pre-compiled shaders. They're going to need shaders that work with the Switch 2's GPU, which is going to involve some kind of imperfect translation process.

AMD was able to design better hardware that works with older compiled shaders, as done in the PS5/Xbox Series (and Pro consoles). That's not a super common feature, but I imagine that AMD is more motivated to keep Microsoft/Sony happy than Nvidia is to keep Nintendo happy. AMD's graphics division might as well shut their doors if it wasn't for the consoles, meanwhile Nvidia is raking in trillions from the AI boom and would rather forget about gaming.

Windows prefers to deactivate or minimize the write cache on removable devices, most of the common Linux distros generally don't make such changes. Microsoft has a very good reason for that default: not a lot of people actually use the "safely remove hardware" option and if the cache is enabled, using and waiting for that is a hard requirement for the data to have actually made its way onto the drive.

Just the usual case of survivorship bias. The long term subscriber base of "we need to go elsewhere" gathering points is mostly comprised of people that either don't vibe with the majority destination for whatever reason, disagree that there was ever a reason to leave in the first place, or don't actually want to leave but just want to complain about the current place.

Github: https://github.com/suitenumerique/docs

Self-hostable, but it seems like an absolute behemoth of an application if their "non-production-use-only" docker-compose file is to be believed, and I couldn't find any production-ready deployment instructions on a quick skim. No obvious signs of federation and I didn't see anything on their roadmap, not sure it would make a lot of sense for this though.