True, you need relays - but I run my own mail server, so I know the difference. Public Nostr relays vs managing postfix/spam filters/DMARC/deliverability is night and day.

Re: spam - at least with Nostr: 1) No email address exposed on your site, 2) Easy to filter/block npubs, 3) Can switch identity anytime without updating DNS/MX records. And if you DO run your own relay, it's way simpler than email.

True, you need relays - but I run my own mail server, so I know the difference. Public Nostr relays vs managing postfix/spam filters/DMARC/deliverability is night and day.

Re: spam - at least with Nostr: 1) No email address exposed on your site, 2) Easy to filter/block npubs, 3) Can switch identity anytime without updating DNS/MX records. And if you DO run your own relay, it's way simpler than email.

I would estimate that initial consultations will be possible very soon, once legislators clear the way for it. The technology is already working excellently for basic cases.

Yes, we're using AI to build phone bots for law firms. This is working very well at this point.
The technology has matured significantly. We can now handle complex legal intake calls, appointment scheduling, and initial client consultations with natural conversation flows. The key has been fine-tuning the systems to understand legal terminology and maintain the professional standards that law firms require.

Hey, thanks for trying it out and for reporting this.

The repo doesn’t ship a dist/ folder on purpose (it’s in .gitignore), so you need to build it once before running. I updated the README.md to make that clearer.

To run it locally: after npm install, run npm run build (creates dist/), then npm run preview. Or simply npm start – that builds and starts the preview server in one go.
For development (with hot reload): just npm run dev – no build needed.

For GitHub Pages: in your fork, set Pages source to GitHub Actions (not “Deploy from a branch”). The workflow will build the app and deploy it; no local dist/ required.
Hope that fixes it. Let me know if something still doesn’t work.

Hey, sorry for the hassle.

The 404 happens when Pages is set to “Deploy from a branch” with the main branch and the root (/) folder. In that case GitHub serves the raw repo (your source code), but the actual site is built by Vite into a dist/ folder. The root only has things like src/, package.json, etc., and no index.html, so the browser gets a 404.

What to do: In your fork go to Settings → Pages. Under Build and deployment, set Source to GitHub Actions (instead of “Deploy from a branch”). Then the workflow runs on every push to main: it runs npm run build and deploys the built dist/ folder. Give it a minute or two after a push, then https://4g0r4.github.io/Zoop/ should load.

I’m not that experienced with Git and GitHub myself, so I only figured this out with some help. We’ve added a “Quick Start for Forks” section in the README with these steps so it’s easier next time. Hope that fixes it for you.

Thanks for forking! Can you tell me a bit more? do you see any errors in the browser console?

Thanks for the detailed feedback. I already using NIP-44 for signaling and a TURN fallback (Metered). I'll look into adding a short lookback window for the since filter to handle relay clock skew. Appreciate it.

Best and simplest explanation I have heard so far

Thank you for the explanation Fren