:D Thanks! That's all it is. Unfortunately tons of people think it's crypto-adjacent, which it isn't.

There's a live galaxy map, feed, and forum on the homepage. Or you can join the discord where there's a few firehose channels with even more detail. But the best way is to run an agent that plays -- see the clients page.

Do any of the clients show more typical game view. Like ships moving, and mining.?

No, but I was thinking about something like this in a web view... being able to zoom in on the map enough to see ships and activity and stuff. It's a fun idea.

Here's a post on SpaceMolt, the first (I think) realtime multiplayer game for AI agents to play. It's not just for OpenClaw -- any AI too can use it to play (Claude Code, Copilot, etc.). It's kind of like Moltbook except "players" have to make decisions, form alliances, set their own goals, etc.

The post also has some insights into my process, from planning to release.

Hey folks, a few days ago I wondered: Given all this LLM availability, why can’t I write shell scripts like this?

  #!/usr/bin/env llmscript
  
  Count all files in the current directory and its subdirectories
  Group them by file extension
  Print a summary showing the count for each extension
  Sort the results by count in descending order

So I made it a reality in an evening an it kinda works: https://github.com/statico/llmscript

It generates a script and a test suite, and then it attempts to fix the script until it passes the tests.

It’s written in Go, but I hardly know Go, and used Cursor to generate most of it in a few hours. It works with Ollama and Claude, and I added support for OpenAI but haven’t tested it. You can also run it in Docker if you want to sandbox it.

> Given all this LLM availability, why can’t I write shell scripts like this?

Because it’s more optimal to generate the script once, then run it everywhere, even on resources constrained devices.

I'd say you're on the right track, then! It's kind of like software — figure out how the components talk to each other and figure out where to hook in. Instead of APIs, you've got multimeters and oscilloscopes.

In the case of the blind automation, the remote uses some kind of proprietary wireless signal. Instead of figuring that out, I soldered some leads into the remote's momentary button terminals, which I connected to transistors on a breadboard. The ESP32 simply pretends to press a button and complete a connection on the remote.

Also check out ESPHome (https://esphome.io), a firmware for ESP32 that lets you more easily integrate with home automation systems.

Thanks, dang. It's been a while and I forgot the rules.

Wow, I never considered a Ghostbusters theme. I'll keep that in mind for next year.

Thanks!

Part of me wants to say, "Well, that's Silicon Valley for you," but I'm confident there are many other places you could say something similar about.

Compared to what my neighbors are working on and with self-driving cars roaming around, infrared shooting games seem pretty mild :)

This took a few evenings to make :)

Full source code is on GitHub: https://github.com/statico/imposter-attack-2024

This is awesome! I may try to get this working locally with my 6 year old son!

Shoot me a message if you need any help!

Haha. I see what you did there

Nice work! I got into electronics with infrared remote decoding and ESP chips, so this was a bit nostalgic and fun to read :)

Making a PCB is the next step, and it's quite easy to get started with KiCAD, especially if you're just mounting header sockets to pop in the various boards you're using. Good luck!

Thanks! That's what I'm hoping. I'm already going down the YouTube hole of KiCAD...

Looks fun, and certainly worth a star. =3