It’s because the outage went on for a very long time (over 24 hours to get Outlook operational again!) and more and more companies continue to migrate critical services to “the cloud” (someone else’s computer) because Microsoft convinced company leadership that it’s “more reliable” and that relying on a single vendor for everything is totally okay and can never go wrong.

So many companies don’t think about hot/warm spares or multi-vendor failover strategies any more because they outsource their thinking to Microsoft or Google. I’ve seen plenty of cases where companies were only able to recover from major issues because they had fully redundant backups or failovers at another vendor (one example - in this case they did it right, with multi-region redundancy on Google Cloud in addition to full backups on AWS - so they were able to recover from Google accidentally deleting all their data)

I suspect that institutional knowledge about dealing with Exchange’s quirks is slowly going away as older employees move to other teams, companies, or retire, and are replaced with younger people who think they can solve everything using AI.

Microsoft’s been dealing with email for a very long time, starting with Microsoft Mail in 1988 then Exchange in 1996. Most of the newer features are just bolted on to the older systems. There’s plenty of legacy cruft in Exchange server (similar to how Windows 11 still has bits from Windows 95 and even icons from Windows 3.0 in it) and that’s the same codebase they still use for Microsoft 365 email.

There’s already plans to ban social media for under 16s AFAIK

Not sure if that’ll apply to Lemmy or not, but I guess Lemmy servers could just geoblock visitors from regions that enforce this.

There’s definitely some negatives about data centers.

However, there’s also a lot of misinformation. All the data centers in the entire USA use less than 1/20 of the water consumed by golf courses, and modern designs use closed-loop water cooling rather than the older evaporative cooling. Evaporative cooling is the type that uses a lot of water.

I live in Silicon Valley, and most of the data centers here are in Santa Clara County. 65% of the water usage by data centers is recycled water.

There’s a lot of regular RAM in the servers too though, since the servers can’t operate entirely from VRAM.

deleted by creator

I agree that more supply would be great and building factories can pay off. It’s still very expensive though, and some banks are growing skeptical of the ballooning costs of AI-related projects.

tl;dr it’s a relatively sophisticated approach to make it look real. The fake site reverse proxies the real online ordering site so that it looks and behaves exactly like the real one, blocks some scripts like trackers or anything that’d redirect back to the real site, and swaps out the payment form for a fake one.

The payment details entered into the fake form go to a live operator that immediately tries to use the credit card elsewhere online. They get through 3-D Secure (where the bank requires verification of suspicious-looking online transactions) by asking the user to confirm the transaction, e.g. by providing an SMS confirmation code or confirming the transaction in their bank app.

If you didn’t see the incorrect domain name, I think this would be very hard to notice, since the site functions normally. Very different to a regular phishing page where the site looks out of place and is often full of broken links (since they don’t want you navigating away from the fake login page)

I bought a new Nokia E63 for AU$199 in 2009 (around US$160 at the time). I liked that phone! It had a QWERTY keyboard. Replaced it with a Samsung Galaxy S3 in 2013.

$100 or even $200 is likely not doable for a modern touchscreen phone, unfortunately.

and the reason manufacturers aren’t building many more factories is because they’re extremely expensive and there’s no guarantee the same demand will still exist in 5 or 10 years. What if the AI bubble bursts, the market is flooded with second-hand supply, and all the new factories aren’t needed?

Micron is building new factories in New York, and they expect the first factory there to be online by 2030 at a cost of $50 billion (which is more than their entire 2025 revenue).

There’s Dropbear SSH, which is the most common choice for a minimal SSH server and client, but even that is around 50,000 lines of code.

Technically they’re correct though, in a way. If every account has a password, the system isn’t vulnerable.

You’re also not vulnerable if you use two factor auth, because all 2FA modules require PAM, whereas this vulnerability only exists when PAM is disabled or not installed.

Not just rootless and read-only, but distroless/chiseled too. There’s no reason to have unneeded parts of an OS in your Docker containers. It should just be one app along with any libraries it needs (or just statically compile the app)

“passwordless” here means that the account doesn’t have a password. What the person you’re replying to means is that password authentication should be completely disabled in the SSH config, as that’s the only way to exploit this issue.

Wireguard and apps based on it (like Tailscale) don’t respond at all unless the data is signed with the key of a configured peer (or with Tailscale, a system on your tailnet that passes the ACL). It’s literally impossible for an outsider/attacker to detect with a port scan since it just ignores unauthenticated packets.

The Wireguard codebase is also extremely small. The core Wireguard implementation (the version in the Linux kernel) is around 5,000 lines long, so an experienced developer can read through all the code if they dedicate a day or two to it, and understand how it works.

For comparison, OpenVPN is around 70,000 lines of code and OpenSSH is around 150,000 lines of code. There’s a huge number of features in SSH!

Well… https://www.youtube.com/watch?v=vU1-uiUlHTo

ctOS from Watch Dogs was supposed to be a warning… It wasn’t supposed to become a real system.

How’s it a whoosh? I thought their question was genuine.

Different philosophies.

On Linux, you can delete a running application and it’s fine, because files aren’t actually deleted until the last process that has it open closes it. This applies for all files, not just executables.

Internally, files are mainly identified by an inode rather than the file path. If you delete a file then create a new one with the same name, the new file will have a different inode number to the old file. Anything that had the file open will still have a valid reference to the old file. If you’re running a program and upgrade it while it’s running, the currently running version will still be using the old inode, while any new instances will use the new one.

Windows doesn’t do that. On Windows, the file path is the main identifier for the file. Files that are in use and executables that are running are locked and can’t be modified. It tells you to restart so that it can swap in the new files after closing everything. When updating a program, you just need to close it to be able to update, but OS files need reboots because they’re locked the whole time the OS is running.

Note that some versions of Windows don’t require that any more. Some editions of Windows Server 2025 support hotpatching. This patches code (both OS code and program code) directly in memory, avoiding the need to restart to apply the update. On Linux, there’s a proprietary system called Kernelcare that does the same thing for kernel patches.

For Nginx on Debian, I need to figure out if just updating the libbrotli1 package is sufficient, or if libnginx-mod-http-brotli needs to be updated too. I suspect it’s dynamically linked (since that’s standard on Debian) and thus just updating the Brotli library and restarting Nginx is sufficient.