Personally, better way to phrase might be "Does anybody you've actually met, visually viewed, use OpenClaw? Can you verify them using the software nearby?"
In a few years, it's become so easy to falsify articles, falsify comments, falsify images, difficult to really even trust responses online anyways. As far back as 2016, Microsoft already had bots deployed online that could respond 96,000 times [1] in 16 hours all over social media. Remember Tay? [1][2]
When you have insane amounts of capital and your gpu and talent needs are more or less met, there is a capital relief valve known as growth hacking. It only works if the consumer isn’t aware they’re being hacked.
No. They want you to believe in the hype and that LLMs are the death of programmers and limitless. OpenClaw and other such agents are sold as a tool that "can do anything" but behind the scenes, the implication is still that big LLM is driving it. So both are conflated.
Funny on this type of article linking to Google Patents. Such great possibilities for replacement. Google publishes Google has patented something. Nobody checks.
- Misrepresents a material (non-trivial) fact in order to obtain action or forbearance by another person
- The other person relies upon the misrepresentation
- The other person *suffers injury* as a result of the act or forbearance taken in reliance upon the misrepresentation.
Damages in fraud cases is normally computed using
- Recovery of damages in the amount of the *difference between the value of the property* had it been as represented and its actual value
- Out-of-pocket loss, which allows for the recovery of damages in the amount of the *difference between the value of what was given and the value of what was received*.
Usually also heavily implied it needs to involve money in some significant way:
18 U.S.C. § 1343
(...)'any scheme or artifice to defraud, or for obtaining money or property by means of false or fraudulent pretenses, representations, or promises'(...)
Fraud cases also usually heavily apply burden of court practice on the prosecution, to prove fraud and substantial losses. If you type 'John Smith DOB 1/1/1900' the "victim" has to prove it caused them to suffer injury and that there was a significant difference between the value of the property (non-trivial).
Tried this a little bit ago when making a website to try and qualify for the No JS Club inclusion. Wanted to include a bunch of interactive torches that would light when you click on them, and then turn off with subsequent clicks. Grabbed a bunch from the old Geocities gif image archive [1], and then turned them into something similar to this article.
Part I found a bit difficult was using background images, rather than using <img src""> links, and performing x and y shifting to minimize the use of enormous aspect ratio image files (really long strip of image sideways).
The part that's weird with background images though, is that you have to set them up with negative (-) background shifts. So the 24px x 53px image actually shifts -120px sideways each time it goes through an x-loop.
Further, since the sprite sheet is actually 120px x 265px to handle 5 rows of 5 frames, it then requires a somewhat complicated @keyframe definition setup. It actually needs one x-loop that's short, and loops endlessly, going through the full 5 frames, and a second 5x step length y-loop that then iterates once every full x-loop.
Actually imagery and animations that can be played with can be found here: https://araesmojo-eng.github.io under "Lantern Tests Menu"
NOTE: Needs the lantern to function and light the torches. Requires other minor puzzles on the website.
Unfortunately, the 2D imposter mode has pretty significant difficulties with arbitrarily rotated 3D. The GBDK imposter rotation demo needs a 256k cart just to handle 64 rotation frames in a circle for a single object. Expanding that out to fully 3D views and rotations gets quite prohibitive.
Haven't tried downloading RGDBS to compile this yet. However, suspect the final file is probably similar, and pushing the upper limits on GB cart sizes.
Seems cool. Took a couple minutes how to set up a basic object and do a multiple part bouncing ball tween. Haven't really explored the scripting or export options yet.
In a few years, it's become so easy to falsify articles, falsify comments, falsify images, difficult to really even trust responses online anyways. As far back as 2016, Microsoft already had bots deployed online that could respond 96,000 times [1] in 16 hours all over social media. Remember Tay? [1][2]
[1] https://www.theverge.com/2016/3/24/11297050/tay-microsoft-ch...
[2] https://en.wikipedia.org/wiki/Tay_(chatbot)
Even official government responses.
The British Royal family went to falsification immediately. [3] Note child's broken fingers bent sideways (lower left, didn't even get circled)
[3] https://inews.co.uk/news/signs-princess-kate-royal-family-ph...
The White House is posting altered arrest images of people. [4]
[4] https://www.theguardian.com/us-news/2026/jan/22/white-house-...
Can't trust this stuff much anymore. Obvious caveat with this post.
reply