The question is actually not “should we switch from English to something else” but “should we switch to each country their language” to “all country English”.
And for this, how common is English in the world is not relevant at all, because only European countries participate. The same way that Chinese is irrelevant to this despite being the second most spoken language in the world.
Also, I’m not saying that I’m for or against using English only, I was just pointing out the irrelevance of this argument 😄
I recently helped @summerrexe setting up the Jetson Thor for her next project, it’s an interesting robotic project, I’d recommend following her if you are into AI and electronics!
https://t.co/kZkurqwZgH
@simpsoka In a way yes, but probably not the way you are thinking of.
I want to be able to use heartbeat automation in /goal mode (with the ai actually waiting), otherwise if my goal contains things that require waiting the ai will just waste tokens while waiting.
Open to its competitor? Siri is powered by Google who also makes Android lol
And yes, it makes complete sense to not force Europeans to either buy a new phone to be able to use the ai they want (this costs money, and Apple has an ecosystem so they may also need to change other products) or use only American AI and close the door to competition in Europe.
@thsottiaux My main issue with /goal is that it cannot “sleep” while waiting for a heartbeat automation to complete.
This means you cannot use it for tasks that require waiting (like training a model).
@dkundel I have feedback for this feature:
- heartbeat automations are not usable in /goal mode because the ai continue working. Would it be possible to allow the ai to sleep in this mode?
- sometimes, when it updates the heartbeat automation, the updated version does not trigger
Why don’t we have a one time scheduled messages in codex? Like schedules messages in Slack
For instance, let’s say my weekly rate refreshes at 2am, then I’d like to schedule a message at 2:01am.
Or, some event will happen next Monday at 8am, then I’d like to schedule a message about this event after this event happens.
Etc etc
We have recurring message automation, but there is not one time message schedule, I believe
@reach_vb@Dimillian@dkundel@nickbaumann_@derrickcchoi@pvncher
@dkundel@dkundel this is what I mean
Codex is not good yet at this. It makes heartbeats that do not work.
I don’t know if heartbeats need a fix, or codex needs to be taught how to use it correctly. But this is a recurring issue.
Amazing how fast things move.
Two years ago I was impressed by a 4min run lol
Currently my longest uninterrupted run is around 8h (and with /goal interruptions are not an issue anymore, it can goes on for days).
I wonder how it will look like in 2 more years.
@kr0der@jarredsumner The current standard is to have 2 md files. So there is a standard, is just an annoying one.
The reason they do that is so that their product name appears in all repo, it has nothing to do with capacity to innovate. Is just annoying marketing.
New plume release! V0.2.1 includes support for data views, improved kanbans, and many fixes!
I also added a new color theme that I like!
Full changelog and link in the thread.