I have experience with an IB school in Europe - the kids have a special unit about clocks (analog and digital) in their math class in fourth grade. The student books have a lot of problems involving reading both types of clocks and calculating diffenreces between two clocks in hours/minutes/seconds.
Is it just me or the graph at the end of the article is not really showing rising adoption in general. It basically shows a couple of spikes - each corresponding to some big company switching their edge servers to HTTP/3 like Alphabet, Meta, Cloudflare. There is no gradual increase.
Furthermore, I don't see easy solutions yet for some problems with QUIC - for example browsers still try to establish a TCP connection first unless they know for sure the server supports QUIC. Proxy support for HTTP/3 is still in its infancy, but for many corporate envuronments it is a hard requirement.
So outside of the biggest websites, which I admit also take up a large chunk of the network traffic, is QUIC really replacing TCP in the general Internet?
> for example browsers still try to establish a TCP connection first unless they know for sure the server supports QUIC
As you alluded to here, you can hint a networking implementation with QUIC supporting servers. This feels similar in practice to HSTS Preloading, most of the benefit of full HSTS comes from a small number O(100k? 1m?) of domains being pre-loaded as HSTS supporting, and that's just distributed with browsers now, a fairly straightforward solution. The same could probably be applied for QUIC.
> which I admit also take up a large chunk of the network traffic, is QUIC really replacing TCP in the general Internet?
I guess this depends on whether you're looking at aggregated traffic, or distinct traffic destinations. Neither of those is more important right! If YouTube/Netflix move to QUIC, that's a very significant amount of benefit for the internet and users. Equally if all wordpress sites on shared hosting disappeared because TCP was no longer supported, that would also be a very significant impact. I think the headline saying "QUIC is displacing TCP for speed" is very fair, but over-extrapolating from this would be going too far.
Some EVs use paddles behind the steering wheel to control recuperation. You can switch between several levels or use max regen while you hold one of the paddles. It gives a lot of control without touching the brake pedal.
I wouldn't want that kind of interface. I'd worry about it retraining my mind to think "Braking = pulling this paddle", and then one day I'll need to make an emergency stop, and I'll pull the paddle instead of hitting the foot brake and ram into whatever I wanted to avoid because the regen braking was insufficient.
I suppose the system could be designed to detect a user suddenly putting a death grip on the paddle brake and apply the foot brake automatically.
macOS uses certificate pinning for some .apple.com and .itunes.com sites. If you pass all your traffic through the proxy, some stuff like the app store will not work. Do you bypass the proxy for those or just let them fail?
You can also use a MITM proxy tool to intercept the JS files and modify their response body to remove or replace the `debugger;` statements with something else. Might require inspecting the JS files first to see what needs to be replaced exactly, but should not take more than a few minutes.
That will not pass integrity checks (the script inspecting its own code).
It will also not work if the script is some initially obfuscated string that is passed to eval() or something more complex assembling the actual code on the fly.
That will not pass integrity checks (the script inspecting its own code).
As us "old school crackers" would say, "NOP those out!"
As for obfuscation, you can unpack the scripts in order to do the needful, then use the proxy to "transparent redirect" requests for them to your own locally hosted unpacked and modded version.
>That will not pass integrity checks (the script inspecting its own code).
I've not seen anything like that. The integrity checks are generally limited to verifying the document location and the presence of certain elements in the DOM. Obfuscation techniques have become so sophisticated that integrity checks are not really necessary. Bot challenges (such as the one used by CloudFlare) may go so far as to test graphic elements like the canvas to ensure that the JS is actually running in a browser but I don't think this is a common thing for the average website that just wants to keep bots from scraping them.
This assumes that the script contains the word "debugger" in clear text, however it may not. It may decrypt or descramble a string and then eval() it. Your approach wouldn't catch that.
> If you install Windows, apparently Microsoft doesn't allow you to get updates (on W11) because of the Deck's lack of a "TPM".
I have installed Win 11 on my Deck because Easy Anti-Cheat does not work with Proton yet and have no issues with updates. The latest firmware (BIOS) seems to work fine for Win 11 requirements and I receive updates for Windows as well as new drivers from Windows Update.
Older Lego trains use IR for control so if you just want to control motors and lights, you can get one of those and control it with the IR blaster on the Flipper. If you also want the sensors/newer programmable hub, then you need the BLE protocol.
You should add basic rate limiting to your app. We had a similar issue with Stripe and making sure that different card numbers could not be quickly used one after the other by the same account fixed the problem.
reply