Darkassassin07

This reminds me;

5-6 years ago, I was scrolling through reddit and stumbled across a link to a website that was just a generic white page with hundreds of hyperlinks on it. No other formatting or images, just row after row of links on a plain white background.

Each one was a direct link to an IP security camera somewhere in the world. Presumably these either used default logins, had no login, or the credentials were stolen somehow. There were private residences, public buildings, the interior and exterior of stores, what looked like public security cameras (like pole mounted traffic cams), some spa resort type places, even a few elevator cams. Some of them even had working PTZ controls (tho I only came across 2-3 of those in the few dozen I played with).

I wasn't entirely sure they were even real; until I spotted a phone number in one of them and gave it a call. Took a bit of convincing, but the lady that answered finally believed me when I told her how many fingers she was holding up.

I wish I'd have saved it, just to see if anyone did anything about it. I really should have fired off an email to the domain registrar or something; but... naivety 🤷

HP

Well there's your problem....

Leaking valve stem, or less likely a cracked rim. A 5$ fix while the tires were off; but more work just to fix on it's own. If it's a slow leak you keep ontop of, you may as well wait till the next tire rotation; make sure you request they replace the valve stem(s).

Not a biologist, not something I study, just a passing thought:

I would guess a large number of venomous animals are also poisonous, because you'd be ingesting their venom. Probably not always the case; you're not always eating the venom containing parts, and it my not be poisonous unless injected into the bloodstream/tissue. But that's what my intuition tells me. 🤷

Just because it's kinda interesting:

Tomatoes are technically a fruit, but they're legally, a vegetable. At least in the US.

Plex, Emby, and Jellyfin are all legal, and each have ways to serve liveTV alongside your own locally stored content, and DVR that liveTV if you want. You'd just have to purchase a liveTV subscription from your local provider (or go the Pirate route ofc).

Emby has what they call 'Emby Connect' which is entirely optional and is basically a glorified DNS service.

It doesn't proxy connections, it just passes on the hostname to the client. The server is still required to setup port forwarding or other routing like tailscale or a proxy on a vps.

Emby Connect will let you sign into your local server using your emby.media credentials, but unlike Plex it's completely optional and only works once explicitly linked to the local user of an Emby server.

I only bring it up because you explicitly said you have no idea why it doesn't work.

Take things at a comfortable pace; there's no sense overwhelming yourself. Then you just forget what you've done and end up lost in your own maze.

I started with Plex myself, almost 10 years ago. Moved to Emby, where I learned about buying a domain, setting up ssl through a reverse proxy, and just continued to explore from there. Today I run ~26 containers/projects across three systems and I'm always keeping my eye out for interesting new things.

Best of luck with your journey m8.

Sounds like you're behind cgNAT, which essentially means there's another router owned by your ISP that's between yours and the open internet, which also requires port forwarding, but your ISP will never do that for you.

It complicates things, but the solution(s) are tools like tailscale, cloudflare Tunnels, or to rent a VPS just to host a proxy/vpn.

Plex solves this by using their own public servers as a proxy for you, but this is part of how they have control over your users/server/data, such as blocking remote streaming... That makes more than a few people uncomfortable.

Plex centralizes authentication at plex.tv

When a user wants to connect to a 'private' plex server, they must first sign into their plex.tv account, which then provides the auth token needed to login to the users server (even if both the client and server are on the same lan)

With this system, Plex can monitor and control every single connection to every plex server; limiting access to whatever they want. Even your own local content.

Plex has an automatic proxy service hosted by their public servers. If you haven't or can't configure port forwarding correctly, plex will route the connection through their own servers.

The problem is, that also means Plex co has total control over your server and the data sent between it and clients if they so choose. Anything from quietly logging the data sent back and fourth, to controlling who can connect and what they can do while they are.

Jellyfin has to be correctly exposed to the internet via port forwarding or tools like tailscale/a vpn; but it's entirely your server under your control. You have ultimate control over how your server can be accessed, but that also means you're responsible for actually setting that up.

If they're willing to go that far, they're not parents worth having. Good riddance.