There’s a whole video game series on why this is a terrible idea. (Horizon Zero Dawn)

Generate a unique key for each client or device. SSH keys identify devices, not people, so I do not recommend sharing the same key between two different devices.

I generally do a few things to protect SSH:

1. Disable password login and use keys only
2. Install and configure Fail2Ban
3. Disable root login via ssh altogether. Just change “permit root login” from “no password” to just “no”. You can still become root via sudo or su after you’re connected, but that would trigger an additional password request. I always connect as a normal user and then use sudo if/when I need it. I don’t include NOPASSWD in my sudoers to make certain sudo prompts for a password. Doesn’t do any good to force normal user login if sudo doesn’t require a password.
4. If connecting via the same network or IPs, restrict the SSH open port to only the IPs you trust.
5. I don’t have SSH internet visible. I have my own Wireguard server running on a separate raspberry pi and use that to access SSH when I’m away, but SSH itself is not open to the internet or forwarded in the router.

So far I haven’t seen any attempts to change their user agents. I’ve seen one or two other bots poking around, but nothing to write home about so I’ve left them alone.

I have heard however that changing user agents is a tactic they do indeed employ, especially Claude, so it may be that I’ll eventually have to adapt my defenses.

I’ve been fending off AI bots the last week or so; wrote about it here:

https://gerowen.substack.com/p/the-ai-data-scraping-is-getting-out

Why did they get removed? I feel like I’m missing a whole backstory here.

I’m not sure. I’ve only noticed it on my TV and have even noticed it with content that I personally ripped from DVDs or Blurays and encoded to x265 or AV1. Since it only affects the TV apps I’m wondering if it isn’t a lack of support for some color space or something by the TV hardware because when I’m encoding I don’t usually change anything about the dimensions, color space, frame-rate, etc., just the codec and quality. If the video is 10 bit, I encode it as 10 bit. If it’s HDR, I pass that thru. I’ve checked with the mobile and desktop app and the web player on content the TVs had issues with and those same files played fine everywhere else, so it’s something specific to the LG and Roku apps for Plex.

I do my own ripping direct from disc and I’ve still seen it happen. So far it’s exclusive to the TV apps so I think it’s something to do with the lack of hardware support for certain things.

It had the best loading animation with the comets flying by. Much better than IE rotating and becoming the planet earth. This was back when you actually had to wait for pages to load.

Plex has recently started applying a green filter to certain content.

The files Plex has a problem with work just fine in Jellyfin.

They are regulated, but there’s a lot of breakdowns in the system. People passing background checks who shouldn’t, prior offenders passing background checks because local cops didn’t report them to the feds, etc. The DC Navy Yard shooter years back literally had fired a weapon into his neighbor’s apartment before and still passed a background check to buy the weapons he committed the shooting with. I also think if you’re a parent and you leave your weapon accessible by your children, and they go shoot up their school, you should be held at least partially liable. As somebody who is former military, the civilian population gets away with a hell of a lot with regards to firearms. No federally mandated training standards, concealed carry licenses are haphazard and go state by state, and not all states recognize other states’ permits, no federally mandated storage requirements, etc. When I was in the military, if I wanted to go target practice on base with my personal weapons I had to register them with the provost marshal on base, keep the weapons and ammo separate in locked boxes out of my reach while driving to the range, etc. And if one weapon went missing the entire base was locked down; gates closed and nobody in or out until it was located. Civilians get by with way too much.

I think a lot of our problem is loose are missing standards at the federal level, which leaves each individual state to kind of make things up as they go along and not communicate properly with feds when things go wrong.

I’m on my laptop so I thought I would elaborate on my first comment to give you things to watch out for if/when you update. I’ve been hosting mine with the zip file manually installed with my own Apache/PHP/MySQL/MariaDB setup for ages now without issue. It’s been rock solid except for, like I said, the occasional changes required to take advantage of new features such as adding new indices to the database or installing an additional php addon. Here’s the things that I noticed with updating to 28.

• The 3 dot/ellipses menu was missing in the web interface and was replaced with dedicated buttons for “Download”, “Add to Favorites” and “Delete”. Shift clicking was also broken. This meant that when I, for example, take a lot of photos for a holiday, I can’t use the web interface to select a large range of multiple files and then move them all from “InstantUpload” into a more permanent album. I either had to use the mobile app, or do them one at a time. The ellipses menu, along with the options to bulk “move/copy” have been added back since then with the *.1 update, but shift clicking in the web interface to select a range of files is still broken.
• The “Retention” app, which is listed as a “Featured” app doesn’t function any more. I used it to automatically delete backups of my Signal messenger, files in the “InstantUpload” folder that were over a year old, etc. You can enable it, but it doesn’t actually work and just throws errors in the log file, which is now reported in the “Overview” portion of the “Administration” page with a note of “X number of errors since somedate”, and prevents you getting the green checkmark. It’s probably safe to assume that other apps will also have issues because I had half a dozen get automatically disabled with the update.
• Occasionally when I use the web interface to move or copy a file, I’ll get an error message that the operation failed. Sometimes this is true, sometimes it’s not and the operation actually succeeded. If it ends up being true and the move did actually fail, doing it again results in a successful move.

It seems like they’ve made some substantial under-the-hood changes to the user interface that shouldn’t have been shipped to the “stable” channel. It’s not completely broken, it “is” usable, especially after they restored my bulk move/copy button, but I still can’t use the Retention app, at least last time I looked, so I’ve literally got daily cron scripts to check those folders for old files and delete them, then trigger an occ files:scan of the affected directories to keep the Nextcloud database in sync with the changes. This however, bypasses the built-in trash bin so I can’t recover the files in the event of an issue. I actually considered rolling back to 27 for a bit, but decided against it, so if I were you, I would stick with 27 for a while and keep an ear to the ground regarding any issues people are having that are or aren’t getting fixed in 28.

I’ve hosted mine for years on my own bare metal Debian/Apache install and 28 is the first update that has been a major pain. I’ve had the occasional need to install a new package to enable a new feature, or needed to add new/missing indices to the database, but the web interface literally tells you how to do those things, so they’re not hard.

28 though broke several of the “featured” apps that I use regularly, like “Retention”. It also introduced some questionable UI changes that they had to fix with the recent .1 update. I’ll get occasional errors when trying to move or delete files in the web interface and everything. 28 really feels like beta software, even though we’re a point release in and I got it from the “stable” update channel.

She straight up admitted that she was essentially a sock puppet CEO and would offer no friction to anything Musk wanted.