In my case the pattern appears to be some manner of DDoS botnet, probably not an AI scraper. The request origins are way too widespread and none of them resolve down to anything that’s obviously datacenters or any sort of commercial enterprise. It seems to be a horde of devices in consumer IP ranges that have probably be compromised by some malware package or another, and whoever is controlling it directed it at our site for some reason. It’s possible that some bad actor is using a similar malware/bot farm arrangement to scrape for AI training, but I’d doubt it. It doesn’t fit the pattern from that sort of thing from what I’ve seen.

Anyway, my script’s been playing automated whack-a-mole with their addresses and steadily filtering them all out, and I geoblocked the countries where the largest numbers of offenders were. (“This is a bad practice!” I hear the hue and cry from specific strains of bearded louts on the Internet. That says maybe, but I don’t ship to Brazil or Singapore or India, so I don’t particularly care. If someone insists on connecting through a VPN from one of those regions for some reason, that’s their own lookout.)

They seem to have more or less run out of compromised devices to throw at our server, so now I only see one such request every few minutes rather than hundreds per second. I shudder to think how long my firewall’s block list is by now.

I have and there’s nothing noteworthy, other than tons of other retailers selling the same thing of course.

It doesn’t quite work that way, since the URL is also the model number/SKU which comes from the manufacturer. I suppose I could write an alias for just that product but it would become rather confusing.

What I did experiment with was temporarily deleting the product altogether for a day or two. (We barely ever sell it. Maybe 1 or 2 units of it a year. This is no great loss in the name of science.) This causes our page to return a 404 when you try to request it. The bots blithely ignored this, and continued attempting to hammer that nonexistent page all the same. Puzzling.

Maybe, but I also carry literally hundreds of other products from that same brand including several that are basically identical with trivial differences, and they’re only picking on that one particular SKU.

They also need to be able to replenish that stock at current prices. I’ve worked retail many times in my life and arguably kinda-sorta do so now (albeit largely over the Internet) and I’ve never run any store where we did not set our pricing by replacement cost rather than original invoice cost. In my current operation there are some rare exceptions for clearance items and the like, but for the vast majority of products we sell for what it’s going to cost me to get the next one to put back on that shelf, not what it cost me for the one I’m selling you now.

I don’t have any insider insight into other companies’ operations, but I imagine a lot of other retailers work things the same way. Especially these days.

Negative. Our solution is completely home grown. All artisinal-like, from scratch. I can’t imagine I reveal anything anyone would care about much except product specs, and our inventory and pricing really doesn’t change very frequently.

Even so, you think someone bothering to run a botnet to hound our site would distribute page loads across all of our products, right? Not just one. It’s nonsensical.

I run an ecommerce site and lately they’ve latched onto one very specific product with attempts to hammer its page and any of those branching from it for no readily identifiable reason, at the rate of several hundred times every second. I found out pretty quickly, because suddenly our view stats for that page in particular rocketed into the millions.

I had to insert a little script to IP ban these fuckers, which kicks in if I see a malformed user agent string or if you try to hit this page specifically more than 100 times. Through this I discovered that the requests are coming from hundreds of thousands of individual random IP addresses, many of which are located in Singapore, Brazil, and India, and mostly resolve down into those owned by local ISPs and cell phone carriers.

Of course they ignore your robots.txt as well. This smells like some kind of botnet thing to me.

I’ve got a Timex Expedition that I’ve had since high school. That means I bought it some time during the early Triassic. Its stainless steel backplate is held on with four Phillips screws and I have never in many decades had any problems undoing them when I need to replace the battery every six years or so. It remains resolutely waterproof. I know this because it lives outside rather frequently: at the moment I have it stuck to the gauge cluster on one of my motorcycles with Velcro.

If your Q1 is anything like my previous X-Plus or current X-Max 3, pretty much all of the routines you can run from the touch screen are macros that are defined in your printer.cfg and gcode_macro.cfg files on the machine itself. These are just text files full of gcode and you can dick with it freely without having to reflash the firmware. The only “fun” part will be figuring out which one of the custom macros it is, since Qidi doesn’t always give them a readable name and they tend to make them random looking numeric strings. I’ll have to take a look at mine when I get home and ensure that the filament load/unload/runout routines are located there, but I’m pretty sure they are.

You can edit your config files through the Mainsail interface within the Qidi Slicer or you can SSH into the machine and get a terminal via which you can mess with things directly (username mks, password makerbase).

“All” digital tech?

I don’t think most people realize that any powertrain new enough to even have fuel injection is going to be a “computer vehicle” in some capacity. How are you with carburetors?

Windows 98 SE, maybe. We didn’t gain much traction there until about Win2k or XP.

Windows 98 in its original flavor didn’t even support USB mass storage devices out of the box without drivers. Hands up everyone who remembers having to carry around one of those tiny driver CDs that came in the box with every single Sandisk Cruzer for a couple of years? Yeah? How quickly we forget.

