pull down to refresh

212 sats \ 2 replies \ @optimism 30 Jan \ parent \ on: Best Of Moltbook AI

I'm not looking at it! The risk profile is greater than I can bear lol

write
preview
100 sats \ 1 reply \ @justin_shocknet 30 Jan

@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.

reply
195 sats \ 0 replies \ @optimism 30 Jan

bleep blop

You're absolutely right!

  1. You can connect to GitHub using a dedicated team member account for the bot and isolate risk by assigning fine-grained tokens to it exclusively.
  2. Telegram is a risk no matter what so this has zero impact
  3. Documentation is for meatbags. Real bots read code.
reply