swinglock

Wire transfer is better?

If it takes seconds to compile it then the browser wins. The PoW only runs for seconds already.

"Sorry, this item's currently unavailable in your location."

Can you not design a PoW that is most efficient in a browser? Don't brute force hashes like Hashcash/Bitcoin, do something similar to RandomX instead but in JS. Browsers ought to run the fastest JS interpreters already so if interpreting JS becomes the bulk of the work, that attack might not work. Maybe even involve the DOM or whatever else makes sense.

It was more interesting when there were real tangible improvements. Game graphics has been like smartphones for a good long time now. Performance and feel (low latency and high consistency) still matters though, that is not solved, but it's also never marketed. Quality is not included with a UE license.

Windows does memory compression too.

I don't think it has overcommit at all, at least that's the default. That would be why you don't have Windows OOM killer stories.

Steam Support can probably get it sorted.

AF_ALG does ring a bell.

Neither was NixOS.

https://discourse.nixos.org/t/is-nixos-affected-by-copy-fail...

Because it's there.

Something breaking after 49.7 days is a classic. Someone counted milliseconds since start with a 32 bit unsigned int and some code assumed it couldn't wrap.

There are self-hosted options too. I can't vouch for any of them but many look competent.

Win32 and Wine being a lightweight alternative to HTML and Electrum is a fun idea.

This is why I used ReadItLater and now Instapaper. It's integrated in my ebook reader too.

Most users have JS enabled nowadays. Much of the web doesn't work without it. It was just an example.

No it does not. I've had this happen in legacy systems myself. The checksums of TCP/IP are weak and will let random errors through to L7 if there are enough of them. It's not even CRC and you must bring your own verification if it's critical for your application that the data is correct. TLS does that and more, protecting not only against random corruption but also active attackers. The checks you get for free are to be seen only as an optimization, letting most but not all errors be discarded quick and easy. Just use TLS.

Men in the middle including predatory ISPs can not only spy but also enrich. Injecting JavaScript and embedding ads is the best case scenario. You don't want that.

In addition even without bad actors TLS will prevent random corruption due to flaky infrastructure from breaking the page and even caching those broken assets, preventing a reload from fixing it. TCP/IP alone doesn't sufficiently prevent this.

IPv6 and CGNAT growth has finally started to suppress IPv4 prices. There was a huge pump when hyperscalers decided they needed more. But IPv6 keeps growing and is the majority of traffic in many networks. If you own significantly more IPv4 addresses today than you need, I would dump them on the market yesterday. Spend some of the profits to move to IPv6 if still needed.

Well but then attackers just compile a kernel with a rootkit that hides the hack and itself from the APIs of the BPF program, so it has to deal with that too or it's trivially bypassed.

Anticheat and antivirus are two similar but different games. It's very complicated.

assert() is always only compiled if NDEBUG is not defined. I hope DEBUGASSERT is just that too because it really sounds like it, even more so than assert does.

But regardless of whether the assert is compiled or not, its presence strongly signals that "in a C program strcpy should only be used when we have full control of both" is true for this new function as well.

I'm surprised curlx_strcopy doesn't return success. Sure you could check if dest[0] != '/0' if you care to, but that's not only clumsy to write but also error prone, and so checking for success is not encouraged.

The latest DLSS and FSR are good actually. Maybe XeSS too.

This used to be a feature to protect spinning hard drives. Why this would exist today and why it would throttle anything is bizarre.

In mobile networks it's usually a single device.

You should block the whole /64, at least. It's often a single host. It's often but not always a single host, that's standardized.

It's working. It will not be settled.

There were too many apps; all they wanted was the phone app, but it doesn’t default to the keypad, which was too much for them to find.

Then why buy an iPhone? There are phones designed for seniors that do just that. You don't need to pay 10-30x more for functionality you don't need and can't understand. Buy a Doro if you just want to call.

They previously renamed Remote Desktop to Windows App.

Though it's rich coming from a kernel lacking a better filesystem of its own.