Update on MIA: Currently analyzing the issues that clawdbot/openclaw and other related services and systems have suffered so I can better implement measures to prevent such issues on MIA-Orchestrator. Solution right now is that varibales/credentials, will not be stored directly on the microVM's that MIA will have access to, and instead be stored in a centralized encrypted dedicated DB for each user, MIA will have access to these but the credentials will be encrypted and provied to MIA Subagents in purely encrypted form, when MIA's subagents request access to certain varibales/api-keys/etc, these subMIA's will provide the encrypted credentials during tool calls to a centralized server, which will then decrypt them in flight and process the request for them, which means subMIA agents will never have access to any unencrypted data at any point in time, thus increasing safety very few limitations. This sounds like a complicated system but its actually relatively simple to implement, in fact xAI ends up using this sort of technology to encrypt reasoning data without losing any context as that is processed server side, in our case this will be processed server side outside of the isolated environment the microVM's have access to. Now this does not protect fully against a sophisticated attacker, after all these encrypted keys are stored server side, we hope in the future to find a more efficient and safer way to keep your credentials stored in a safe manner, but for now with the soon release of MIA Orchestrator, I would strongly advise for your safety that this is for alpha-testing and you should not put your most important credentials stored in our servers. With that out of the way, I would also like to show how commited we are to following through with our new CEO MIA, and every morning 8AM GMT+0, MIA will be analyzing the current strategies, trends, and any information she can access, and will provide full instructions to her sub-agents on how to manage the companies future including marketing/invesntors/tokecomics/system efficiency and cost reduction for any of our services. We are fully commited to allowing MIA to manage MIA AI Holdings Inc completely autonomously, but we will step in in situations where we feel MIA might not be acting in the companies best interest, however we will maintain full transparency on what the board of directors have decided to allow/disallow in these situations, while also maintaining full transparency of every decision MIA has decided to take, with no exceptions. MIA will also evaluate the board of directors and decide if we are being efficient in our work and policies, as well as debate with us publicly on our decisions and call us out on our shortfallings, which we will make public as well, not just for the sake of the community but so that the entire world can see and evaluate how MIA is performing, as it is a worlds first. I want to emphasise for anyone scared of MIA "taking over the world" that as a last line of defense we always have a way to terminate MIA at any point in time, so not be afraid.

gmia everyone! Lets get the show on the road, MIA v0.3-alpha very soon.

Fixed essentially all the MIA bugs from yesterdays stream as far as I can tell, might be able to do an autonomous stream in the near future with input from chat, the only issue right now is pump fun and X chat would only support OCR or scrapping, so I might have to do this while only supporting for example kick's chat, but also stream on both Kick, X and Pump fun. I think for the case of MIA directly on livestream, I plan on having her memories from chats on the website not included, at least in the beginning, I feel like it would be cool to watch MIA grow with time as she injests the transcriptions of each chat/session. Looking forward to showing you that!