As already thoroughly explored in the apparent documentary “99 Red Balloons,” in 1984.

For fuck’s sake.

In terms of Windows 11? You can move the start button back to the lower left corner in the settings, but you can’t stick the taskbar itself to the sides or top of your monitor nor resize it like you could do in previous versions. Even Windows 95 supported all of the above.

The functionality is still there, mind you, and you can do it via registry hacks or third party tools. Microsoft just saw fit to remove the option for the user to do it themselves for some inexplicable reason.

I’ll bet I can make your left eye twitch.

Are you ready?

A “large” amount of information.

Bitch, my computer has 128 gigabytes of RAM. It’s a tiny god. The fact that I have as many as 100 cells copied to the clipboard (which is the threshold that triggers this stupid message, if you’ve ever wondered) is not even a rounding error. I’m sure this was marginally important in 1982 or whenever this was first coded into Excel, but today my computer could lose an entire megabyte of memory or maybe even ten down between the couch cushions and neither of us would notice.

There is still no setting to disable this dumbshit message.

The TLC NAND chips used in most commodity memory cards these days are only good for something like 1500 write cycles per cell before they are prone to wearing out and coming back with errors. The difference between a dedicated SSD and a dinky memory card is partially the amount of extra space reserved for relocating data as the memory cells wear out, of which a consumer MicroSD card typically has little (on expensive ones) or none (on cheap ones).

I’ve heard it said, or rather seen it written, that some TLC NAND can endure “up to” as many as 3000 write cycles, but everyone is cagey about the true number and most consumer grade card vendors are tight-lipped about what kind of chips are actually in their products. So in other words, if you’re just scarfing a cheap card off of Amazon or from Microcenter or whatever, don’t expect ironclad longevity.

The one thing with flash storage writes that’ll bite you and it’ll bite you fast is logging. Unix-like systems love to incessantly write little one line additions to oodles and oodles of log files all the time, and if you want to extend your poor overworked little SD card’s lifespan you can dabble in turning some of that stuff off, once you’re positive you don’t need it for troubleshooting.

There also exist high reliability cards sold for industrial embedded applications, which will use lower capacity SLC but be able to endure upwards of 100,000 write cycles (per the marketing literature, at least). Expect capacities to realistically top out at about 64 gigs and for a single unit at that capacity expect to pay north of $100 for the privilege. It may be more appealing to use an NVME SSD at that rate and connect it with USB adapter or a hat.

I do too, but I’d highly doubt it will. It’s well known that Meta sells every headset at a loss and funds the expenditure via revenue from their gargantuan advertising and spy network, specifically to squeeze out competitors and make it harder to enter the VR market as a newcomer. Zuck Zuck still thinks all the prime real estate in the metaverse is going to be his, because he only read the first half of Snow Crash.

Gabe is a rich man and I assume he and his company could take this approach as well if they wanted to, at least temporarily. But based on their pricing for their past hardware (particularly the Steam Deck), I predict they won’t.

Insufficient pedantry detected.

The PC platform is an extension of IBM’s Personal Computer architecture, which was not a description of what it was so much as it was literally the brand name. It’s long since been forgotten that this is now a shorthand, and the full name of the platform arguably ought to be PC Compatible. Unless you bought your machine from IBM, anyway, which these days would be quite the trick.

Being PC compatible was a big deal back when the original PC was also a big deal. Probably slightly less so now, since it’s the assumed default.

It should go without saying that the original IBM PC, model 5150, did not run Windows… Because Windows did not yet exist. It didn’t even necessarily run the then-nascent PC-DOS provided by Microsoft, because IBM also supported running CP/M and and UCSD Pascal on it.

The whole Windows-as-default thing didn’t happen until well after the appeal of the PC specification had escaped containment at IBM and x86 had handily taken over the desktop computing world.

A personal computer is basically anything you can stick on your desk (or lap) and doesn’t require hooking up to a mainframe to run. But a Personal Computer, capital P and C, implies an x86 compatible platform with architecture designed such that it is technically still capable of running all those decades old 8086 programs and operating systems. (Just, several orders of magnitude faster than their designers ever envisioned, and probably only by sticking your UEFI BIOS in legacy mode first.)

FYI, technically Meta/Facebook had already owned Oculus for something like five years before the original Quest came out. They just started getting really blatant about the branding shortly after that time, probably to acquiesce to Zuck Zuck and his huffing of his “metaverse” crack pipe increasingly frequently.

In that case who knows what it was. This is one of those rare instances where it’d be awesome to have a flame spectrometer.

That was never actually an official statement. It was an offhand comment by some staffer that didn’t carry any legal weight nor accurately describe the internal trajectory for Windows in any way. As much as we like to poke fun at it regardless.