There's also changing from circuit to packet switching, which also drastically changes how the handover process works.

tl;Dr - handover in 5G is buggy and barely works. The whole thing of switching from one service area to another in the middle of a call is held together by hopes and dreams.

systemd tries to unify a Wild West situation where everyone, their crazy uncle, and their shotgun-dual-wielding Grandma has a different set of boot-time scripts. Instead of custom 200-line shell scripts now you have a standard simple syntax that takes 5 minutes to learn.

Downside is now certain complicated stuff that was 1 line need multiple files worth of workarounds to work. Additionally, any custom scripts need to be rewritten as a systemd service (assuming you don't use the compat mode).

People are angry that it's not the same as before and they need to rewrite any custom tweaks they have. It's like learning to drive manual for years, wonder why the heck there is a need for auto, then realizing nobody is producing manual cars anymore.

According to this post, the person involved exposed a different name at one point.

https://boehs.org/node/everything-i-know-about-the-xz-backdoor

Cheong is not a Pingyin name. It uses Romanization instead. Assuming that this isn't a false trail (unlikely, why would you expose a fake name once instead of using it all the time?) that cuts out China (Mainland) and Singapore which use the Pingyin system. Or somebody has a time machine and grabbed this guy before 1956.

Likely sources of the name would be a country/Chinese administrative zone that uses Chinese and Romanization. Which gives us Taiwan, Macau, or Hong Kong, all of which are in GMT+8. Note that two of these are technically under PRC control.

Realistically I feel this is just a rogue attacker instead of a nation state. The probability of China 1. Hiring someone from these specific regions 2. Exposing a non-pinying full name once on purpose is extremely low. Why bother with this when you have plenty of graduates from Tsinghua in Beijing? Especially after so many people desperate for jobs after COVID.

It was always there, but we've long ignored the warnings. It invented the Internet, which we took for granted. It wasn't until Gore seeped through a series of tubes that we realized, but by then it was too late.

It had already taken over the windmills.

Pretty sure emergency mobile broadcasts are included (at least by gov agencies) but you know what happens with these things that are only used for emergencies:

"It's annoying can't I turn it off?"

That's why I still think the more methods the better. It's probably one of the few reasons I'm okay with being bombarded with messages (not in jp, but literally got 2 earthquake warnings yesterday).

I think we may be looking at these wrong. Yes there's a visible throughput/latency improvement here but what about other factors? Power savings? Cache efficiency? CPU cycles saved for other co-running processes?

These are going to be pretty hard to measure without an x86_64 simulator. So I don't fault them for not including such benches. But there might be more to the story here.

Uh oh. I used to work University IT. I can only imagine the number of tickets this would generate:

"Bad wifi at XYZ hall"

"Request to setup private router in dorms due to bad wifi"

"Please fix my computer I've heard this patch breaks wifi" (meanwhile, the reporter never installed said patch)

*Gasp* the registration is coming from inside the colo!

You don't understand. It's not like the self-driving feature is just software where they can price it at whatever they want. It's physically consuming brain cells every month. And those aren't free you know!

::: spoiler Do I really need a \s tag for this or does this tin foil hat make me look fat? :::

Because the horses are coming. And they are ANGRY.

The only way to survive is to win three rounds of trivia nights on various horse topics. So quit horsing around!

Make sure to test your setup if you are using DAV. Large files can fail if your nextcloud setup is done incorrectly.

Source: idiot who misconfigured PHP that resulted in a DAV client stuck in a retry loop, then getting banned by my own firewall for DoS.

Isn't the whole point of these things the "bloated" (CI/CD, issue tracker, merge requests, mirroring, etc) part? Otherwise we'd all be using bare git repos over ssh (which works great btw!)

It's like complaining about IDE bloat while not using a text editor. Or complaining there's too many knives in a knife set instead of buying just the chef knife.