Cheap AI Token Resellers: The Secret Ingredient Is Fraud

[Matt Lenhard] has an interesting writeup explaining exactly how fraudsters offer access to cutting-edge AI models at a tenth of the price. Perhaps unsurprisingly, the secret is to get tokens for free from anywhere they can and by any means necessary. Then wrap them in a pretty relay API, and sell access to it.

Relaying tokens is not by itself a shady practice. That distinction belongs to services that obtain tokens fraudulently, opening the door to selling them at rates far below market value. This practice is widespread and profitable, in part because the abuse is so hard to pin down and stop.

One source of tokens is free credits on new accounts. New accounts are spooled up as fast as possible, hammered until they’re empty, then it’s done all over again. Another method is to sign up as pay-after, possibly with a stolen card, and simply ensure the account has no valid payment method once the bill comes due. Or set up a temporary card, pay some minimum up front and consume as much as possible, then initiate a chargeback. It doesn’t matter if individually each of these doesn’t amount to much before they get flagged, because it’s being leveraged relentlessly on a massive scale by automated systems.

There are the shadier methods, too. Fraudsters don’t just target providers directly. Consumer software products with AI features get reverse-engineered, then the back ends hammered for all they are worth. Poorly-coded support chatbots can be highjacked into serving fraudsters’ traffic instead of just their own. It doesn’t actually matter where the tokens come from, after all. As long as the fraudsters are obtaining them for free (or at least below their costs) then it’s profit.

That last point is one [Matt] zeroes in on with advice on how to mitigate this abuse. He goes into detail in his writeup but what it comes down to is recognizing that it’s a numbers game. Fraudsters depend entirely on obtaining tokens for free, or nearly free. So just like using an AI to keep phone scammers tied up, anything that raises friction increases the fraudster’s costs, in turn encouraging them to find an easier target.

Reject Fluid Simulations, Return To Rheoscopic Fluid

Fluid simulations are one of the “killer apps” of high-performance computing, but if you can’t afford the performance, they can take a depressingly long time to run. Depending on your use case, as long as you keep the Reynold’s number in mind– or are just looking for a qualitative look at pretty flows–you might be able to get away with purely-practical simulations using rheoscopic fluid, as [Visual Thinker] demonstrates in a recent video.

The fluid, as you can guess from the name, lets you scope out rheos— that’s flow, for those of you didn’t take Greek. Making it is as simple as you could ask for: get some mica flakes, which are readily available to add ‘sparkle’ to cosmetics, and mix with water and a drop of soap. The soap isn’t always necessary, but depending on your mica it helps keep it in suspension and avoid clumping– [Visual Thinker] found it helped him a good deal. Being flat plates of reflective material, the mica flakes catch the light and sparkle beautifully– and since they align with the fluid shear, they show you exactly what’s going on in your ‘simulation’.

[Visual Thinker] isn’t starting with serious simulations; the first thing he tries is essentially a toy that lets him see fluid flow around a Benchy by sticking magnets in it and using it to move a cross-section of its hull though a thin layer of fluid sandwitched betwixt pieces of laser-cut acrylic. We don’t call it a toy to disparage it, though– we totally want one. [Visual] mentions the idea of a coffee table combining the concept with the kind of underslung mechanism we see in sand drawing tables, which sounds dangerously hypnotic. If any of you build one, please try and tear your eyes away long enough to let us know.

He has another beautiful piece that make the video worth watching: a wind-tunnel, again made of laser-cut acrylic and printed parts. With careful consideration of the scale and flow speeds, that one might actually prove useful– and even if it doesn’t, it’s pretty enough that it doesn’t really matter. Beauty has its own utility sometimes.

Most wind tunnels we see around here use actual wind, but rheoscopic fluid was invented for this sort of thing, even if it does make for pretty baubles.

Continue reading “Reject Fluid Simulations, Return To Rheoscopic Fluid”

Native SMB3 Client Brings Modern NAS Access To 20-Year-Old PowerPC Macs

As software updates cease for operating systems, they eventually begin to lose access to parts of the LAN and internet due to out of date encryption features, as well as the inability to handle file sharing protocols like SBM3, which is somewhat of a necessity if you have e.g. a NAS on the LAN. Such too was the case with [watermark_hd]’s 20-year old PowerPC Macs and their installations of OS X Tiger and Leopard.

Cue Aqualink, a native SMB3 client for these older OS X versions that uses [Ronnie Sahlberg]’s libsmb2 server/client library for SMB2 and SBM3. The source code can be found over on GitHub, along with a Japanese translation. By using a local WebDAV server Tiger’s built-in mount_webdav feature can be used to mount these remote volumes.

While you can often still use SMB1 even on modern Windows and Linux/BSD via Samba, allowing even retro systems like these PowerMacs to speak SMB3 is at least a great boost for network security, even if the aforementioned encryption shortcomings mean that you cannot quite run encrypted file shares yet.

Although OS X eventually began to adopt modern SMB versions, some of us may remember how incredibly buggy they were, to the point that us OS X users often had to fall back to CIFS (SMB 1.0), so this is another potential use for this Aqualink application.

