Sure, don’t mock. Just test in production

You’re probably looking for these 2

• https://github.com/blacklightpy/PlymouthXP
• https://wiki.archlinux.org/title/Plymouth

I suspect those may depend on choosing a particular response to some of the previous questions

Sure, because more java is all they ever needed, apparently 🤣

CPUs are also somewhat choked. I had to use throttled to make mine run above 2.4 GHz under load. (You need HWP_MODE and possibly Disable_BDPROCHOT, if anyone’s interested).

But other than that, waaaay better compared to …70 laptops, and some models seem to beat maxed out t440p-s. Also quicksync massively speeds up video decoding/encoding, so I’m overall happy with mine so far.

Mastodon also doesn’t have e2ee for DMs (AFAIK), so it’s still better to stick with signal/matrix for that

Still no ligatures :(

Eh, yet another piece proprietary garbage. I’d rather use plain wayvnc or waypipe.

I mean, they said they don’t like flatpak explicitly, and appimage is kinda the same thing but bulkier, standalone nix is similar as well except the lack of sandboxing stuff, and spinning another distro in a container seems overkill-ish. Idk, honestly, mb they prefer the windows way of downloading random installers from the web or that clusterslackery of placing stuff in /opt by hand

Oops, my bad

If you’re on arch/nixos, that’s fine since stuff you may need is most likely in the repos already. If you’re on Debian/Ubuntu derivatives, good luck with 100500 ppa-s

Bypassing parental control is a great learning opportunity, tho :D

Kinda follows from the description on their website:

You should use KDE neon if you are an adventurous KDE enthusiast who wants the latest and greatest from the KDE community as soon as it’s available, with no delays, opinionated patches, or UX changes.

Although, yap, I may’ve put it a bit too harshly, and the same may be applicable to using KDE on many rolling release distros.

To be fair, the only problem I had while using it (except for the usual need to add a ppa to install literally anything) was exactly the same I encountered on arch: sddm just died after some updates and refused to start. What made it worse, however, was that they decided it was a great idea to configure the same keyboard layouts both for the graphical session and tty, so I couldn’tc even login to fix it :/

Well, you might’ve entered the password incorrectly a few times, and then faiilock faillocked the account. Can be fixed by going to another tty (e.g. Ctrl+alt+f3), logging in as root and faillock --reset --user your_username_here. If that doesn’t help, that’s probably neon’s issue (mb they messed up pam stuff or something).

On a side note, KDE neon is not exactly stable for daily driving, I’d suggest switching to another distro that’s not meant for testing recent KDE stuff

Idk, I probably haven’t used Debian derivatives long enough, but isn’t installing random .deb-s somewhat of a bad practice? I mean, repos exist for a reason (ignoring the fact they usually have like 3 packages in the official repos)

Yeah, whatever. If you don’t like the community, you leave it. Or make your own unofficial community with blackjack and hookers. As simple as that.

Well, it may be worth checking… As soon as they open the compiler, that is.

The Gray Layout installation script ran the rm -rf command, which normally removes all files from the device

Translation difficulties, or does the author really think that’s what it’s normally used for?

So, you have a phone that does the tethering or something? Maybe, It’s some bug on its (or their, depending on how close you two are) side? I’d try another device with the same hotspot.

Alternatively, the laptop may be connected to several networks at the same time and be using whatever works. Can probably be checked by verifying ips of the phone and the laptop.