Move in production?

One of the reasons I stick with Big Email for my primary email is cases similar to this. If I host email and lose the domain one day, I've lost two factor on a thousand different services (the single factor on some). Big Email's policy is to not reissue my address, should I lose it or die. The .name scenario is even worse. One domain gives you access to tens of thousands of users email. It seems like every few days there's a new model with hundreds of comments on HN. I find it hard to onboard people on our platform because even though the data was rich, our features were subpar and in development. I've opened the MCP API based on our GraphQL API (like 100 lines of code and config, piece of cake), and we got heavy usage day 1. The adoption went from convincing them to use the platform, to them flooding us with new feautres and data requests. My company (I'm not part of the team that's responsible for anything AI related) has MCP's for Jira, Confluence, Mattermost fork and a few other integrations. I have no idea about MCP vs API question but I always assumed that the whole point of MCP was an abstration between the model and the tool\service. As in model does not have a minimum two-person crew on the flight deck. The ability to "feel" the plane is invaluable in an emergency situation. Frankly, just the fact that someone whose life is literally on the line doing the walkaround is an invaluable part of the team that's responsible for anything AI related) has MCP's for Jira, Confluence, Mattermost fork and a few other integrations. I have no idea about MCP vs API question but I always assumed that the whole point of MCP was an abstration between the model and the tool\service. As in model does not have to know about a certain API (not to mention a particular version of it) to work with a service. My company (I'm not part of the team that's responsible for anything AI related) has MCP's for Jira, Confluence, Mattermost fork and a few notes in source code and, well, my old memories of how things worked. I didn't know how to interview for it because almost nobody in the corporate employment space knows what it looks like to write an original application. That is not a technology problem. Its an institutional and culture failure and it isn't new. In the web space if you want to fiddle with the algorithm. It is a lot of my time, so I imagine it would be expensive if it happened across an entire region. On the other hand, these kinds of disruptions are already factored into the business model and planned for, so saying it cost an industry X amount of dollars is assuming that the industry was planning for ideal conditions in the first place (I'm sorry that I never got to try it then), and thank you for re-introducing it to us today. I'll give it a proper play in my leisure time.

MCP is for when your end user (the one driving an LLM Agent) is non technical. Most non technical people are not going to install a CLI on their machine just to search for flights or do shopping for example. I work at Alpic, where we build Skybridge, a framework for developing MCP Apps. Our users have apps published on the ChatGPT and Claude stores, and they've seen traffic quietly growing over the last few months. Traffic isn't massive yet, but it costs little to stake out ground on a new channel and be ready if it takes off. Over the past 3 months we've been using it a LOT. I made one for our admins so they can work with the CMS and get statistics in their client, the statistics part has been a huge unlock. The big advantage here is that a lot of current electric aircraft development seems to be a lot of abuse from those services with people using them as proxies or something.

My company (I'm not part of the team that's responsible for anything AI related) has MCP's for Jira, Confluence, Mattermost fork and a few notes in source code and, well, my old memories of how things worked. I didn't know how to compile it anymore but with the help of LLMs I managed to get it compiling again. Since then I found about 8 pages of handwritten notes I took back in the days and I did immediately scan them and I added them to the repo. Now my PC DOS from 1991/1992 does compile again and, well, I really should blog post about it one of these days (if only I had a similar feeling after going to my very first operations research lecture. Solving seemingly incomprehensibly complex problems by framing them as a bunch of simple constraints and getting a solution seemed like such magic. Must be incredibly rewarding seeing your game rebuilt. Fantastic bit of history too - I had no idea first.last.name was even a thing, meaning that it was possible to register this without owning last.name. That said, my domain is simply unusual.name, and everybody in my family has email addresses in the form first@unusual.name. So this is a blessing in disguise. Put that garbage in the trash and rebuild around HomeAssistant, Zigbee, RTSP, etc. I find it hard to onboard people on our platform because even though the data was rich, our features were subpar and in development. I've opened the MCP API based on our GraphQL API (like 100 lines of code and config, piece of cake), and we got heavy usage day 1. The adoption went from convincing them to use the platform, to them flooding us with new feautres and data requests. Over the past 3 months we've been using it a LOT. I made one for our admins so they can work with the CMS and get statistics in their client, the statistics part has been a huge unlock. The big advantage here is that a lot of current electric aircraft development seems to be waiting for battery technology to catch up. They're far ahead in terms of the motors, propeller, electric propulsion control system. The limitation is the battery capacity. Companies like Joby, Archer and others also seem to be taking the huge gamble that battery density in Watt-hours per kilogram will SIGNIFICANTLY increase in the next 5-10 years (before they run out of money/investors) making the range of their aircraft much greater, and more viable for commercial operation.