I2P is a secure network protocol. to your ISP it’s just an encrypted stream.

it can work across any network connection. Bluetooth, Lora, ARRL, etc.

the way I interpreted your comment presented the possibility that the ISP would cut services based on the content being hosted, not as a wide area communications disruption.

https://geti2p.net/en/

your shits gay and you sound retarded

you’re that guy. congrats!

I2P

makes sense but wasn’t that already fixed with dockers rootless patches?

question, why would you leave docker for podman?

I straight up ignore anyone who does this.

I don’t give a fuck if it’s the CEO.

don’t waste my time.

PostgreSQL

fuckin gross!

what county was your mother or father born in? just 1 out of 3143.

hope your parents aren’t dead and you can’t ask them.

good luck!

/s

point is, this information used to be used as a way to align an identity to an individual, however with the expansion of digital identity information making its way on the internet the mechanism is broken.

I different method could and should be used.

OP ignore anyone saying wireguard is better than openvpn, it’s not. they are two solutions used to solve for multiple problems.

openvpn is highly configurable and is more widely supported across almost all platforms but the learning curve is medium to difficult.

wireguard is easier to setup for first timers and has stronger encryption but lacks multiplatform support and has shorter track record ensuring security and viability.

some say wireguard is “faster”, but I haven’t seen any real world instances of this being true unless you get close to the theoretical full saturation of a 1g interface. unless you’re dealing with HA or high throughput apps in a commercial setting I doubt you will run into that issue.

personally I prefer openvpn because I use it across multiple platforms and have peace of mind knowing it’s a tried and tested solution with decades of public and private support.

I too like to live dangerously.

I mount them directly from the NAS inside docker volumes.

if there are any configuration/local data files that need to be persistent, those are usually kept in ~/project/{container}. the compose file is kept at the root project directory.

home user is a daemon user created specifically for running docker containers that does not have root privileges.

well you conveniently edited your original comment, but you attacked the integrity of the post, not the content.

then you should be more active in posting “useful information” instead of complaining.

found the Russian troll!

pihole has got the best UX for DNS management hands down. it’s easy, not overly complicated, and perfect for entry-level selfhosting.

the fact that it actively blocks ads is a bonus.

nor will Plex.

I do not recommend using a seven year old as a server for the following reasons.

1. their parents will get mad
2. the neighbors might call the police about all the children you have racked in your basement
3. they have poor computing power, wait until they’re at least in their late teens (although software updates come too late and the system is usually very unstable at that time.)
4. think of the smell! your house will smell like a kindergarten
5. food costs are already high enough, add two or four growing kids to that budget and it’s far cheaper to run a couple Dell R610s every month.

overall, not worth it mate. good luck though!

this is what I’m talking about when it comes to the selfhosted communities.

if you don’t know how to properly segment and vlan your network, you have no business exposing your shit to the internet.