Did… Did you just ask; why creating photo-realistic sexually explicit material of real children, should be illegal?

As far as I understand; it’s not the tools used that makes this illegal, but the realism/accuracy of the final product regardless of how it was produced.

If you were to have a high proficiency with manual Photoshop and produced similar quality fakes, you’d be committing the same crime(s)

creating child sex abuse images

and

offenses against their victims’ moral integrity

The thing is, AI tools are becoming more and more accessible to teens. Time, effort, and skill are no longer roadblocks to creating these images; which leaves very very little in an irresponsible teenagers way…

I tend to drop the link into yt1s.com

Sometimes just for audio, sometimes for the full vid.

I’m rarely grabbing more than one video at a time though.

[re-commenting as I meant this to be a top-level comment, not a reply]

I tend to drop the link into yt1s.com

Sometimes just for audio, sometimes for the full vid.

I’m rarely grabbing more than one video at a time though.

127.0.0.1 is the loopback address. Ie it’s your computer trying to reach a service its hosting (prowlarr)/talk to itself. Sonarr/Radarr should be using this address as long as prowlarr+sonarr/radarr are on the same machine.

Prowlarr is either not running, or port 8080 is blocked by your firewall.

Could always plug it in temporarily; do what you gotta do, then remove it again.

… Sata DVD-ROM drives are a thing

Hell I’ve still got one just in case

A paid plex share is a plex server that someone is running + selling access too.

This is against plex’ terms, gets plex accounts banned; and in some cases, Plex (co) has taken rather drastic action by blocking entire VPS providers from reaching plex.tv; thus plex server software no longer functions on those VPS’s at all.

Naturally, people selling shares want to maximize profit, so they use VPS providers on the cheaper end; resulting in cheaper VPS solutions being blocked for everyone.

Drink less paranoia smoothie…

I’ve been self-hosting for almost a decade now; never bothered with any of the giants. Just a domain pointed at me, and an open port or two. Never had an issue.

Don’t expose anything you don’t share with others; monitor the things you do expose with tools like fail2ban. VPN into the LAN for access to everything else.

and using DDNS

As in, running software to update your DNS records automatically based on your current system IP. Great for dynamic IPs, or just moving location.

Sure, cloudflare provides other security benefits; but that’s not what OP was talking about. They just wanted/liked the plug+play aspect, which doesn’t need cloudflare.

Those ‘benefits’ are also really not necessary for the vast majority of self hosters. What are you hosting, from your home, that garners that kind of attention?

The only things I host from home are private services for myself or a very limited group; which, as far as ‘attacks’ goes, just gets the occasional script kiddy looking for exposed endpoints. Nothing that needs mitigation.

Unless you are behind CGNAT; you would have had the same plug+play experience by using your own router instead of the ISP supplied one, and using DDNS.

At least, I did.

No. You just need to be able to exit without power. Getting back in mechanically isn’t a requirement.

It should be, but it’s not.

Both the client and server connect to plex.tv which then brokers the connection between them. They essentially work as a very limited vpn between your clients and server.

This also gives them unrestricted access to the entirety of data passed between devices; and the ability to request any and all info from your server to be handed to whoever they chose.

This is also how they allow you to ‘share’ content/libraries with each others servers; through their public infrastructure that’s collecting your information. Information they then sell to third parties to support their development and broker content agreements.

Yes. Emby was originally open source, but people would regularly fork it to remove the licensing. When they chose to go closed source; jellyfin forked that final release and has built from there.

Emby has a premier licencing system to support their development, instead of selling user data and making deals with content providers like Plex, or depending on OSS development/contributions like Jellyfin.

As far as I understand almost 80% of jellyfins current code is the original Emby code (called ‘media browser’ or ‘MB’ at the time), though to be fair, I haven’t verified that claim.

Reminds me of the BBC licence fee in the UK.

The number of people I’ve come across that are absolutely baffled by the concept of port forwarding…

Then you add CGNAT ontop and things can get really complicated for someone unfamiliar.

Plex is a privacy nightmare that’s slowly trying to faze out you having a server all together in favor of feeding you commercialized content from other providers; and many people find Jellyfin is far too unpolished/disorganized for a lot of debatable reasons I won’t go into.

I’ve been quite happy with the middle ground: Emby. It’s not FOSS, but is well polished with consistent development, great feature parity across platforms, excellent clients for pretty much every device I’d want to use, and a helpful community ready to assist with any problems you come across. They also have a heavy focus on privacy; with no third party partners collecting your info like Plex, and no telemetry sent from servers/clients.

The lifetime premier license I bought 7 years ago was well worth it.

they probably made a really good return before it shut down.

Part of the sentence was to forfeit $1million in profits, I’d say they did pretty well for themselves.

As long as you didn’t want to send it whole…