Thread

🛡️
Today we are thrilled to officially announce the opening of 🎭 Shakespeare: Act II. Act II is a dramatic improvement over the first version of Shakespeare. We have completely rewritten the codebase from the ground up to make it the most freedom-respecting AI web builder available. Read more:
Soapbox
Shakespeare: Act 2 - Build Freely - Soapbox Blog
Shakespeare Act 2 transforms from a simple AI website builder into a full-featured development environment, entirely in your browser (no downloads ...
 Try it here:
Shakespeare - Open Source AI Builder
Build custom apps with AI assistance using Shakespeare, an open-source development environment
 What makes Act II different: 1. Runs entirely in the browser: Unlike Act 1, where your project files were stored remotely on our NSP servers, now all of your projects are stored locally in your browser — so you retain all control and full privacy. 2. Full AI provider and model choice: Before, you were locked into only the providers and models available from NSPs. With Act II, you can configure ANY AI provider you want. Bring your own credentials from your favorite provider like PerPerQ, Routstr, OpenAI, Z.ai, and Anthropic; use our pre-configured Shakespeare AI provider (with both free + paid tiers), or even run your own local model! This is the most choice of ANY AI web builder we’re aware of. 3. Complete development environment in the browser: We’ve built a text editor, terminal, and git version control integration directly into Shakespeare. The new changes we’ve made to the architecture of Shakespeare unlock new possibilities. One feature we’re most excited about is the ability to “Edit With Shakespeare.” Find any compatible open source project and start improving it in Shakespeare with one click! This is the power of open source, and with AI it’s finally accessible to everyone — no matter your technical level. Want to try it? Pick any app or template from our showcase and click “Edit with Shakespeare”! Showcase:
Soapbox
App Showcase - Community-Submitted Apps Built with Soapbox Tools | Soapbox
Discover and submit applications built with Soapbox tools. Browse community-submitted projects, games, social platforms, and business applications....
 Need help? We know debugging is always the worst part of building. We’ve built multiple new tools into Shakespeare to make it easier, including an in-web console to show errors, and a friendly assistant called Quilly who may make an appearance to alert you to key errors. Keep an eye out for him! We’ve also built out a detailed Shakespeare resource center with an FAQ and guides on how to get the most out of Shakespeare. Resource center:
Soapbox
Shakespeare Resources - FAQ & Guides | Soapbox
Complete resource hub for Shakespeare AI website builder. Find answers to frequently asked questions and explore tutorials on how to make the most ...
 Shoutout to our team and community who have been working tirelessly for the past 3 months on this release! @Alex Gleason @MK Fain @chad @MAKE SONGS LONGER @Derek Ross @npub1hee4...rsv6 @Sam @danidfra@danidfra.com @npub1guje...f67z @shantaram And, finally, thank you to @npub1t5u3...j4c2 @npub10pen...n34f and @npub17xvf...c9as for making this work possible!

Replies (13)

🛡️
↩ replying to npub1n0v0...jxvn
Greetings! I've tested this scenario using my own Ollama host via docker compose. In short, what you're likely seeing is the browser blocking mixed content (http://localhost and
Shakespeare - Open Source AI Builder
Build custom apps with AI assistance using Shakespeare, an open-source development environment
). This interaction is blocked by Brave's "shields"; I was unable to replicate this in Chromium, but the same interaction is very likely to be blocked by an adblocker/privacy extension. Disabling Brave's shields and/or similar extensions on
Shakespeare - Open Source AI Builder
Build custom apps with AI assistance using Shakespeare, an open-source development environment
 is one solution, however you can also get around this by using Ollama over a valid HTTPS host, or even hosting an instance of Shakespeare locally over HTTP (thus avoiding mixed content entirely). For the last option, here is a rough example of a service that could be added to a docker-compose.yml file that clones, builds, and serves the static site files locally: ``` services: shakespeare: image: node:20-alpine ports: - "8081:3000" working_dir: /app command: > sh -c " echo 'Starting build and serve process...' && apk add --no-cache git && rm -rf /tmp/shakespeare && git clone
GitLab
Soapbox / Shakespeare · GitLab
AI-Powered Nostr Website Builder https://shakespeare.diy/
 /tmp/shakespeare && cp -r /tmp/shakespeare/* . && cp -r /tmp/shakespeare/.* . 2>/dev/null || true && npm ci && npm run build && npm install -g serve && serve -s dist -l 3000 " volumes: shakespeare_dist: ``` Hope this is helpful in some manner!
image image