We just shipped a new feature in NextDNS: Bypass Age Verification.More and more sites (especially adult ones) are now forcing users to upload IDs or selfies to continue. We think that’s a terrible idea: handing over government documents to random sites is a huge privacy risk.This new setting workarounds those verification flows via DNS tricks. It’s available today to all users, including free accounts.We’re curious how the HN community feels about this. Is it the right way to protect privacy online, or will it just provoke regulators to push harder?<a href="https:&#x2F;&#x2F;nextdns.io" rel="nofollow">https:&#x2F;&#x2F;nextdns.io</a>

Show HN: NextDNS Adds "Bypass Age Verification"

Claudia – Desktop companion for Claude code

The Enterprise Experience

ArchiveTeam has finished archiving all goo.gl short links

Hi HN! I got so frustrated with modern WYSIWYG editors that I started to play around with building my own.The problem I had was simple: I wanted a low-tech way to type styled text, but I didn&#x27;t want to load a complex 500KB library, especially if I was going to initialize it dozens of times on the same page.Markdown in a plain &lt;textarea&gt; was the best alternative to a full WYSIWYG, but its main drawback is how ugly it looks without any formatting. I can handle it, but my clients certainly can&#x27;t.I went down the ContentEditable rabbit hole for a few years, but always came to realize others had solved it better than I ever could.I kept coming back to this problem: why can&#x27;t I have a simple, performant, beautiful markdown editor? The best solution I ever saw was Ghost&#x27;s split-screen editor: markdown on the left, preview on the right, with synchronized scrolling.Then, about a year ago, an idea popped into my head: what if we layered a preview pane behind a &lt;textarea&gt;? If we aligned them perfectly, then even though you were only editing plain text, it would look and feel like you were editing rich text!Of course, there would be downsides: you&#x27;d have to use a monospace font, all content would have to have the same font size, and all the markdown markup would have to be displayed in the final preview.But those were tradeoffs I could live with.Anyways, version 1 didn&#x27;t go so well... it turns out it&#x27;s harder to keep a textarea and a rendered preview in alignment than I thought. Here&#x27;s what I discovered:- Lists were hard to align - bullet points threw off character alignment. Solved with HTML entities (• for bullets) that maintain monospace width- Not all monospace fonts are truly monospace - bold and italic text can have different widths even in &quot;monospace&quot; fonts, breaking the perfect overlay- Embedding was a nightmare - any inherited CSS from parent pages (margin, padding, line-height) would shift alignment. Even a 1px shift completely broke the illusionThe solution was obsessive normalization:<pre><code> &#x2F;&#x2F; The entire trick: a transparent textarea over a preview div
 layerElements(textarea, preview)
 applyIdenticalSpacing(textarea, preview)

 &#x2F;&#x2F; Make textarea invisible but keep the cursor
 textarea.style.background = &#x27;transparent&#x27;
 textarea.style.color = &#x27;transparent&#x27;
 textarea.style.caretColor = &#x27;black&#x27;

 &#x2F;&#x2F; Keep them in sync
 textarea.addEventListener(&#x27;input&#x27;, () =&gt; {
 preview.innerHTML = parseMarkdown(textarea.value)
 syncScroll(textarea, preview)
 })
</code></pre>
A week ago I started playing with version 2 and discovered GitHub&#x27;s &lt;markdown-toolbar&gt; element, which handles markdown formatting in a plain &lt;textarea&gt; really well.That experiment turned into OverType (<a href="https:&#x2F;&#x2F;overtype.dev" rel="nofollow">https:&#x2F;&#x2F;overtype.dev</a>), which I&#x27;m showing to you today -- it&#x27;s a rich markdown editor that&#x27;s really just a &lt;textarea&gt;. The key insight was that once you solve the alignment challenges, you get everything native textareas provide for free: undo&#x2F;redo, mobile keyboard, accessibility, and native performance.So far it works surprisingly well across browsers and mobile. I get performant rich text editing in one small package (45KB total). It&#x27;s kind of a dumb idea, but it works! I&#x27;m planning to use it in all my projects and I&#x27;d like to keep it simple and minimal.I would love it if you would kick the tires and let me know what you think of it. Happy editing!---Demo &amp; docs: <a href="https:&#x2F;&#x2F;overtype.dev" rel="nofollow">https:&#x2F;&#x2F;overtype.dev</a>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;panphora&#x2F;overtype" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;panphora&#x2F;overtype</a>

Show HN: OverType – A Markdown WYSIWYG editor that's just a textarea

Derivatives, Gradients, Jacobians and Hessians

Web apps in a single, portable, self-updating, vanilla HTML file

Google admits anti-competitive conduct involving Google Search in Australia

A gigantic jet caught on camera: A spritacular moment for NASA astronaut

I got tired of open file.docx → wait 8 seconds → close Word just to read a document, so I built a terminal-native Word viewer!What it does:* View `.docx` files directly in your terminal with (mostly) proper formatting* Tables actually look like tables (with Unicode borders!)* Nested lists work correctly with indentation* Full-text search with highlighting* Copy content straight to clipboard with `c`* Export to markdown&#x2F;CSV&#x2F;JSONWhy I made this:Working on servers over SSH, I constantly hit Word docs I needed to check quickly. The existing solutions I&#x27;m aware of either strip all formatting (docx2txt) or require GUI apps. Wanted something that felt as polished as [glow](<a href="https:&#x2F;&#x2F;github.com&#x2F;charmbracelet&#x2F;glow" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;charmbracelet&#x2F;glow</a>) but for Word documents.The good stuff:* 50ms startup vs Word&#x27;s 8+ seconds* Works over SSH (obviously)* Preserves document structure and formatting* Smart table alignment based on data types* Interactive outline view for long docsBuilt with Rust + ratatui and heavily inspired by Charm&#x27;s [glow](<a href="https:&#x2F;&#x2F;github.com&#x2F;charmbracelet&#x2F;glow" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;charmbracelet&#x2F;glow</a>) package for viewing Markdown in the CLI (built in Go)!<pre><code> # Install
 cargo install --git https:&#x2F;&#x2F;github.com&#x2F;bgreenwell&#x2F;doxx
 
 # Use
 doxx quarterly-report.docx
</code></pre>
Still early but handles most Word docs I throw at it. Always wanted a proper Word viewer in my terminal toolkit alongside `bat`, `glow`, and friends. Let me know what you think!

HN

Show HN: NextDNS Adds "Bypass Age Verification"

Claudia – Desktop companion for Claude code

The Enterprise Experience

ArchiveTeam has finished archiving all goo.gl short links

Show HN: OverType – A Markdown WYSIWYG editor that's just a textarea

Derivatives, Gradients, Jacobians and Hessians

Web apps in a single, portable, self-updating, vanilla HTML file

Google admits anti-competitive conduct involving Google Search in Australia

A gigantic jet caught on camera: A spritacular moment for NASA astronaut

Show HN: Doxx – Terminal .docx viewer inspired by Glow

Why Nim?

Llama-Scan: Convert PDFs to Text W Local LLMs

Clojure Async Flow Guide

BBC Micro, ancestor to ARM

I Prefer RST to Markdown (2024)

A Visual Exploration of Gaussian Processes (2019)

Non-Uniform Memory Access (NUMA) is reshaping microservice placement

SystemD Service Hardening

Mangle – a language for deductive database programming

Modifying other people's software