all 11 comments

sorted by: hot top controversial new old
[–] 1 point 10 hours ago

How about a client that isn't bloated and constantly being updated.

  • source
  • [–] 18 points 1 day ago* (1 child)

    Opens .gitignore

    ignored/
    tailscale/
    .vscode/
    .claude/
    logs/
    

    Not all vibe coded projects are worth being skeptical of but an extremely ambitious, CRUCIAL component of the web stack should be vetted and questioned when there are signs of vibe coding…. Especially when it is being ghost-written by claude code.

  • source
  • hideshow 1 child comment
  • [–] 4 points 23 hours ago (4 children)
  • [–] 1 point 12 hours ago

    When I was going for a selfhosted mesh tunnel solution this year, I originally steered toward Netbird given that Tailscale (the client) is rather obtuse to connect with alternate control servers.

    I don't actively use Netbird, but rather did go with Headscale in the end. If you're satisfied with and your requirements for Netbird don't include anything that deviates from their setup scripts, I'd imagine your deployment would go fine. My requirements and my strong desire to have everything relevant in my selhost deployments be fully to mostly declarative, and be trackable via git had me finding out how incompatible Netbird is for me. I don't think I have seen an app more averse to being deployed declaratively, which as it turns out is likely the reason their deployment scripts exist in the first place.

    The there's the (at the time at least) really confusing and contradictory documentation that describe two different generations of potential deployment of the software. Good documentation is half of what makes software deployments maintainable, and Netbird had (and might still have) outright misleading documentation that will have you looping in circles attempting to figure out reasonably standard functionality like using external oidc for accounts.

  • source
  • parent
  • [–] 4 points 22 hours ago (1 child)

    It's nice to have alternatives but I don't understand why we can't have a fully FOSS implementation of overlay networking without needing a company trying to up-sell us to premium features. I don't like to rely on companies to maintain a product that's a critical part of my infrastructure.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 21 hours ago

    I've been using netbird for couple of months now.

    The good:

    • I was able to do everything using the free version (exit node, DNS)
    • in theory you can self-host it (haven't tried)
    • it has an Android client app in f-droid
    • stable, everything works really nice

    The bad:

    • it eats up a lot of battery on Android. There's a bug open for it for months now. After playing around with some settings I got it to the point where the battery usage goes up on mobile data only. Once I'm back to WiFi it's ok. I have deployed netmaker locally and testing it is on my to do list but as things are now I can go through the day without issues with netbird and I'm kind of hoping they will fix it before I'll have the time to test netmaker

    Netmaker was easy to setup locally but I don't know if it can fully replace netbird.

    I tried headscale and it wasn't easy to set up. From what I read tailscale apps treat self-hosted solutions as an afterthought so it's not as easy to set up. I would be worried they will drop it and force you to use their servers at some point. Netbird at least is marketed as a self-hosted solution.

  • source
  • parent
  • [–] 2 points 21 hours ago (1 child)
  • [–] 4 points 1 day ago* (last edited 1 day ago)

    Headscale is a good fit for individuals wanting to manage a work from anywhere private network and monitor via a GUI. Also I suspect for businesses wanting to avoid Tailscale's increased prices. Works fine with the regular tailscale client as well. It's all doable in docker containers for security. Does Saml identity etc so you can do the auth via an identity provider. Probably more secure than Tailscale's backend given their size and recent embrace of AI integration

  • source