TarantulaFudge

I mean that’s exactly why I don’t use these devices. ODB port is not designed to be used for extended periods of time. I’ve had them fail on me before. It’s a diagnostic port not a USB port. There are a lot of things connecting to the bus already.

Holy crap, I didn’t realize there was was some Velcro there!! I even looked for it.

I just want to say the ergonomic addon pack only the controller straps are any good. A bit confusing to put on but makes more sense when you figure it out.

However the top head strap is complete garbage. Out of all the top straps I’ve seen this one has got to be the worst. Not adjustable at all. I have a big head, regular hats don’t fit me… The headstrap is way too shallow and feels like it’s gonna roll off my head.

Took about a week to get my order email. Then a couple more days to get shipped. Shipping itself only took a couple days.

OBD is not a good solution for this. These devices can crash/fail and cause problems. It’s just not reliable enough.

I’ve got mine accessible with SSL proxy. I would say make sure you use an alternative port to help reduce exposure during scans.

Compared to what? Most services do not run PID1

Clearly post does not understand kernel booting. Initrd will never go away, you need a way to tell the kernel to start systemd, which is usually part of initramfs. Both can be compiled as part of the kernel image which can be directly booted from EFI. So basically EFI->Kernel->Decompress InitramFS->Run Initrd Boot Script (usually ends by kicking off SystemD). Initramfs is compressed to reduce boot partition usage, load faster into ram (more noticeable on HDD). You want the bare minimum of kernel modules available in initramfs to load storage drivers, filesystem, LVM, LUKS. Everything else should be modules on the root filesystem, unless it needed for boot. You can compile these static into the kernel too. Generally modules are preferable as they can be unloaded/reloaded if there is an issue. Also updating initramfs modules is annoying. I wrote my own initrd scripts and custom initramfs. You can build it all with bash scripts and configure the kernel to include the payload.

It’s perfectly fine to host jellyfin online. Use a proxy server to enable TLS and do not use default ports 80/443. Use letsencrypt for free certificates. No need for VPN to access here either. Do not expose any other ports such as SSH on default ports. Lock down your jellyfin server and any other related services behind a VPN service and block access to Internet through other interfaces (except for port forwards on your ISP for jelly). Go high on port ranges since they typically aren’t scanned or blocked. Go dual stack for best results and don’t use your router address for IPv6 more than likely you have your own /64 choose a different address for port forwards. Do not assign this address to your internal servers. Use a reserved unrouted IPv6 range internally and do NAT6. Do not allow any raw IPv6 internet access