lvl

Very appealing for a travel device running a Linux kernel. On the product page, they also mention Open Warranty, which makes me believe it will be easily serviceable - this would be a big plus, especially for a travel tablet, being able to switch the disk easily.

If you use them for your use only, or want them “cleanly” organized, consider prefixing it with something personal to you (or a generic one such as my_). For example, I’d prefix them with l_: my_rename_photos.sh, my_lightson.sh, etc.

If there’s a lot of them, write a wrapper script which would call the individual scripts from a common location (/usr/share/my-scripts/). Then, you can only make sure your wrapper script is aliased/moved in the PATH. Example: my rename, my lightson, etc.

Well, that didn’t take long, the @x handle is now an official X-Twitter account!

Wireguard is not meant to bypass detection of any kind of Deep Packet Inspection technology. It’s also stated by the project website, under the Known Limitations sections.

https://www.wireguard.com/known-limitations/

There are many characteristics (except the handshake) which can make it stand out as a P2P or VPN(-ish) traffic, and then get blocked.

Gives me the feeling someone overengineered this a bit. You can grab a Fedora Silverblue copy and get more or less the same experience with toolbox/distrobox.

Well, look at the bright side: the evolution of descentralized federation now depends on the moderation topic. I wouldn’t be surprised if someone takes federation to the next level and creates a moderation tool which would work out of the box for the fediverse, at the technology level (e.g. ActivityPub).

If and when this happens, federation has a bigger chance in replacing current centralized social networks.