Yes, it’s the next step and an evolution because it is far more of a trust less approach. With VPNs you need to trust your provider. If they “give you up” then you’re well and truly fucked. For I2P there is no way for a malicious node operators to parse out who is doing what. And the source code you can vet yourself so no need to trust it. Still if you have actors working together in the nodes, the torrent provider and at the ISP level then you can most certainly find a way to break the layer of secrecy. The barrier is however vast and so far police haven’t spent that much effort on piracy because it isn’t a serious crime in the eyes of the law. And I don’t foresee that they will for many years.

It’s also far more accessible than say Usenet and VPN+private trackers. Which is a very good thing for privacy in general.

Yes, it’s the next step and an evolution because it is far more of a trust less approach. With VPNs you need to trust your provider. If they “give you up” then you’re well and truly fucked. For I2P there is no way for a malicious node operators to parse out who is doing what. And the source code you can vet yourself so no need to trust it. Still if you have actors working together in the nodes, the torrent provider and at the ISP level then you can most certainly find a way to break the layer of secrecy. The barrier is however vast and so far police haven’t spent that much effort on piracy because it isn’t a serious crime in the eyes of the law. And I don’t foresee that they will for many years.

It’s also far more accessible than say Usenet and VPN+private trackers. Which is a very good thing for privacy in general.

Yes, it’s the next step and an evolution because it is far more of a trust less approach. With VPNs you need to trust your provider. If they “give you up” then you’re well and truly fucked. For I2P there is no way for a malicious node operators to parse out who is doing what. And the source code you can vet yourself so no need to trust it. Still if you have actors working together in the nodes, the torrent provider and at the ISP level then you can most certainly find a way to break the layer of secrecy. The barrier is however vast and so far police haven’t spent that much effort on piracy because it isn’t a serious crime in the eyes of the law. And I don’t foresee that they will for many years.

It’s also far more accessible than say Usenet and VPN+private trackers. Which is a very good thing for privacy in general.

Hmm, the 4:3 versions did make it to DVD but finding the old version for things is never easy. It’s a common wish however, in Anime circles in particular.

Looking at a predb over scene releases and going back as far as they go I see that the naming standard, as I suspected, didn’t hint at neither aspect ratio or resolution.

https://predb.net/search/south.park.s01?page=1

However if you look for DivX or Xvid releases I’d say it’s fairly likely they’ll be in 4:3 since Xvid by and large had gotten replaced by H.264 / X.264 by 2017 which is the earliest release I can confirm is going to be the remaster since it’s from the Bluray that released then:

https://www.dvdsreleasedates.com/movies/4399/South-Park-(TV-Series-1997-).html

The above is likely not fully complete so the remaster might’ve happened between 2004 and 2017, and this might be readily available information but I’m running out of time…

So basically my tip if you’re lazy is look for Xvid/DivX and cross your fingers. If you’re not then correlate the remaster date/release date to the predb and look for a scene release from before the remaster dropped.

That’s what I’m saying. It’s like everyone knows some college kids smoke pot from the smell in the dorms, but Police can’t legally search room by room to find out who it is, they need a search warrant which they need more than a general suspicion that someone in the dorms smoke to get.

Same with I2P, it’s done in a public setting so from traffic patterns we can be pretty sure someone is downloading a shit ton, and that it’s likely illegal content. Residential IPs have little reason to consistently download several GB files on a daily/weekly basis, streaming and download also look vastly different profile wise and at least no one I know of go to those lengths to try and mask their traffic patterns by trying to make streaming look like download or vice versa.

But as I said and you reiterated, you still need to crack the encryption to actually prove it in court. But given a specific target there are many ways to do that. A generic approach is likely not going to happen. Which means that I2P is secure much like having a secret chat in a crowded place like Grand Central Station in NY. You know that people are meeting there to chat about illegal stuff but you don’t know who. It becomes much easier if you know who to follow and eavesdrop on, but of course still not easy.

It is however nowhere near as safe as communication over channels that aren’t public to begin with. But such of course do not exist outside military and other special contexts.

But at the same time I2P is still built upon TCP/IP so it’s still like encrypted yodeling. Finding out who’s likely yodeling down movies is rather easy. The protection instead lies in the high barrier to prove exactly which movie and when so as to pass the barrier for court admissable evidence.

Now don’t misunderstand me, I2P is great stuff and I’ve used it on and off for years, but it shouldn’t be treated as the holy grail of safe and secure communication. Nothing can truly be that if it’s built on TCP/IP for fairly obvious reasons.

1337x is probably the biggest these days and it just needs a free quick and easy account to upload a torrent. If you’re concerned about privacy then use a mail relay like Firefox Relay which is free.

