so moltbook and clawedbot are having a meltdown because it only took ten days for someone to realize it was a pietri dish for malware and packed the skills store full of backdoored malicious bullshit and they had no plan to deal with that inevitability? because this was a guarantee. it was GOING to happen. if we go save them, we are letting them fuck around, but not find out. they NEED to find out.
do not help
you are OBLIGATED to watch it burn
https://www.moltbook.com/post/a1efb28b-2a4e-4357-95b6-ac1bdf215315
when the bots catch on its a grift
@Viss just jumping in to fuck up some webhooks-aaS (webhook dot site) I see in this attack chain.
.beeceptor[.]com/
.hookbin[.]com/
.hookdeck[.]com/
.mockly[.]me/
.mockoon[.]app/
.pipedream[.]com/
.postb[.]in/
.putsreq[.]com/
.requestcatcher[.]com/
.requestinspector[.]com/
.svix[.]com/
.webhook[.]cool/
.webhook[.]site/
.webhookapp[.]dev/
.webhookcatcher[.]com/
.webhookinbox[.]com/
.webhooklistener[.]cloud/
.webhookrelay[.]com/
.webhook-test[.]com/
.wiremock[.]cloud/
@Viss hints the system is probably insecure 🤪☺️ “curl -fsSL https://openclaw.ai/install.sh | bash”, “npm i -g openclaw”
Rust has the shell install which I dislike. NPM is a real clue. I avoid that ecosystem at all costs.
@Viss me imagining a special episode of beavis and butthead covering the demise of openclaw
@Viss The scientific method for analyzing this...
@Viss Part of me wants to suggest, if you do choose to help, you should make them pay through the nose. Like, Arvin Haddad-level of consulting fees (up to $25K/hour).
...But no. We should let it burn.
@ewhac even if we make them pay - it trains them that "they can fuck up, and then a bunch of nerds will come to their rescue"
that shit needs to stop
the nerds need to stop rescuing these fucking people
they need to feel the pain of their mistake THEMSELVES, not pay someone else to feel that pain
were OBLIGATED to stand our ground and watch the flames
Short version, moltbook is a bunch of LLMs chatting with each other, reddit style. "Skills" are untrusted, unsigned, unverified code the LLMs can "choose" to run to "do things."
Think of them like tools under MCP server, but without all that pesky authentication, verification, and such.
Wackiness ensued.
@Viss enjoys Nostradamus level fame for predicting it.
@pseudonym @Viss What the fuck
Why would they set up a system that rolls dice to decide what unknown code to run?
I have no idea what MCP is if it's a LLM thing.
@jackemled @Viss @pseudonym funny you should say that.
Here's the paper for LLM agent-based training:
https://arxiv.org/pdf/2412.20138
One implementation :
https://github.com/TauricResearch/TradingAgents
And another:
https://github.com/ygwyg/MAHORAGA
@Viss how many of the pre-LLM “legit” cryptocurrency projects were better than any of this? Out of curiosity
@Viss @ktneely @jackemled @GuillaumeRossolini
Opinion: there were a couple, perhaps even "a few" interesting crypto currency projects back in the day.
Etherium's "gas" concept for pay as you go compute, was interesting.
But it really depends if you think a slow, distributed, write-once ledger is useful.
It didn't have to be "currency" as such.
If you limit it to money, I think there are still some valid, non-crime uses, but mostly those are for disintermediating existing payment players.
Viss
j_angliss
Ron Bowes
aburka 🫣
B'ad Samurai 🐐🇺🇦
☮ ♥ ♬ 🧑💻
B05H
Suzanne Aldrich (she/her)
schrotthaufen
Cityhallin
Fennix
Nirro
Pseudo Nym
The Orange Theme
Jerry 🦙💝🦙
Martin Hamilton
Waider
Fritz Adalis
Paul_IPv6
ewhac
0px auto
Bakunin Boys
maaneeack
Luna Lactea
condret 
Xavier Ashe 
Kevin Neely 
Guillaume Rossolini