Skip Navigation

Posts
8
Comments
569
Joined
1 yr. ago

  • I just think the idea of your alternative being partially coded by the company you're attempting to avoid is a little stupid. I don't give a shit who he is. I barely give a shit who runs Mozilla.

    Brave and every other Chromium fork are at the mercy of Google to exist as an alternative to Google, which to me, defeats the point. Every bit of their effort would be better spent rolling their money over to donate to browser development rather than band-aids.

  • I've been dosing too much tux, doc. My mind's all FOSSY.

  • "Where's the fucking, list?"

    List: "I don't know! Stop yelling at me! Who are you!?"

  • It won't arrive, lets see,... tomorrow. Good! Just around the time I won't be expecting it.

  • *What aren't

  • If meat from foreign countries was vermin, it would cost way more than steak.

  • A lot of far right people are into whatever an influencer does because that's their news.

  • Anyone else like Tool? I use arch, btw.

  • Oh yeah. https://hub.docker.com/r/linuxserver/wireguard

    Basically, docker can and does create network devices. It's as easy for it to create wg0's as it is to create networks for your other docker containers. If you're going to run wireguard and docker, you're better off to let docker handle the network routing and just run one of the various containers out there to stop them from fighting. That particular container is more general. You can run it client or server. Wg-easy, I believe is server-only, or even hide it inside other containers like docker-qbittorrent-wireguard, where it just hangs out and connects to whatever .conf you give it.

    I did the whole thing in my early days selfhosting where I installed wireguard, docker, some apps, rebooted, everything breaks.

    Install a wireguard container, configure it as you would, your apps, reboot... it still works, because docker isn't conflicting with native wg-quick. It's either this, or untangle and make an iptables setup permanent so when you reboot, it doesn't break again.

  • adds a one to it

    next app...

     
        
    ports:
     - 8081:8081
    
      

    Ughhhhh

  • Double-pro. Running wireguard on docker assures that a native wireguard install won't conflict with docker. Keep those iptables in the same place.

  • Joke's on him, it's 100.99.99.99

  • I am overwhelmingly happy for both of you.

    I was raised Baptist. Don't recommend it.

  • Alternate reality foss religions were not on my imagination list this morning but there ya go

  • "Son, are those ads in my house!?"

    dad, please, it's only a little marketing!

    "NO SON OF MINE! GET MY BELT!"

    dad, no!

    "What's our DNS address!?"

    dad, I don't kno-

    "Count the licks, boy! I'll teach you the hard way!"

  • News Media: "ADVERTISERS CAN'T DISTRIBUTE ADS BECAUSE OF YOUUUUUU"

    g-good!

  • Depends. Using some no-name dns server in Uzbekistan is likely not going to be easily reachable for your queries by your local government, if at all.

    Then again, most of you don't have queries over encrypted protocols anyway, so it's an open book regardless of who your third-party is.

    Best case if you're a luddite, run a very highly recommended(by the fediverse) VPN, like windscribe or mullvad, and use their dns servers. Wireguard will encrypt the queries, and the vpn being supposedly trustworthy would put any cork in it otherwise.

  • Then change it?

  • You think most people open settings or hamburger menus? You're more optimistic than I am.

    These days the average caveman is used by his phone, not the other way around.