My router is just a Protectli Vault mini PC with Alpine Linux. You can essentially pick your favorite Linux (or BSD) distro and make it a router.

They’re similar but mainly Tailscale arranges WireGuard tunnels between peers. There are tons of useful features around that functionality like being able to route specific traffic through specific hosts (“nodes” using “app connectors”); it’s even better at finding a way out of hostile networks using relays.

Just as an example I typically use my VPS as an “exit node” so that all my traffic routes through it (which does a ton of tunnel hopping through commercial VPNs) while my wife isn’t into that at all, but both of us have Tailscale on our devices so when either of us accesses Home Assistant it’s routed directly to the host hosting it.

I used to just use a script with cron to update Cloudflare DNS records but these days I don’t screw around with exposing anything to the public internet directly, I just use Tailscale.

Why is this always the go-to answer? I kind of wish we’d stop asking it must sync to the clearnet.

Honestly if Lemmy (and other services) were built from the ground up for anonymous overlay networks rather than clearnet in the first place it would be a better place overall.

Web developers (or rather those that pay them) will do literally anything but stop spying; fucking trolls. It’s disgusting how greedy people are.

(Disclaimer: I’m a professional web developer myself but thankfully not in the realm of unethical spyware shit like this.)

Yeah the scale is crazy confusing.

Share of people who gave a response between 1-4 on a 1-10 scale to the question: “Please tell me whether you think homosexuality can always be justified, never be justified, or something in between.”

“Share” would imply it’s the percentage of respondents to the survey no?

Even worse, don’t use the suggested Samba, NFS without a tunnel either! You should probably have the default ports blocked at the router.

Surprised no one just said Samba or NFS over a tunnel (Tailscale, WireGuard, etc).

Or by “sharing” do you mean keeping files synced between the two for replication?

I’m mostly into it for the strong typing, self-documenting nature of it. In my own GraphQL APIs I’ve done a pretty great job of avoiding common pitfalls.

I’m a Ruby on Rails developer currently developing a service that’s basically ripped out of another Ruby on Rails app and the legacy data is just crazy bad — a lot of it has to do with poor validation but it’s understandably easy to get to that point in a dynamic language like Ruby if you’re not careful.

I also manage a REST JSON:API and it’s just so bulky and horrible to deal with. The tooling is barely there and it’s way overly complicated compared to GraphQL — the concept of “only query what you need” is fantastic.

I’ve been blocking Facebook for years but I have to say as a developer I’m absolutely in love with GraphQL. I really can’t stand having to continue development on REST APIs (though I’m equally obsessed with Conditional GET Requests as of late).

!crossview@lemmy.world

This reminds me of a legacy Rails 3.2 app that used a fork of the official Ruby on Rails only for one commit that backported some one-liner bug fix. This was at an old job in the Rails 6 days, getting it on the latest official version was definitely an adventure (no unit tests + tons of spaghetti code + a dash of currency conversions stored as Postgres floats).

I’m on Linux and I was going to shit all over Windows but realized I could use this on a few servers that I fuck with and constantly break.

If it’s cable internet you might just be constrained by the available upload speed. I tend to put my media in Storj then run a VPS somewhere between all the clients that serves the media via WebDAV with rclone. This gets around the slow upload speed of cable internet at home, and I can cache the remote content on my NAS at home too.

Yep, as a web developer I hate this too. C’mon now, how hard is it to get this right?

As a web developer this grinds my gears. It’s dead easy to fix this.

deleted by creator

deleted by creator

deleted by creator