+1 to this. My birds all have open cage doors and they mostly stay in their cage. That's where their food and water is, and they only come out of their cage to go into another one
I just don't understand why bot owners can't just run a complete windows 11 VM running Google Chrome complete with graphics acceleration.
You can probably run 50 of those simultaneously if you use memory page deduplication, and with a decent CPU+GPU you ought to be able to render 50 pages a second. That's 1 cent per thousand page loads on AWS. Damn cheap.
There are myriad providers competing to offer this, nicely packaged with all the accoutrements (IP rotation, location spoofing, language settings, prebuilt parsers, etc.) behind an easy to use API.
Honestly it is a very healthy competitive market with reasonably low switching costs which drives prices down. These circumstances make rolling your own a tough sell.
They do, but the fact that they have to do this means there are fewer bots because it's less economical to go to such lengths, compared to something much less complex (which is orders of magnitude cheaper).
I assume your concern with GPU passthrough is that each VM needs a whole GPU?
You can use GPU-PV to split your GPU between VM instances.
Then the main bottleneck becomes how thin you split out your VRAM.
Wouldn't virtualbox or vmware's paravirtual GPUs be a better fit for this use case? Unfortunately the offerings with qemu/libvirt still lag vmwares by a lot.
I mean you missed the minigame of preventing Chrome from signaling that it’s being programmatically (webdriver etc) driven and tipping your hand, but … yup?
In theory you could run hundreds of full-fat Chrome bots if you don't care about the ops mess, but keeping Windows images stable while Cloudflare and friends keep changing the fingerprinting game turns the cheap math into a maintenance job from hell. AWS VM signals are a big red flag, so you still eat CAPTCHAs and blocks even with a full browser stack. The page load number looks cheap.
With current LCD controllers but new drivers/firmware you could selectively refresh horizontal stripes of the screen at different rates if you wanted to.
I don't think you could divide vertically though.
Don't think anyone has done this yet. You could be the first.
I believe E-ink displays do this for faster updates for touch interactivity. Updatimg the whole display as the user writes on the touch screen would otherwise be too slow for Eink.
Anyone who has accidentally snapped the controller off a working LCD can tell you that the pixel capacitance keeps the colours approximately correct for about 10 seconds before it all becomes a murky shadowy mess...
So it makes sense you could cut the refresh time down to a second to save power...
Although one wonders if it's worth it when the backlight uses far more power than the control electronics...
> A 1Hz panel is almost, but not quite, on the level of an e-ink panel, which isn’t the prettiest to look at. LG’s panel also uses LED technology, the mainstream panel technology that’s being overtaken at the high end by OLED panels with essentially perfect contrast.
> Whilst cranking, an ICE car will drop to around 6 volts (then maximum power is extracted according to thevenim's theorem).
> That means all computers etc will work at 6v.
Not necessarily all of them. Plenty of stuff will drop out while cranking; hopefully not the computers that run the fuel injection and ignition, though.
Not a car engineer, but those motors can be pretty high A, so this could also just be a feature that helps the starter get as much power as it can while cranking.
The specs say no less than 6volts. In the real world when the temperature drops down to -70F or colder and batteries get old the voltage goes well below that: deal with it.
Manufacturers are now encrypting Canbus traffic, voluntarily on current and future models.
Buying or selling tools designed to break the law is already illegal - trivial or not. If a driver gets a DUI and possess a NOOP interlock, they are getting an additional charge, and get to help am investigation into the illicit device supply chain.
> Buying or selling tools designed to break the law is already illegal - trivial or not.
I'm curious how this will play out. The "John Deer" exemption from the DMCA comes to mind, not sure if it's strictly for farm equipment or still in effect.
You might be a functioning alcoholic, but when alcohol intoxication is so prevalent in your life it interferes with day to day routines activities, it absolutely meets the psychosocial definition of addiction, and likely points to a deeper one.
Every rural area I've ever worked in had a non trivial number of folks who would have 2-3 drinks at the bar/whatever on a Friday or a Saturday and drive home. It was not alcoholism, it was "I'm totally fine to drive, the law doesn't know my limits" etc.
On some level that's just the price of wanting to go out and not wanting to drop a bunch of cash on a taxi (assuming you can get one to come).
2-3 drinks on a Friday night when you're supposed to drive home is different. I'd also say "I can drink because the law is wrong" is also not exactly a neutral take.
- I believe the law is overly proscriptive / strict / wrong.
- I believe I won't get caught
It's no different to someone speeding because "It's clear conditions and I consider myself to be perfectly safe at this speed". Or skipping a stop sign "I can clearly see nothing is coming".
The LEA-vs-shift thread here kind of proves the point. Compilers are insanely good at that stuff now. Where they completely fall short is data layout. I had a message parser using `std::map<int, std::string>` for field lookup and the fix was just... a flat array indexed by tag number. No compiler is ever going to suggest that. Same deal with allocation. I spent a while messing with SIMD scanning and consteval tricks chasing latency, and the single biggest win turned out to be boring. Switched from per-message heap allocs to a pre-allocated buffer with `std::span` views into the original data. ~12 allocations per message down to zero. Compiler will optimize the hell out of your allocator code, it just won't tell you to stop calling it.
Agreed. It really requires an understanding of not just the software and computer it's running on, but the goal the combined system was meant to accomplish. Maybe some of us are starting to feed that sort of information into LLMs as part of spec-driven development, and maybe an LLM of tomorrow will be capable of noticing and exploiting such optimizations.
If you think compilers can't punch through abstractions, you haven't seen what whole-program optimization does to an overengineered stack when the programer gives it enough visibility. They still miss intent, so the game-specific hack can win.
And that launch country list is most likely the countries where cracked YouTube Premium is most common.
App piracy is huge by copying around modded APK's, and everyone's grandma is doing it.
reply