It's called secure boot and it's been around for over 10 years now.

OpenAI noticed that Generative Pre-trained Transformers get better when you make them bigger. GPT-1 had 120 million parameters. GPT-2 bumped it up to 1.5 billion. GPT-3 grew to 175 billion. Now we have models with over 300 billion.

To run, every generated word requires doing math with every parameter, which nowadays is a massive amount of work, running on the most power hungry top of the line chips.

There are efforts to make smaller models that are still effective, but we are still in the range of 7-30 billion to get anything useful out of them.

I always assumed that Poettering is an arse to people because of the hate he got for systemd. I imagine it's hard to see the best in people when there's a crowd of haters everywhere you go. Though I have no idea what he was like beforehand.

Maybe you should

Some googling suggests this is what Dropbox does when it doesn't like the owner or permissions of any files in the Dropbox folder. It is very weird though. I assume you have dropbox installed? It is syncing correctly? Running find /home/dullbananas/Dropbox/ ! -user 'dullbananas' will list any files in that folder that aren't owned by you.

Assuming your userid is 1000 (likely but not guaranteed), running the script should be harmless and stop the password prompt from appearing until there is another file permission issue. Check your user id with id -u 'dullbananas'.

They're still at it, they bought Campo Santo (Firewatch Devs) in 2018 and now their game In The Valley of Gods is never gonna happen, they worked on Alyx instead.

They poached a bunch of folks from Hopoo Games recently too.

Oh boy you're gonna love Seal https://github.com/JunkFood02/Seal

They should bring back the original https://www.youtube.com/watch?v=tPYbzfwIJRA

ZFS doesn't have fsck because it already does the equivalent during import, reads and scrubs. Since it's CoW and transaction based, it can rollback to a good state after power loss. So not only does it automatically check and fix things, it's less likely to have a problem from power loss in the first place. I've used it on a home NAS for 10 years, survived many power outages without a UPS. Of course things can go terribly wrong and you end up with an unrecoverable dataset, and a UPS isn't a bad idea for any computer if you want reliability.

Totally agree about mainline kernel inclusion, just makes everything easier and ZFS will always be a weird add-on in Linux.

My partner worked for a local council. They reset your password every 90 days which prevented you from logging in via the VPN remotely. To fix it you'd call IT and they'll demand you tell them your current password and new password so they can change it themselves on your behalf.

Even worse, requesting a work iphone meant filling out an IT support ticket. So that IT could set up your phone for you, the ticket demanded your work domain username and password, along with your personal apple account username and password.

Thank god we have crypto bros like Sigma G and Sina_21st to get the inside scoop on the Chinese rural bank loan crisis.

IPv6 isn't just larger addresses, it was meant to totally remove the need for layer 2 / MAC addresses, bus networks, DHCP, and broadcasts. Since the plan was to get rid of the 12 byte ethernet header, the 24 byte increase in IP addresses would only be a 12 byte increase in header at the end of the day. WiFi wouldn't need three MAC addresses in every packet. IPv6 only achieves it's true potential with a complete switch over.

I personally don't think that can ever happen. The opportunity to switch everyone over is absolutely long gone. IPv6 isn't an extension of v4 or a compatible replacement, like ASCII to UTF-8. It's more like X to Wayland. The protocol authors went "This is a mess we gotta rethink this from scratch". But there's so much already relying on the old protocol, and replacing it with something that doesn't perfectly match features is difficult for little reward for users.

The increase in IPv6 nodes has mostly been due to mobile networks. The tragedy is they actually still mostly use layer 2 and bridge networking. IPv4 nor v6 can handle maintaining connections while addresses change. So they set it up so that you keep the same IP address as you travel and move between different towers. This is done with massive virtual layer 2 LANs across towers, with the IP routing happening at a central datacentre. IPv6 is simply used for the larger addresses, and none of the network/protocol simplifications it promised can be used.