We are using systemd. ~/.bashrc or similar dotfiles should not be used to start services/processes automatically. Do not "sudo" anything in ~/.bashrc.
[Yes, it did that] A systemd service should be created for any processes/services that need to run automatically and persistently. The current output of `systemctl list-unit-files | grep enabled` is available at [ . . . ]
sshd is already enabled + running and listening on 0.0.0.0:22 and [::]:22. ~/.ssh perms are already 700 and ~/.ssh/authorized_keys perms are already 600. Public key authentication is already enabled in sshd and ~/.ssh/authorized_keys already contains pubkeys ENDING as follows: . . .
tailscaled is already enabled + running; the tailscale address for [host] is [addr]
It is not necessary to fix connectivity to any 192.168.0.0/16 ; tailscale interface should be used for any traffic to [host] or other hosts involved in the project; hosts/nodes lacking tailscale interface should be assigned one
[roommate + bot spent 45 minutes on trying to configure their way through NAT when not having to do that is almost the entire point of tailscale. It was just (essentially) like, "You're absolutely right. We have tailscale set up, so we don't need to be able to ssh to that other interface at all. Not troubleshooting that would have saved 45 whole minutes. Oh well, now what?"] mail.google.com##div[aria-label="Message Body"] span[contenteditable="false"]
or user styles / Stylus / etc.: div[aria-label="Message Body"] span[contenteditable="false"] { display: none !important; } mail.google.com##div[aria-label="Message Body"] span[contenteditable="false"]
It is admittedly a bit beyond "easy customizability" once you find yourself sifting through element attributes in the dev console to craft a selector ("easy" shouldn't require knowing what any of those things are, I would think), but in case you still want to actually do it, this seems to work.
Hey that's fresh. Do they have Hittitomori too?