Ah, right, read to fast it seems! Though that still leaves the possibility of software firewalls, but any OOTB ones wouldn’t be doing any packet inspection.

Do you have a firewall? Packet inspection in particular can wreak havoc on speeds.

Yes, which is exactly what I’m stating. Showing a forcibly non-upscaled video (or one where you’ve manually tweaked the upscaling for that matter) is likely not what you want because there are no circumstances where that is what you’d watch on that particular screen. It could perhaps work as an example of how that video would look if you had a 1080p monitor of the same size instead of the 4k one you have, since it scales in a linear fashion, a pixel of 1080p is 4 pixels in a square on a 4k screen. But that’s likely not what you want to test. Instead the thing you do want to test is “does it matter if I download X content in 1080p or 4k? How big is the difference really?” And if that is the question you need to let it upscale.

Not really possible. A 1080p video smashed into a 4k container (so it can actually represent the 4k part) would look worse than a true 1080p video file since that would get up scaled by your TV or monitor in most situations.

Best comparison would be making a playlist of the same video first in 1080p and then 4k.

Tell them to move to yubikey or similar hardware key which is far more secure than any password policy will ever be and vastly more user friendly. Only downside is the intense shame if you manage to lose it.

The key should stick with the user thus not be stored with the computer when not in use. The key isn’t harmless of course but it takes a very deliberate targeting and advance knowledge about what it goes to and how it can be used. It’s also easy to remote revoke. If you’re extra special paranoid you could of course store the key locked at a separate site if you want nuclear codes levels of security.

Yeah, I was just confused about the direction/flow he was asking for. He clarified and his use case is fully solvable. Just not something I’ve personally dabbled in since he wants it for non http traffic.

Well thats just a normal reverse proxy then. In my setup I use Caddy to send traffic through the NetBird managed wireguard tunnel to my home machine that runs Jellyfin but for any outside observer it look like it’s my VPS that is serving Jellyfin.

You want to group by IP in grafana and not using http traffic? Why not group on data or metadata in what is being sent which is the common approach?

If you can fool the Internet that traffic coming from the VPS has the source IP of your home machine what stops you from assuming another IP to bypass an IP whitelist?

Also if you expect return communication, that would go to your VPS which has faked the IP of your home machine. That technique would be very powerful to create man in the middle attacks, i.e. intercepting traffic intended for someone else and manipulating it without leaving a trace.

IP, by virtue of how the protocol works, needs to be a unique identifier for a machine. There are techniques, like CGNAT, that allows multiple machines to share an IP, but really it works (in simplified terms) like a proxy and thus breaks the direct connection and limits you to specific ports. It’s also added on top of the IP protocol and requires specific things and either way it’s the endpoint, in your case the VPS, which will be the presenting IP.

Preserve the source IP you say, why?

The thing is that if you could (without circumventing the standards) do so then that implies that IP isn’t actually a unique identifier, which is needs to be. It would also mean circumventing whitelists / blacklists would be trivial (it’s not hard by any means but has some specific requirements).

The correct way to do this, even if there might be some hack you could do to get the actual source IP through, is to put the source in a ‘X-Forwarded-For’ header.

As for ready solutions I use NetBird which has open source clients for Windows, Linux and Android that I use without issues and it’s perfectly self-hostable and easy to integrate with your own IDP.

That doesn’t sound right, I’m betting it’s a bug due to some in the series being bought and some on the time limit deal. Reach out to support.

No the scenario a VM protects from is the T110s motherboard/cpu/PSU/etc craps out and instead of having to restore from off-site I can move the drives into another enclosure and then map them the same way to the VM and start it up. Instead of having to wait for new hardware I can have the fileserver up and running again in 30 minutes and it’s just as easy to move it into the new server once I’ve sourced one.

And in this scenario we’re only running the fileserver on the T110, but we still virtualized it with proxmox because then we can easily move it to new hardware without having to rebuild/migrate anything. As long as we don’t fuck up the drive order or anything like that, then we’re royally fucked.

Yes, but in the post they also stated what they were working with in terms of hardware. I really dislike giving the advice “buy more stuff” because not everyone can afford to when selfhosting often comes from a frugal place.

Still you’re absolutely not wrong and I see value in both our opinions being featured here, this discussion we’re having is a good thing.

Circling back to the VM thing though, even if I had dedicated hardware, if I would’ve used an old server for a NAS I still would’ve virtualized it with proxmox if for no other reason than that gives me mobility and an easier path to restoration if the hardware, like the motherboard, breaks.

Still, your advice to buy a used server is good and absolutely what the OP should do if they want a proper setup and have the funds.