This type of plant is generally used for emergency power to balance the grid, whilst other plant come online.

Really like the idea of this, and good timing for me. Will give this a try over the weekend.

Thanks! I hope this will be useful for you.

Have a soft spot for digg

Best thing I have seen on HN in ages. Also interesting for a CNC geek.

I had a similar thought about 3D printing - particularly extruding mathematically defined shapes in vase mode.

In both of these cases, mathematically generating the points to visit (in gcode) is needed, and we don't care about constant speed - the firmware handles the instruction->motion part.

I am thinking about non-planar printing mostly, but this could also apply to CNC finishing passes.

Pelican riding a bicycle is only official when it comes from Simon Willison https://simonwillison.net/2025/Jun/6/six-months-in-llms/

I agree. When he logs in to chatbot interfaces, the random seeds become blessed with authenticity and thus only those outputs are valid.

Yeah lets just kill all the bugs, good move.

You have read the part where the sticks provide "good bugs that fall in [...] an escape path", right?

good bugs lol

Reminds me of http://www.gamtech.com/oakflat.aspx loved blowing triggering SCRAM as a kid

Thankyou for the reminder, long term Node-RED user here, I recently looked again at n8n and wondered why I never took it to far, this is the reason. When you see a git icon and repo it's easy missed.

The license looks quite permissive though as long as you're not using n8n as the platform for your business. According to the license, if you just wrap/productize the flows you create and users don't bring their own n8n credentials or API keys, then you're good. It seems like there's a ton you can build off of it and still stay within the parameters of the license.

Yup. Always makes sense to read the actual license too. I did that today and learned n8n changed their license in 2022. So you could look at the licenses before 2022 as well.

Say what you will about it. MCP surely has to be your primary interface?

Actually, while MCP is a great direction for standardizing context, the "special sauce" of Ego isn't the context-passing itself, but the proprietary engine that uses that context to dynamically generate prompts from a deep personality model.

For the MVP, I had to build the custom state handler to prove out that core persona logic first. Long-term, I'd love for Ego to accept context from standard protocols like MCP—it would make the engine even more versatile.

Appreciate the sharp question!

System Prompt aside and not that critical today, however you look at it you are stuffing context. MCP is good at that and it works in most AI‘s.

You're definitely right for now, MCP is great for 'stuffing context'.

However, the long-term goal of this framework is to make the persona itself dynamic. It's designed to use that context to subtly update a persona's core personality traits over time, creating a more 'life-like' evolving 'virtual soul'.

The cherry-on-top is framing it all as a 'Persona-as-a-Service' API to make the dev workflow straightforward but powerful. It's not for every application, but for anything that needs real character depth - like in gaming or advanced assistants - the goal is to make it simple for any developer to create those deeper, more meaningful interactions that are typically hard to get right.

When a competitor buys you this happens. There are plenty of exceptions, however.