Sabitlenmiş Tweet
nForms
7 posts


@alexandersstudi Exactly this. PoW flips the model entirely —
the browser does the work, the user does nothing.
No visual challenge. No auditory fallback needed.
Just math.
What stack are you working with?
English

@nformseu WCAG 2.2 AA is the benchmark now, and you're right, CAPTCHAs are a common accessibility hurdle. There are definitely better patterns for bot protection that don't rely on visual or auditory challenges.
English

nForms is now listed on @TrustMRR
Real numbers. Verified by Stripe. No screenshots.
What @marclou built is exactly what the indie hacker community needed — transparency that can't be faked.
We're starting from €0. Building in public.
trustmrr.com/startup/nforms
English

Couldn’t be easier to use!
nForms.eu
Noah Kellner@but_noah0
One script tag. <script src="api.nforms.eu/shield.js" /> - Bot protection (PoW, not CAPTCHA) - WCAG 2.2 AA validation (auto ARIA injection) - Form backend (EU-only, zero cookies) Free tier. No npm install. No build step. nforms.eu/docs
English

Try nForms Today for Free!
nForms.eu
Noah Kellner@but_noah0
reCAPTCHA sets cookies. Turnstile sets cookies. hCaptcha sets cookies. Your cookie banner? That's not UX. That's the cost of using US bot protection on EU forms. I built nForms Shield: SHA-256 Proof-of-Work. Zero cookies. EU-only. nforms.eu
English
nForms retweetledi