AI Book Scanning: Just What Is A Rare Book?

One of the stories of the last few weeks has been that AI companies have been scanning books in very large numbers in order to train their models with content guaranteed to have been written before 2002, and thus AI free. It’s caused some outrage, because of the size of the operation, and because the scanning process is destructive. In particular the phrase being bandied around is that these are rare books, and it’s this phraseology I find problematic. I think it’s time to unpack why that is the case.

It’s Not Book Burning, Folks

Before I worked for Hackaday I had a long career in and around the publishing industry, mostly on the electronic side, but from time to time crossing paths with my colleagues in the world of paper-based publishing. I understand the appeal of a good book, I’ve spend a lot of my life among bibliophiles, and let’s just say I own a few books myself. In particular I understand the symbolism of destroying books, bringing to mind as it does the actions of repressive regimes. I have stood in Bebelplatz in Berlin where the photo of Nazi student organisation members burning the library of Magnus Hirschfeld’s institute was taken in 1933, and if you know me, you’ll have an idea why that’s close to home. But for all that, what the AI companies are doing is not the same thing.

In this case they’re destroying the books for two reasons. Firstly, as I remember from a previous employer in the publishing world, it’s much easier to digitise a stack of papers than it is a bound book. Thus I’m pretty sure that’s one reason they remove the binding before digitising the pages. Then secondly, as I understand it it’s a copyright issue. If they buy a book, digitise it, and destroy the physical copy, they can legitimately claim that only one copy of it exists, and they hope, sidestep copyright claims from publishers. Continue reading “AI Book Scanning: Just What Is A Rare Book?”

Artificial Intelligence As It Once Was

One day, people will look back at what we call Artificial Intelligence and laugh. We do the same thing today, as chat bots totally outstrip what the computer industry called AI up until pretty recently. This didn’t escape curators at the Internet Archive, apparently, and [Jason Scott] tells us about a recent collection, “Vintage Artificial Intelligence.”

These are old software titles that will run for you in emulated machines right in your browser, ranging from somewhere in the 1970s to the 1990s. There’s Eliza, of course. Actually, there are several copies of Eliza. Given how simple it was to write Eliza, it did a pretty good job. Then there are adventure games that are pretty conversational, Lisp, Prolog, which was going to spawn expert systems to replace us all, and Racter, which tried to write fiction.

There was even Alter Ego that was supposed to help you explore life decisions, maybe? There are a couple different versions of even a few versions of Conway’s Game of Life. We aren’t sure that’s ever really been AI, but perhaps it depends on your definition. We’re happy to see Sargon, the chess program, represented.

We didn’t see Hexapawn, which is a shame. We also didn’t see Parry (the paranoid counterpart to Eliza) or that elusive software we remember but can never find that built word chains from text called George.

We’ve written about Eliza before. If you want to experiment with Prolog and you like Pokémon, you’ll appreciate this tutorial.

Anatomy Of An SLA Resin Printing Disaster

When I got back into SLA resin printing recently, I knew that I’d inevitably have to deal with the agony of failed prints and of course resin spills. This moment eventually came, and I felt motivated to treat mistakes as teaching moments on aspects like how to properly prepare an SLA build plate in terms of angles and supports or how to deal with failed print aftermaths.

Before moving on to the disaster, I’d like to first start with a look at the resin print of the previous article, which contained a number of fairly small parts. These I had oriented and supported almost fully using the automatic methods provided by the ChituBox slicer software, and worked about 90% as I had hoped, while leaving plenty of room for improvement as well.

Overall, preparing an SLA build plate in the slicer isn’t quite the same as for an FDM printer, mostly due to one phrase that strikes fear in the heart of anyone who has ever done resin printing: “peeling forces”.

Continue reading “Anatomy Of An SLA Resin Printing Disaster”

Quest VR Headset Becomes Unlocked Hardware

The Quest virtual reality headset gets a fully unlocked bootloader thanks to the QuestStack tool, which automates a complex process of privilege escalation to provide stable, privileged access to the hardware. This solidly frees the headset from its existence as a device tied to Meta’s walled garden, although the tool only works on the Quest 1.

Image credit: notmastergamerok on Reddit

Not simple enough? No problem, there’s also a web version by [darknight1050] that makes the unlock process as simple as plug in headset, visit web page, receive unlocked bootloader.

The first-generation Quest headset is an older (released in 2019) piece of hardware that is still perfectly capable, although it has been surpassed by later models in terms of performance and optics.

It has also been essentially forgotten as far as parent company Meta is concerned, with no requirement for new content to be compatible with it, nor consideration in general given to the device for some time now.

Hardware that is no longer supported should be opened. The Oculus Go got an official unlocked OS build which was a positive thing, but the Go was also a pretty limited device. The Quest 1 — the ‘Oculus’ part of the name having been dropped around the time Facebook renamed itself to ‘Meta’ — is considerably more capable than the Go was. Now people can have privileged access to its hardware, which may help save some of them from junk piles while enabling folks to do as they please with the hardware they purchased.