Wolf314159

Yeah this reeks of discrimination and exploitation.

Well there's your problem. Public wifi is going to have systems in place to stop exactly the kind of thing you're trying to do.

But you can represent up to 999 lab techs with only 1 more digit. Or 946 lab techs with just 2 alpha numeric characters. Heck just 2 letters gets you 676 combinations. About 17,000 combos with 3 letters and more than 40,000 if you use 3 alphanumeric characters.

Yeah, it's super weird. I once named a file with mixed case, but one of the letters was the wrong case. Renaming the file didn't work at first. Renaming a file named PAscalCase.txt to PascalCase.txt resulted in no change to the filename. Windows continued to show it as PAscalCase.txt. I had to rename it to something totally different with different characters entirely, then rename it again to get it right.

Coffee is also a seed, not a bean.

Are you implying that your fingernails were never cells of your body? How does that work?

The speed limit need not be the same for each direction of travel. The speed limit changes at the sign. There is no expectation that the signs be at the same road stationing for opposing traffic. If the open street map database can't handle that appropriately, then there is no correct way to map this situation.

"Fingerprints?"

Cut to an animaniac holding a timid looking purple clad rock star.

"No, thanks." -Dot

I have setup and run what are basically HTPC's for decades now. Kodi running on a Debian based Linux distribution or just Debian is a solid recommendation and has lots of support for infrared remotes, but kodi can be very fiddly to setup properly. It will work, but don't expect it to work "out of the box". You'll probably still need a mouse and keyboard for anything outside Kodi. You'll have to read a bunch of documentation and do some customizing to get the most out of Kodi. It's still easier than most other setups, but it will feel very frustrating if it's your introduction to Linux too.

I've moved to using my HTPC primarily as a server. Once you get comfortable with linux and docker, setting up new server services like Jellyfish, Plex, and and *ARR stack is relatively trivial. The advantage here being that you can serve your media to any device that can connect to your server. For me that means one library of media to share with any TV in my house, any mobile device I own, and any friends and family computer savvy enough to download the right apps and setup an account. If your network (and your Internet connection) isn't reliable this kind of setup may not work very well for you at all. For example, Plex account authentication will fail is you don't have Internet. Jellyfin and Kodi fair better when Internet is only available occasionally or is unreliable.

My least favorite part of using Kodi was setting up the remote. Even worse was trying to configure controllers for retro gaming. The situation is MUCH better than it was, but is still far from easy. I was kind of able to side step the remote problem because now I can just use the remote for the TV (if it supports the Plex or Jellyfin apps) or another streaming stick like fire stick, Nvidia shield, or Roku. My Nvidia shield can pair with any Bluetooth controller and runs RetroArch so that problem was side stepped too. ROMs can be copied via samba shares or loaded directly by a USB drive.

TLDR: Kodi has built-in support for IR, but streaming sticks are cheap, and in the long run I found setting up a server was more versatile, more reliable, and less stressful. I know, I also hate it when people ask for a specific solution and others recommend asking a different question. But in this case, my experience is that IR remotes suck, are flaky, and not worth it if there is any other option.

Do you mind sharing what brand retail UPS weren't lasting a year?

I'm dealing with similar brownouts and also an area with lots of lightning. I got about 5 years out of my UPS batteries. Wondering if I've just been lucky.

Windows is never going to like an NTFS that has been touched by another OS even if it windows was completely shutdown during that time. Reading the NTFS partition might be okay. But, last I checked none of the Linux drivers could write without windows noticing and fouling things up. If that has changed it would be welcome news to me despite my warning use of windows.

If windows (and to a lesser extent that other OS) came bundled with some ability to mount, read, and write filesystems popular with other operating systems this wouldn't be such a problem. One shouldn't have to involve the network stack or 3rd party drivers just to share a partition on the same hardware or a portable drive with a modern file system.