“mostly solve the write hole problem” 😬

You do you, but I wouldn’t trust my data to that.

Don’t use the RAID56 functionality of BTRFS, the official docs still list it as unstable. Apart from that it’s pretty good.

You’re welcome, great to see how you’re taking all the comments on board!

There are more subtle problems with NAT as well. Say that PC-A opens a connection from port 1234 (to something on the internet), and PC-B opens a connection from port 1234 too. Now the router has to translate the PC-B connection to coming from port 1235 to distinguish them from each other. But if PC-C then wants to open a listening port on 1235 it won’t work because the port is already in use, even though you can’t see anything using that port!

NAT is full of ridiculous corner cases like that, which normal users aren’t very likely to notice. But once you start self-hosting things or trying to get something like older multiplayer games working the problems pile up fast if you’re unlucky.

Yeah multiple NAT is a lot worse, but normal NAT has a lot of corner cases too that most people just don’t run into that often. For example if two computers behind NAT want to listen on the same port, that just doesn’t work.

NAT is a “good enough” solution that tricked a whole generation of people growing up with it into thinking it’s a good thing. While in reality the best case is that you don’t run into issues and the worst case is that performance is horrible and you can’t do the things you want to do. The only people that benefit from it are lazy ISPs, not their users.

NAT is not a firewall and it’s not that great for privacy either, it’s not hard to fingerprint individual devices behind NAT. There are zero cases where NAT is better than the alternatives, except when you’re out of public IP’s, which isn’t an issue with IPv6.

So you’re much better off by not trying to reinvent the wheel and using IPv6 the way it was intended. Use privacy extensions for privacy. Use proper firewall rules for security. Revel in the fact that NAT isn’t fucking up your inbound connections. Do not under any circumstances force the horrible kludge that is NAT into your IPv6 network.

Are you kidding me? Go was developed by Google, and they’re using Rust more and more as it gives them measurable security benefits. The Linux kernel is also slowly including Rust. So I have no idea what industry you’re talking about but it certainly isn’t the IT industry.

Watched the trailer expecting it to be bad in a fun way but ended up bewildered how even the trailer looks this terrible.

Many modern programming languages like Rust and Go and Zig compile statically anyway, so don’t use any libraries. The whole “my distro supplies my libraries” model has been steadily losing relevance for years now. Flatpaks are just one more example of this.

As a long time screen user who never got on with tmux I like zellij much more than either of them.

You can. There are simple options, that only recognise predefined sentences, that even work on a Raspberry Pi, and at the other end of the spectrum you can host an LLM locally and chat with that if you have the right hardware (Coral isn’t powerful enough for that, you want a GPU with lots of VRAM). Obviously setting this up is more complicated, but there are a lot of options to do it your way.

Depends on which one you have. If you buy their own smart speaker (Voice PE), which is designed to stay entirely local if you have the right hardware and software locally, and even has a hardware switch to temporarily disable the microphone, it’s pretty easy. And of you don’t have all that locally you need a paid subscription to use their cloud a little bit, but they won’t store anything. So still pretty easy.

Absolutely possible if you keep the network setup simple. However, I run different sets of containers as different users, some of which also use services from the host itself (such as a PostgreSQL instance), and things quickly become more complex in these situations. The examples on the github helped me a lot to realise everything I wanted.

If you want to use caddy as proxy for other containers running as quadlets have a look at this repo: https://github.com/eriksjolund/podman-caddy-socket-activation

It certainly demystified some network shenanigans for me.

The books are over a century old so while I didn’t click with them either it’s easy to set why they’re not up to modern standards.

The movie bombing had many more reasons. Disney got a new CEO while it was being made who didn’t believe in it, so it basically got no marketing at all. It also demanded script changes during filming, which is why the character of Dejah Thoris alternates between powerful woman and damsel in distress throughout the movie. And there was a dispute over what the movie should be called. IMHO John Carter is the worst title they could have gone for, my personal favourite would have been Barsoom.

But yeah, for everyone who missed it it is definitely worth a watch, it’s a contender for the most expensive and beautifully made B-movie of all time.

I usually tell people running MySQL that they would probably be better off using a NoSQL key-value store, SQLite, or PostgreSQL, in that order. Most people using MySQL don’t actually need an RDBMS. MySQL occupies this weird niche of being optimised for mostly reads, not a lot of concurrency and cosplaying as a proper database while being incompatible with SQL standards.

Yes and no. It came at a time when TV makers weren’t allowed to assume their viewers would watch every episode, in the right order. So while it does have a big overarching story, half the episodes are stupid filler episodes so people wouldn’t fall too far behind it they missed one or two. If it were made a couple of years later they could have gone hard in every episode.

Pretty sure you can unblock per device in Adguard, so maybe block it first then unblock from the logs for the clients you want to allow?

Hearts of Darkness is the most insane documentary I’ve ever watched, would recommend.

It’s true, we should all love fossilesque.

What kind of AI written nonsense is this. No sources to back up their claims. Made up percentages that seem way too specific. Obviously bad IoT devices can do bad things but claims like these require something to back them up.