

deleted by creator


deleted by creator


kids set any other DNS, parents will never know
I mean, if you’re forcing them to use a specific DNS resolver I doubt they’ll have privileges to modify DNS on any computer.
On top of that, majority of kids don’t even know what a DNS even does.


Even the Chinese government struggles tracking people using VPN’s, Utah is in for a rude awakening.


How good is invidious?
The experience, at least in my case, has been the same. Invidious is very hit or miss due to YouTube’s methods of blocking connections, one day my instance will be working perfectly fine and the next will drop some obscure error. While my instance is technically public, it is only exposed to 1 country and even then hardly gets any hits off of my reverse proxy.
Thankfully they tend to update pretty frequently when YouTube starts acting up on a large scale.


So majority of distros you see are typically based off of another, as you’re already aware.
We have Debian based distros such as Linux Mint, Ubuntu, Kali Linux, PopOS and so on, then we have Arch based distros such as Arch Linux, Manjaro, EndeavourOS and so on, and then we got Fedora based distros such Fedora, Nobara, RisiOS.
You get the idea.
Now if Debian were to move a package from unstable to their stable repository all these derivatives will also pick it up however, they can prioritize their own packages from their own repositories over the ones supplied by Debian.
If you’re using Linux Mint cat /etc/apt/sources.list and also check out the files in /etc/apt/sources.list.d and you’ll see the repositories your system pulls from. You can add repo’s there if you want but you have to be cautious that the packages in the repo don’t conflict with the ones already installed, that means ensuring the versions are also supported on your distro.
I’m sure others can give more detail on Arch and Fedora based systems as I am not personally well familiar with those distros and how they store their sources files.
Just throw your services in a docker-compose.yml file, create a docker bridge network, and assign the:
networks:
- YourDockerNetwork
To the services in the yaml file, specify the ports it want’s to open with
ports:
- 8080:8080
And let it start up. If you want to get more complicated suggest reading the man page which really isn’t that long of a read.
Networking really cannot be simplified, you have to view it in a logistical way of how is Point A communicating with Point B which where Docker bridge networks come into play, they make the communication easy, if all your containers are all on the same docker network all you have to do is specify http://ContainerName:Port for them to communicate back and forth internally.


Yeah, would much rather a package designed for my distro than a flatpak.
I recall a time where the native package on my distro wasn’t working at all, I think this was when I was using discord and tried to use Vencord on Debian 12, so I tried the flatpak version and again it did not work. I was between a rock and a hard place, do I troubleshoot what is essentially a containerized/sandboxed application or try to figure out what’s going on my host machine.
I chose the latter and eventually got it working, but now I don’t use discord so waste of my time regardless.
It has been corrected. Apologies.
My bad, thought I could do it by memory.
It’s important to understand that many distro’s are usually based off of another.
We got Debian based distros such as Debian, Ubuntu, PopOS, KaliLinux, LinuxMint and so on, Arch based distros such as CachyOS, SteamOS, Arch and so on and Fedora based distros such as Fedora, Nobara, Bazzite.
Once you learn one of these base distros switching to another within its field is easy as majority of shell commands will be identical.


Hell that could just be the entry level position for all we know.
The other thing I tried was deploying an Element server so they could talk to family on their own without risk of exposure to the world at large, but ended up abandoning this.
Matrix is a PIA to configure properly, it is nice to have once you got it running but you’ll end up spinning like 8 different services (if you use Docker) for all the functionality to work.
Additionally, I recommend unbound for those already on pi-hole.
Never could get unbound to work properly, it would always knock my internet out to the point of troubleshooting for hours, whether that be Pi-Hole, OpenSense or Technitium I’ve always had issues with unbound.
As much as I like hosting my own services, I want them to be reliable.


Commercial software publishers will bend over backwards no matter what.
Selfhosting folk have it significantly easier and I’m sure a lot of people rely on small obscure websites.


I mean… What’s easier, implementing an unpopular APi into your already production ready service or blacklisting a country from making requests to your reverse proxy?
Personally I would choose the latter. Enough blowback from people will likely get this overturned.
EU has dumped similar legislation out however, they recently have had a poor streak in regards to legislation involving digital privacy.


Man I wish I spent time actually learning Proxmox, instead dumped everything into a headless Debian VM and called it a day.


deleted by creator


Oh yeah I’m aware, if people don’t want to use a VPN then I suggest this but give them the advisory warning.
Actually, recently I’ve been using a fork of IPAllowList which accepts DDNS addresses, but that usually is for more technical folk who would probably rather use a VPN then purchase a domain and associate it with their network.


Pangolin is based off of Traefik if I’m not mistaken, should be able to use Traefiks IPAllowlist middleware to blacklist all IP addresses and only whitelisting the known few, that way you can expose your application to the internet knowing you have that restriction in place for those who connect to your service.
Pulled directly from KDE Plasma’s Bigscreen website.
https://plasma-bigscreen.org/