Showerthoughts was one I tried. I don’t remember specifics but I tried a couple times to post actual thoughts I had in the shower and they got insta-banned by a bot so I just gave up.

Oh I did and even contacted moderators a few times to try to have posts reinstated after they were insta-banned by a bot. I just got tired of fighting with it every time I wanted to participate.

I tried to like Reddit but every time I tried posting something I thought was original or thoughtful it would get auto deleted by a bot for not including the right “flair” or some other stupid shit.

Cats are wild. Mine came home once with about a quarter of his face hanging loose. I wrapped him in a towel to protect myself, cleaned him up with antiseptic and antibiotic cream, put the loose flap back in place and covered it with gauze and tape. Surprisingly he left it alone and it healed up good. If you pull his fur back you can find the scar but it did really well.

The hard part is finding an acceptable balance between good OPSEC but not pre-emptive compliance.

Key files should be key files that are associated with the device encryption, not just the password stored on a text file.

https://www.cyberciti.biz/hardware/cryptsetup-add-enable-luks-disk-encryption-keyfile-linux/

All the more reason to give him hell for doing a terrible job. If you can’t handle the heat get out of the kitchen.

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.

They straight up ambushed those guys. Makes me wonder if the car accident was staged specifically to attract emergency workers.

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

Alternatively though, if an app has KDE library dependencies for example, it’s kinda nice to not have to install a whole other desktop system wide.

I made one the other day, though I bought the music from HDTracks instead of “acquiring” it from Limewire or Kazaa. Burned it to a CD because the bus I drive has a CD player but no SD card slot or anything.

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

Other than that one disc I haven’t had any real issues getting a complete copy of the whole disc, and that disc did eventually cooperate. MakeMKV is pretty good about halting or warning you in the event of an error, checksum mismatch, etc. So I haven’t lost any data so far and I’m up to season 6. I’ll start season 7 tomorrow and try to finish the whole show in the next day or so and I’ll just keep full ISOs of these discs. I’ve got the space and an off site backup so I might as well do it at least for stuff I really like. Years ago when I first started my home server I kept ISOs of everything; but that quickly got out of hand when I started backing up my Blurays at 50GB a pop.

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.

Lemmy looks and works fine in a mobile browser; why do you even need an app?