notabot

It’s been quite a while since I’ve used sleep on a laptop, but it worked well on my Dell (latitude I think, as I said, it’s been a while). It did take a little experimenting with sleep levels to get it reliable, but once it was it worked for years.

ETA: I realise that saying “it worked for me” is probably intensely annoying, my appologies for that, but I thought a counterpoint might be a useful extra data point.

Fair, that maybe came across harsher than I meant. Refusing to provide packages because you don’t use the system is fine, but please provide a tarball that I can unpack, rather than some dodgy script that has to try to work with the differences in those ststems anyway.

Better to do away with the entire concept of downloading and running a shell script like that, and use distro native packages instead. It’s not hard to create DEB or RPM packages, ebuilds aren’t too bad either, and it sounds like AUR packages are managable too.

The entire concept of blindly downloading a script, running it as root, and hoping that, in the best case, it’d install the version of the software you want is a bit crazy. If the upstream developers refuse to provide packages, please, at least, provide a tarball.

This is excellent article on enshitification, some of the factors that can lead to it, and ways founders could think about it to hopefully avoid it. What it doesn’t seem to talk about is how Tailscale intends to avoid it, now and in the future.

The joys of distributed algorithms. You can now get more errors, more quickly than before!

I remember writing a chat system in assembler, for DOS, using, IIRC, IPX networking. When it went wrong, one or more machines would just freeze, with the string “NETWORK ABEND” in the middle of the screen.

I should fork vim and call it ‘death’, so I can shout “give me vim or give me death!” any time someone suggests a different editor.

Surgery, especially on animals.

In any other context, someone cutting you open, slicing bits out or rearranging them, them sewing you shut would be considered horrific, but we do it because we know that the short term suffering out weighs the long term harm of not doing it. When you choose it for yourself it might not be too ‘evil’, but an animal would not understand, even if you know it will mean they get to live a long, happy life, free of the pain and suffering that issue would otherwise cause.

Piefed seems to have this, and the ability to subscribe to posts as @TheLeadenSea@sh.itjust.works asks about below.

Migrating is fairly straightforward, it can import your lemmy settings to get you up and running quickly, and the systems interoperate seamlessly, which is fantastic to see.

These things are usually buried somewhere in the small print, and it might even have been in some “hey, look at this exciting new prek we git you” email from your employer when you/they joined the scheme. It might have been something like “Any items we provide to assist with member’s physical therapy remain the property of <evilcorp> at all times, and must be returned at the end of the therapy”.

Just treat the tablet as what it was provided as, a way to access their app, and be ready to return it afterwards.

Bear in mind that they already have your home address, as they sent the tablet to you, that address is geolocated, and anyone with a phobe passing near you will have enumerated any wifi networks and possibly bluetooth too and geolocated those.

They already know what devices are around you unless there’s not been a phone within range since you got them.

You were sent the tablet in order to be able to access the the app they provide. I strongly suspect that it is actually a loan, and they will want it back when you are finished with it. Given that, you shouldn’t even attempt to root it. Use it for what it is intended for, gain some benefit from that, hopefully get your massager, and return the tablet when you’re finished with it.

Unless you deliberately give them more information, there’s not much new they can gain about your environment from the tablet. What you do in the app is going to be much more valuable data to them as it’ll give them information about you and your health that they could not gain any other way.

That does feel rther like jumping out of a plane and hoping you can finish making your paracute before it’s too late.

The concept of moving on from X11 is a good one, but making Wayland just a protocol that every compositor has to implement separately, and having so many optional larts to the spec seems like a guarantee that the ecosystem around it will never properly mature.

The KiCad developers have a good article about some of the issues with Wayland here.

Hmm, that one worked for me, but maybe the wayback machine will work for you? https://web.archive.org/web/20250618100950/https://www.linuxjournal.com/content/arch-linux-breaks-new-ground-official-rust-init-system-support-arrives

The article vanished some time after being published, here’s an archive link.

They’re publishing articles that are completely false, which suggests failures are the writing and editorial levels, whether or nit they use an LLM. It’s going to take a lot of high quality, accurate, articles to regain my trust.

It looks like the article was AI, it’s been pulled from the site.

Blast. This sounded like really positive news, linux as an ecosystem desperately needs to revisit its init process choices, but there really doesn’t seem to be any hint of it elsewhere. There is a rye that’s written in rust and which has an init command rye init. I wonder if it’s a case of an LLM latching on to that and just making up the rest?

If you are just a user, in that a computer is just a tool you use, then you’re right, there’s comparatively little reason to be concerened or even know about the underlying details of the system. If you go further and start making changes to your system, or even building more complex systems, over time you will find yourself forming quite firm opinions about various parts of the underlying system, especially if you’ve had experience with other options.

Honestly, I’m not sure, I was looking at Devuan, but then noticed that Debian supported sysvinit natively so I went that route instead. I figure that sticking to the source distro was going to give me fewer headaches, and so far it’s been plain sailing.

Debian, installed without systemd as per the wiki. So far I’ve not hit any issues, whilst I’ve recently ended up diving through both kernel and systemd code to find the root cause of an issue I was hitting on one server. I could have just bodged past it, but I wanted to actually understand what the issue was, and what else it was going to affect.