MK Fain on Nostr: It's probably not worth bothering, but I will answer this in good faith because it's ...

It's probably not worth bothering, but I will answer this in good faith because it's actually very simple:

We did not make changes to the models themselves. The premium models have been capable of building these kinds of apps for 6 months, at least.

What we built (often with AI-assistance in the terminal and code editors) is a website that allows non-coders to use the same AI tools that coders already have access to. And yes! We did use our own tools to build it! But we also had to build, update, and maintain those tools in the first place, too :)

So, if you already knew your way around a terminal, text editor, nostr libraries, AI providers, and managing agents, then all Shakespeare does is provide a convenient UI wrapper for your projects.

However, if you have never opened a terminal before, don't know what AI providers are or how to choose a model, don't know how to prompt to get it to build a Nostr app... we put all of that in a friendly web interface with most of the hard stuff behind the scenes so you can have low-barrier access to the same power that coders already had.

The goal is to make what WE could already access accessible to everyone. I think we've come pretty close to that.

Yes, there are limitations on what AI can build (though those limitations shrink by the day). But at least now everyone can use the same tools, which is actually sufficient for a huge population of people whose projects don't have complicated or unique technical needs.

We've been very open in documenting this process from the ground up, and encourage you to dig into how the tech works behind the scenes if you're curious!

https://soapbox.pub/blog/stacks/

https://soapbox.pub/blog/mkstack-tutorial/