If you set up resources correctly on his netbird network it effectively is a split tunnel. You don't have to route anything through it but his "file shares and stuff".

I have a rather gnarly nested double nat within my house where the homelab is isolated behind it's own separate firewall and have some limited resources on both. It's been perfectly serviceable.

I believe I have a resource of *.whathaveyou.net on the netbird gateway inside the network and no default route. If you do have that default route I believe you can have it as a separate resource and disable it.

Self-hosted netbird is pretty incredible to be honest.

I'm too Linux pilled and thought I was going to read an x11 hate blog. I guess Twitter sucks too, though.

There's no reason to use md5 if you don't care about security and only want speed. Non-cryptographic hashes are incredibly fast to calculate and there are far faster hashing algorithms if you want to go that route. Using md5 is a "I don't want to think hard" answer, and if you don't want to think hard, then you might as well be secure in your default answer.

The blame and mistake isn't honestly on git, but the rest of the tooling ecosystem. This wasn't a snap decision and the fact that nobody thought to get ready in the 6 god fucking years that this has been planned is the real problem.

This will be painful, but only because apparently nobody was willing to just start supporting it 5min before the deadline.

You've insufficiently described any technical reason to use git as the basis for your chat history. Git is a poor choice for all the reasons I explained in your last post and more. It's like using paint as glue or using a microwave to heat your bathwater.

While it might be technically possible and work on first glance, there are few to no technical advantages to doing so, and anyone could tell you as such. In fact in some cases it might even be a detriment.

In your posts, you're talking about the usage of Tor and how WebRTC is a bad fit compared to Git and I can only guess at how you reached the conclusions you did.

Literally just ask your AI why using Git as the basis for a secure encrypted messaging application is a bad idea and I'm sure it could do so more eloquent than I.

Like, my first thought is "why not use https or even TCP directly rather than Git" sqlite and a TCP socket is more sane than this.

I'm actually not against vibe coding, but this is the kind of stupid shit people point to when they say vibe coding is bad.

I'd guess they're talking about RHEL's server web UI of the same name.

It has nothing to do with AI, I see it as highlighting the irony in the "pull yourself up by the bootstraps"/grind set mentality. They're stuck in a situation where their options and capabilities are limited, and rather than suggesting something realistic or achievable they're being recommended things that are impossible to do while stranded at sea.

You could possibly make some "let them eat cake" type allegory as well.

I'm trying to understand where this rage and hatred is coming from. This isn't some canonical interchange format here.

It has little to do with time on first glance, at least to me I read the name as a gif manipulation library. If it were named jiffy or similar it might be slightly more reasonable.

Comments are as brittle as visual testing, perhaps even more so when you can stop referencing a class without tweaking the comment accidentally or otherwise.

Hasn't this been a thing for a long time? Personally I don't eat more than one "proper" meal a day unless I'm being physically active.

I think it's fine. I don't like cooking that much and it's less effort.