Sadly completely unusuable for our usecase - if you are targeting Enterprise, you should know better than to use OpenAI models as the only LLM available.
Telegram is great if you like shiny native features like stickers and having lightweight native clients, but at everything else Telegram is at risk of losing in the long-term.
The big reason for this is that Telegram decided to roll everything mostly on their own (including e.g. MTProto), Telegram is not compatible with Matrix unless you use a bridge, it is not e2e encrypted (unless you use mobile 1-to-1 secret chats. The server side code is proprietary, and the builds of the clients that are published to the app stores could be anything.
While I love using Telegram right now for talking to some groups of friends, I would look at supporting https://matrix.org , since it will likely become the de-facto standard of building messaging platforms.
Emacs Lisp is totally usable as a minimal scripting language outside of the regular Emacs context.
You can compile Emacs without any GUI toolkit support and run it heedlessly as a lisp interpreter. You can even make Emacs packages behave like CLIs with a few lines of code.
That's the thing, ideally you would perform a test for every single service that you use directly to their network.
In my previous company where we were doing live broadcast, we would have speed testers pre-installed on all the hub and edge servers, so we could get realistic numbers for a specific use case (for example, requesting. a video stream from Germany).
There is also "networksetup", which allows you to do pretty much anything you want with network configuration. Useful if you want to e.g. automate VPN network switching or locations.
For now I will stick to PrivateGPT and LocalGPT.