Piper is less than 2MB, and allows reconfiguring Logitech mouse buttons. It’s available in Debian and Ubuntu package managers.

Screenshot:

I had to use Piper to get exotic features like having mouse 6, 7, 8 buttons function as mouse 6, 7, 8, rather than the default of alt-tab and ctrl-v.

Sure, here are instructions for getting Linux Mint running: https://www.linuxmint.com/download.php

These instructions are for creating a USB flash drive that functions as both a live environment or an installer. If you don’t want to install it yet, this allows you to try it out while booting just from the flash drive, without modifying your hard drive at all.

Sorry if it wasn’t obvious, I’m using sysvinit.

My favorite is Debian, with systemd uninstalled. At this point, you can’t install Debian without systemd, but you can uninstall systemd after OS installation.

It used to be that most desktop environments in Debian depended on libpam-systemd, which depended on systemd and systemd-sysv. More recently, desktop environments just depend on libpam-elogind and elogind which is only part of systemd, and allows you to use sysvinit.

I prefer sysvinit mainly because I find it easier to create custom services out of my own programs. My success rate at doing this in systemd is 1/3, and in sysvinit about 10/10.

I also had a problem where a Debian-based embedded system had some kind of broken NTP client running on startup, and due to systemd, I couldn’t figure out how to disable it. It would set the time to several years into the future, as soon as it first got a network connection on each startup.

My problem with that theme is that it doesn’t highlight any buttons. I believe all buttons should have borders, especially the ones the titlebar. This helps distinguish a noninteractive label from an interactive clickable button.

This survey doesn’t distinguish between levels of cloud service provider, so I was a little confused.

Virtual private servers, cloud virtual servers (like AWS), cloud-based software where you provide code or a program and the cloud system runs it on a server of its choosing, and cloud-based systems where someone else provides the software (like Google Docs).

I assume bash scripts using jpegtopnm | pnmtopng are also in the neutral good category (from Netpbm).

Windows is just as hard as linux, harder even with all the layers of obscurity.

Windows used to be easy. Now, it’s so obscure and locked down that only Microsoft can maintain your computer. And they maintain it for their own benefit, at your expense, with mandatory ads and lockouts.

SSHFS is very mature. I use it for administering several home servers.

It works so well that they added a mode where some users can have SFTP only access (without SSH shell) so you can set up shared directories. It was easier to set up (for me) than CIFS or NFS.

Jellyfin depends on proprietary Microsoft .NET, even on Linux.

It’s still better than Plex and Emby, which are fully proprietary, and have no source code. But I will stick with sshfs with kodi, and nginx plus mpv for now.

Sure, here are some:

http://security.stackexchange.com/questions/259088/ddg#270934

https://en.wikipedia.org/wiki/Digital_signature

The main feature would be that if flathub (or a hacker with access to flathub) acted maliciously, digital signatures would prevent them from issuing malware infested updates to flatpaks. Only the software’s originator would have the cryptographic key needed to sign releases of the software.

The risk of dependency vulnerabilities is real.

Also, flatpak packages are not digitally signed, unlike apt and all other major Linux distro package managers.

This article seems like a lot of FUD written from an anti-FOSS perspective. In their second point, they say that F-droid’s inclusion policy is “ridiculous” for requiring programs exclude proprietary software. I think the author is ridiculous for asking for this. This is what F-droid is for. I don’t want any proprietary apps or libraries on my phone. If developers only want to work on their proprietary software, they don’t get into F-droid. If they make a modified FOSS version and put it in F-droid, and let it bitrot and go unpatched when vulnerabilities are discovered, and F-droid issues a security advisory for that program, that’s not F-droid’s fault.

I think that wormhole.app page is different software from magic wormhole (and warp). It just has a similar name. wormhole.app does appear to be proprietary.

Thanks. I think I found its homepage, is it the same as this? That looks like part of Gnome, so should be open source too. (It’s maybe available in your operating system without needing a flatpak, if you would prefer it that way)

I’m not familiar with warp, and couldn’t find it with a search. But I did find magic wormhole, and it appears to be MIT licensed, so it is open source. I also searched packages.debian.org and found it, so definitely open source.

As for firewalls: it might only block incoming connections, or has an exception for LAN hosts. I’d have to see the configuration to say more.

ydotool is missing a lot of features. It emulates an input device, so it can only send inputs to the active window. xdotool can send keystrokes to non-active windows, and has features for searching for a window to send to. xdotool can minimize, dismiss, or move windows around.

I’m aware of newton. It’s a work in progress, though, and doesn’t have as many features as X11 accessibility has. Although it might have enough features eventually, I worry that X11 will be deprecated by operating system vendors before that.

I worry about Wayland for the features it drops from X11. Wayland will never have xdotool support, due to its security model. I worry about onscreen keyboards for drawing tablets and screen readers for the blind.

Proton in Wayland works well in Ubuntu out of the box. I don’t think it matters if it is native or an X11 compatibility layer, since the games I played ran better than they did in Windows 7.

I’ve done this with Debian before, and it works fine. Linux usually mounts the root filesystem based on its UUID, so it doesn’t matter if changing the motherboard caused a change from /dev/sda to /dev/sdb .

If you use the proprietary Nvidia driver, make sure to update it to a version that supports the new video card. If you use the open source Nvidia driver, you should be fine even if it’s old, because it will at least support starting up in an unaccelerated mode.