That’s just for a exit node. I explicitly stated that one should only let larger organizations run a node.
Also, my original comment still stands about no one being arrested
That’s just for a exit node. I explicitly stated that one should only let larger organizations run a node.
Also, my original comment still stands about no one being arrested
Exit relays are totally fine from a legal perspective. They key is making sure the ISP and local police are aware so they don’t come after you. ISPs have sent DMCA letters and such to operators when in reality they can’t and shouldn’t control the traffic coming out of Tor. The good news is that Tor has templates to respond.
Best practice is to let bigger organizations run exit relays so that there is the oversight from leadership.
Don’t run a Tor node in places that have censorship laws or problems with freedom. In places such as the US and most of Europe it should be totally fine to run a node. What the network really needs is more middle nodes. You can inform your ISP and the local police of what you are doing just to be sure.
The only time you could get into trouble is when you are running a exit node. ISPs and police have mistakenly classified out nodes as local traffic. It is recommended that only organizations such as universities run Tor exit nodes. However, it is important to keep in mind that to my knowledge no one has ever been arrested for running a exit node in a western country.
Email does take some serious bandwidth
On a more serious note, people who have fast Internet should be running Tor relays. It would make the network much faster and secure.
Obligatory https://files.catbox.moe/6bwk52.gif
Honestly there isn’t a lot of reason for 10G. Honestly 100M is probably fine for some people who are just browsing the web. The big think it latency as some of those old copper connections are very painful.
I would stick with 1G and be done with it
Plex doesn’t get updates 3 times a week
Again there docker image is just a packaging format and a health check. I very much wish it were better but for now it works
YOU CAN’T DO THAT
Yes, docker is the best way. Anything else is hell. It is still painful with docker but at least it is manageable
The images work fine for me. The problem is that Nextcloud is a complex app that doesn’t really work with the design of one container to do one job. It is pretty much a regular application that uses docker for packaging.
Why are your backups so out of date? Just setup daily snapshots and call it a day if it isn’t critical. You never want to update major versions first thing. Wait 3 months and then update.
This smells like shadow IT
The world is your oyster test env
One that lacks a good IT department apparently
Honestly it is fine assuming you don’t need 24/7 uptime. Just make a compose file and verify you have a working health check
Sounds like you are not using docker correctly.
That is a very bad idea. Use the stable tag instead. Better yet, create an Ansible playbook that updates the containers in bulk and then manually run it when you have time.
Seems easier to blame Nextcloud
You can’t update it in the web app. You need to do a docker-compose pull followed by docker-compose up -d
I disagree. I use and depend on the apps including things like calendar and talk.
I’m talking about docker compose