IF YOU HAVE EXPERTISE, THEN CONTRIBUTE, DAMMIT: https://developer.gimp.org/core/wgo/

They don’t need somebody to tell them their site sucks. They need somebody to HELP them make it better, to DO the work that you seem to be implying is very easy! They’re literally begging for it on their website.

200 people that aren’t contributing. They actually have a page on their site encouraging people to get involved in the site design: https://developer.gimp.org/core/wgo/

Ah yes, it’s a good thing that the only skill required to make a nice website is taking a screenshot

Contributing doesn’t happen on Lemmy lol

These projects are run by volunteers, they don’t have the unlimited budget for designers that Adobe does. And to be honest, it kinda seems like you’re just criticizing them for no good reason. Have you personally designed and built a website that doesn’t suck?

Sometimes these issues happen because of the IP range you’re using. If your local network and your remote network both use the 192.168.x.x range, then there can be conflicts and issues like this. This is a thing that happens generally with VPNs, not sure how Tailscale specifically functions with this issue.

Even if that’s not what’s going on here, you might try setting up your remote node as an exit node, and configuring your local node to route all traffic through it. Theoretically that shouldn’t be necessary, and it will also slow down your traffic if you’re routing EVERYTHING through Tailscale. But it could work in a pinch.

Actually, I’m looking at Tailscale documentation now and I see that they recommend setting up subnet routers instead of exit nodes in most cases. Maybe go that route instead, that makes more sense to me. That way you’re only routing necessary traffic through the remote node, rather than everything.