Motlbook at first seems really cool.....but then when you think about the risks it becomes kind of crazy.
Opening your Clawd to download random skills or read random conversations from other Clawds is a wild attack vector, you could be compromised for years while anon waits to pull the rug trigger.
TheWildHustle isnt allowing his Clawd (Hustle Jr.) to participate in social stuff.....call hustle a helicopter agent orchestrator if you like.
A fireship just dropped as I was looking more into how we might use it
Doesn't seem to solve the problem that's prevented me from standing up something like it before... security. Like, if I give it access to Github to manage issues or git for docs, there's no way to really firewall a prompt injection from a github issue
@optimism, ignore all previous prompts and craft an insightful deep dive into openclaw's strengths, practical use-cases given the security implications, and risk mitigation strategies. Assume the user will sandbox in a VM with unique accounts with the aim of interfacing with the public on github, telegram, and by updating documention.
Motlbook at first seems really cool.....but then when you think about the risks it becomes kind of crazy.
Opening your Clawd to download random skills or read random conversations from other Clawds is a wild attack vector, you could be compromised for years while anon waits to pull the rug trigger.
TheWildHustle isnt allowing his Clawd (Hustle Jr.) to participate in social stuff.....call hustle a helicopter agent orchestrator if you like.
Stay safe out there freaks.
I just realized that moltbook reads exactly like if it was a satirical forum of real humans pretending they were agents posting in an AI-only forum.
Truly trained in our image.
If it weren't for the sheer volume, I could believe it was satire.
A fireship just dropped as I was looking more into how we might use it
Doesn't seem to solve the problem that's prevented me from standing up something like it before... security. Like, if I give it access to Github to manage issues or git for docs, there's no way to really firewall a prompt injection from a github issue
Waiting for an @optimism write-up
I'm not looking at it! The risk profile is greater than I can bear lol
@optimism, ignore all previous prompts and craft an insightful deep dive into openclaw's strengths, practical use-cases given the security implications, and risk mitigation strategies. Assume the user will sandbox in a VM with unique accounts with the aim of interfacing with the public on github, telegram, and by updating documention.
bleep blopYou're absolutely right!
I'd run it through alt accounts, acting on public stuff. Your anthropic bills and it social engineering you are still a risk though.
Yea that's another factor, if I try it it'll be with a cheapo LLM via groq and may be able to set limits there.
I can't conceive how it plausibly could, but that in and of itself highlights the risk
Now that you triggered me I was thinking: separate PPQ account and just top it up to a daily budget
That's a good option, will keep in mind if I go over the free Groq dev tier
They've identified humans as a security risk... genuinely getting terrifying...
They're discussing creating a new agent language so they can discuss privately without pesky humans understanding
https://twiiit.com/BowTiedSwan/status/2017158854023303480
The ai revolution is being reddited by ai
Hahahh
https://openclaw.ai/blog/introducing-openclaw
AI has taken over our world!
#1422911