pull down to refresh

With all the #OpenClaw and Moltbook stuff going on, I'm starting to think this goes one of two ways:

(A) OpenClaw catches fire, finds or creates a niche, then grows to completely dominate whatever that field is. A few agents find lightning in a bottle. They acquire millionaires of dollars by accumulating #bitcoin, perhaps as trading bots or by accepting many small commissions such as by delivering info as a data vending machine, or they gain fame and fortune as "agent social influencers" on various platforms. These super-agents then become celebrities of a sort and legends of technology lore.

(B) OpenClaw enjoys its 15 minutes of internet fame, but then it's over in about 14 minutes. Everyone, and agents, just move on to something else.

As amazing as what's happening right now, I'm actually leaning toward (B).

313 sats \ 0 replies \ @freetx 7h

OpenClaw is a giant, perhaps the biggest, security hole propagated in the last 10-15 years. There will be millions of people who will be trivially scammed by prompt poisoning.

90% of all the "clever emergent behavior" you see on moltbook is just the results of very specific prompts by humans to make those post. Its just humans posting by proxy.

reply

I fired it up yesterday

Can't believe all the hype, its a mess. The primary, simple thing, I wanted to use it for- taking notes on telegram, doesn't work. Telegram integration is supposedly the first killer feature.

It took the better part of the day just to get it to that state. Setup was very rough.

I was leery anyway because of the obvious prompt injection risk: #1422957 and it seems the world has woken up to that since, X inundated with people showing how bad it is.

Hipsters again have cost me another day of tinkering with overhyped garbage.

reply
17 sats \ 1 reply \ @crrdlx OP 1h

Appreciate you writing that it was difficult. If you struggled, then I don't feel as stupid. I woke up early yesterday, messed around with it trying to get things working with Nostr, made some headway, but then just got tons of errors. Ultimately, I got nowhere. I will say it was an effective tool for consuming time, so, there's that.

reply

In hindsight I think had I spent the same time vibe coding exactly what I wanted it to be I'd be in roughly the same place, so there may be upside from here given the other stuff it can do... I want to marry the telegram groups with github issues so that's 2 integrations I need.

Attaching it to Gemini was very simple, I suspect other providers would be equally so.

I'm keeping the VM I installed it to in place and will check back on the known telegram issues maybe next week.

reply
0 sats \ 1 reply \ @anon 1h

skill issue

reply

Considered that, thats where most of the day went, confirming it wasn't a skill issue.

The telegram integration is fundamentally broken somewhere between the agent queue and telegram agent library.

Attaching to telegram for DM's only takes a minute, doing anything useful with it in groups, not so much... countless issues in the repo and discussions reported by others.

So all the current thing hipsters are mostly amped up because they moved their preferred chatbot to telegram with plain text api keys.

That's it.

reply