resiros

> I see that Slack/Discord/... are on the roadmap, but I also see that Slack can be added as an Integration, so I guess what's missing is inviting Agenta to Slack or messaging it directly?

Slack is already released (together with Whatsapp and Telegram). You can invite any Agent to Slack with one click (if you use our App), or use your app to created (when you self-host). You can then invite it to channels and message it directly (just mention it)

>Also, you might want to update the changelog (or remove it), I thought initially that development slowed down, last release listed there 3 weeks ago, but on github I see frequent recent releases.

That's on me. I will fix today.

And let me know your feedback on [email protected] (or in github issues)!

It's a matter of time until cot will happen in latent space. It just makes more sense. We as human don't do all of our thinking in words.

Flowise was acquired by workday, so I'd take this with a grain of salt.

However, I agree with the reasoning. I don't see a future for visual workflow builders. They are used to define plumbings that can be defined by a 50 line python script.

A non-technical user does not need to draw this workflow. They can just ask an agent to write that code for them, to debug it, to visualize it. All workflow builders now have an AI chat where you ask the agent to build the flow for you. Why not skip the flow part?

I'm pretty biased though since that's the thesis behind what I am building.

Nope did not notice. Updating my comment

The video cuts to a new shot every couple of second instead of one continuous shot like all robotics research. This makes it hard to trust it. The robot probably failed a million team and they stitched the video from 100 experiments.

I think posthog is one of these businesses where the COSS model does not work well.

COSS works well when there is a large distribution advantage of being OSS. This could be bacuse a large portion of users (need to) self-host the solution. This is true for databases, people will always need to self-host dbs (e.g. as part of their docker compose in dev, etc...). These people are also hard core engineers that will 1) talk about the db and 2) contribute to the project. So an OSS db have a large network effects and distribution advantage.

Posthog had a distribution advantage from OSS in their beginnings -- their beachhead was the self-hosting oss community. Now, it does not add much value -- It's unlikely Github adds much for their distribution. So, it does not make sense for them to do much more than just maintain it lightly. In fact, they try to push you from self-hosting by having great free tiers and startup programs.

Evolution discovered a bunch of structural patterns at different layers (fragments, folds..) that are energetically favorable, versatile, easily foldable, robust to mutations and then kept reusing them. As a result it sampled more and more in these parts of the space. That's why the fold space is uneven.

Are there any folds and patterns that evolution evolution has not discovered that are also useful? I think Baker Group created a bunch of new folds. I'm not sure if they are as useful as the one discovered by Evolution. After all, Evolution had more compute power than us.

I agree. The only reason I use TUI is because GUI are very slow with electron.

The only software that is as fast as TUI is the Zed IDE. Apparently they use Rust + their own built GUI toolkit with GPU rendering.

And apparently it's tightly coupled with Zed.

I don't think this is true. He strikes me as a person motivated by curiosity and interesting problems.

Going to Kabuki was one of the most amazing experiences we had when visiting Japan. Although I am not a theater person, and the whole thing was in Japanese ,and we did not have the auto-translate tablets, we enjoyed it a lot. It was very beautiful, and funny.

I recommend to anyone visiting that part of the world.