nobug-404

It’s just code…

If you’re using torrents you aren’t only downloading…

You could make a container for the VPN and have the torrents route through that. Instead of having the whole system go through the VPN. You can then also make the VPN a dependency of the torrent container to prevent it from leaking torrent traffic out of your standard internet connection.

I know there is a Spotify endpoint that you can run on a pi. And I did see a project to make one a Chromecast target. Bit that didn’t work for me.

Mass transit cannot be free.

It should however be without toll. It can quite reasonably be funded with tax.

But free? No. Someone somewhere has to pay for the infrastructure and operations.

The Elon simps in the replies…

In a real democracy you can run to be elected. And if enough people like your policies you will be able to enact them.

He isn’t US born.

That’s not how banks work.

The rules forbid asking for links mate.

AI is the solution to everything. Even AI.

I run a service on my computer called radarr. I have it set to not look for camera recordings.

I get unable to connect.

Well I wasn’t one of them. I canceled mine.

What?

The real engineering original is basically spot on.

Discord is terrible for being able to go back and see shared knowledge.

That’s elons model.

Those will not be UPSs they will be power banks. Most Powerbanks are lithium. Lithium requires careful monitoring if it is constantly float charged. And they fail catastrophically when over charged.

A reverse proxy is a service that takes incoming traffic on an IP address and port. It reads the URL the connection came into and passes it to the service it is configured for.

Example: A server runs Plex. There is a DNS entry plex.myhome.nework that points to the IP of that server. Nginx listens on port 80 and 443. If a client connects to port 80 using plex.myhome.network nginx will pass it to Plex. If it comes in on 443 nginx will still pass it to Plex but it will also provide the configured SSL cert to the client connecting to Plex.

If the server is also running jellyfin and DNS is setup for jellyfin.myhome.network with the same IP. The user connects to jellyfin.myhome.network on port 80 Nginx instead passes it to jellyfin.

So from our example you can see that we have both jellyfin and Plex using the same IP address and port 80.