Larger sites cater towards scriptless web for accessibility requirements.
Smaller sites don’t need SPA, so will most likely work to some degree.
The better (not necessarily bigger) blog systems will use scripting for fancy things, but will have fallbacks and will still work.

It’s the middle tier web-app (and sites that want to be a web app but have no reason to be) that will run SPA without any fallback. You know, the ones that want to send notifications and know your location and all that fun stuff.

Yikes, that’s rough!

Are you 100% sure it was a form from a bank?
Everything stinks of a scammers phishing form, leading to scammer calls.

I expect the only time a bank is going to want your phone number is when you initially sign up with them. After that, they should know who you are and your contact details.

I almost got caught out by a “sorry we missed you” delivery message, until it was asking for my date of birth.
Some of these random emails and SMS can catch you off-guard and seem legit

You can do reverse proxy on the VPS and use SNI routing (because the requested domain is in clear text over HTTPS), then use Proxy Protocol to attach the real source IP to the TCP packets.
This way, you don’t have to terminate HTTPS on the VPS, and you can load balance between a couple wireguard peers so you have redundancy (or direct them to different reverse proxies or whatever).
On your home servers, you will need an additional frontend(s) that accepts Proxy Protocol from the VPS (as Proxy Protocol packets aren’t standard HTTP/S packets, so standard HTTPS reverse proxies will drop them as unknown/broken/etc).
This way, your home reverse proxy knows the original IP and can attach it to the decrypted http requests as x-forward-for. Or you can do ACLs based on original client IP. Or whatever.

I haven’t found a way to get a firewall that pays attention to Proxy Protocol TCP headers, but I haven’t found that to really be an issue. I don’t really have a use case

USB-C is also ridiculously future proof and flexible, because it’s just a connector.
We are already doing 200w power and 40gbps data transfer rates, using various standards.

Now, standardising on a standard would be neat. But that isn’t going to happen

Tests is the industry name for the automated paging when production breaks

I thought OpenWRT doesn’t support modems due to licencing issues.
So, I guess you would need a separate modem, or ISP router in bridge mode, or double NAT with OpenWRT being DMZ

DRM = Direct Render Manager

I had no idea, was confused, and the article never de-acronyms/initialisms the term

Starting with a pool of all users who use alternative DNS for any reason, users of pirate sites – especially sites broadcasting the matches in question – were isolated from the rest. Users of both VPNs and third-party DNS were further excluded from the group since DNS blocking is ineffective against VPNs.

Proust found that the number of users likely to be affected by DNS blocking at Google, Cloudflare, and Cisco, amounts to 0.084% of the total population of French Internet users. Citing a recent survey, which found that only 2% of those who face blocks simply give up and don’t find other means of circumvention, he reached an interesting conclusion.

“2% of 0.084% is 0.00168% of Internet users! In absolute terms, that would represent a small group of around 800 people across France!”

I wonder how much the court case cost, and if those costs are in anyway likely to be recouped even if all 800 of those convert to a subscription.

I believe PCIe 4.0 wasnt that useful for big server farms, because network cards were already at 400gbps. Even at 100gbps networking, that’s only 2 ports.
PCIe 5.0 is only 1 port of 400gbps.
So PCIe 6.0 is the next actually big step for a lot of servers, so you can finally get dual 400gbps ports on 1 card

Oh, no kidding.
I always thought immutable required the declarative installs.
I guess, immutable is more “containerised userland”?

Yeh, immutable distros… You can install software, it’s just you have to declaratively define what software you want, then apply that as a patch.
You don’t just apt install cowsay, you have to create a file that defines the installation of cowsay.
This way, if you have to change how cowsay is installed, you tweak that patch file and reapply it.
If you have to wipe & reinstall (or get a new computer or whatever) you just apply all your patches, and the system is the same again.

Ah, yes good point

But it is a fixed ratio.
If it was in pounds, metric tons, moles or atomic mass units… It doesn’t change the ratio, the actual number.

Would it be acceptable to drop the unit all together?
“Lethal dose is 0.000000012 : 1 (substance : bodyweight)” (I made up the number).
I’m not sure if there is a better way of writing the ratio.

Could a fraction be more applicable?
“lethal dose is 1/600000 of bodyweight”

I’m sure it’s written as ng/kg to show the base units are the same, and the rest is just “fiddling” scientific notation

It’s the SATA cable

When learning c++ you hate c++. Then suddenly you get it, and love c++. Then you learn more c++, and you end up merely liking c++

Oh man, spoilable items? Spoilable agriculture research packs?
That’s pretty intense

Hard to justify you’re job when all you do is manage a team that does non-visible minor tweaks and improvements that affects like 3% of the user base.
Maintenance isn’t constant growth, gotta redesign.

If netflix are embracing new technology (maybe something that allows 1080p playback on any browser, instead of just chrome) and the changes required are significant enough, then a redesign incorporating the big lessons learned from the current design make sense.

I’m guessing they don’t understand scientific notation, and “numbers are close” without understanding the numbers are much more significant

Browser history was implemented before companies massively abused privacy.
It was an honest feature for users.
We also learned a lot about security regarding password/credential extraction from browsers.

Windows Recall might be an honest feature. It might be super secure and really useful.
But Microsoft doesn’t have the trust to pull this off