• 0 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: February 8th, 2025

help-circle







  • 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.