RT @panphora: When I posted to HN yesterday, I was thrilled to hit top 10. What I was NOT expecting. ??!. Getting….

When I posted to HN yesterday, I was thrilled to hit top 10. What I was NOT expecting. ??!. Getting to #1 on HN with today. Someone noticed the note in the footer on OverType and posted it!!!. 42 early access signups so far 😲❤️.

Join millions who have switched to Grok.

OverType is now live and open source. Try it: GitHub: 45KB total. No virtual DOM. No magic. Sometimes the dumbest ideas are the best ones. 🤷‍♂️. 🧵 9/9.

The constraints:.- Monospace font only.- Same font size everywhere.- Markdown syntax stays visible. But for a 45KB editor that just works? I'll take those tradeoffs any day. 🧵 8/9.

Because it's a real textarea, you get everything for free:. ✓ Undo/redo.✓ Mobile keyboards.✓ Native performance.✓ Accessibility. No reimplementing browser features. No virtual DOM. Just. a textarea. 🧵 7/9.

Here's the entire trick in 10 lines:. ```.textarea .style .background = 'transparent'.textarea .style .color = 'transparent'.textarea .style .caretColor = 'black'. textarea .oninput = () => {. preview .innerHTML = parseMarkdown(textarea .value).}.```. 🧵 6/9.

The solution? Obsessive normalization. Replace bullets with HTML entities (•). Override EVERY piece of CSS that could affect spacing. Test on every browser, every font, every zoom level. It's tedious. But once it works, it REALLY works. 🧵 5/9.

Version 1 failed spectacularly. Turns out perfect alignment is HARD:. • Bullet points throw off character counts.• "Monospace" fonts sometimes aren't truly monospace for bold/italic.• Page CSS can shift alignment by 1px and ruin everything. 🧵 4/9.

After years fighting ContentEditable, I had a dumb idea:. What if we just. put a transparent textarea on top of a rendered preview?. If they're perfectly aligned, you'd be typing plain text but *seeing* formatted text. 🧵 3/9

The problem: I needed to add editors to dozens of places on the same page. Initializing a 500KB editor library each time? No thanks. Plain markdown in a <textarea> works great for devs, but clients hate looking at raw markdown syntax. 🧵 2/9.

Launching OverType:. → ←. I got so frustrated with WYSIWYG editors I built my own. The twist? It's just a textarea. OverType: A transparent <textarea> layered over rendered markdown. You type plain text, but see rich formatting. 🧵 1/9.

feel great being at the top of a session with Claude Code and about to get fresh tokens

HOW LONG BEFORE HE CALLS HIM GAVIN NUISANCE.

I made a monospace revenue dashboard for my product, hyperclay. I will get out of the $0/mo club soon, mom!. #buildinpublic

In years — not decades — there will be a premium on thoughts AI has never touched.

Here's where he tries to launch a ❌ FRAUDULENT crypto project using Hyperclay: Please report.

Here's another post where he takes credit for Hyperclay: Please report.

Hi friends! Please help 🙏. Someone is impersonating me — and taking credit for an app I put my heart into over the past year and a half. Please do me a BIG favor and report this post and the account that posted it (scammer: @petertebow ❌)! . Fake post:

Took me 2 weeks to plan out a major refactor. I organized the plans into sub-plans, until I had a 3-part refactor. Then, one night two weeks ago, I handed it all over to Claude Code at 4am. The result was truly beautiful 🤩. But. I've spent the last two weeks fixing bugs 😂

Early GPT-5 benchmarks feel more like a 4.x fine-tuning than a breakthrough. Solid gains, buy not the seismic shift we were looking for. The progress is a straight line, but the hype curve is exponential. Warranted?.