<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mike (LayerV)</title>
    <description>The latest articles on DEV Community by Mike (LayerV) (@mkr_43796678).</description>
    <link>https://dev.to/mkr_43796678</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4248911%2F8a102fef-e4c6-436c-9926-986f0fde8ae9.png</url>
      <title>DEV Community: Mike (LayerV)</title>
      <link>https://dev.to/mkr_43796678</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mkr_43796678"/>
    <language>en</language>
    <item>
      <title>Identity first, then connection: cryptographic invisibility for localhost</title>
      <dc:creator>Mike (LayerV)</dc:creator>
      <pubDate>Tue, 17 Nov 2026 19:00:23 +0000</pubDate>
      <link>https://dev.to/mkr_43796678/identity-first-then-connection-cryptographic-invisibility-for-localhost-492m</link>
      <guid>https://dev.to/mkr_43796678/identity-first-then-connection-cryptographic-invisibility-for-localhost-492m</guid>
      <description>&lt;p&gt;We've been working on a different approach to sharing local apps for reviews, demos, and testing, and wanted to show what happens before someone is allowed to connect.&lt;/p&gt;

&lt;p&gt;If you've used ngrok or other reverse tunnel to share localhost, you know how easy it is to put a local app behind a URL.&lt;/p&gt;

&lt;p&gt;LayerV built qURL to give you control over who can connect in the first place. With qURL private sharing, the app stays on your computer with zero public inbound ports. qURL establishes the reviewer's identity and checks your approval before it connects them to the app.&lt;/p&gt;

&lt;p&gt;An AI scanner with the link can reach the qURL access page. Without approval, it cannot connect to the app through qURL to identify its software or probe its routes. (that's cryptographic invisibility for your app)&lt;/p&gt;

&lt;p&gt;We wanted to test this live. So, rather than just describing the access model, we ran a live test and watched what actually happened on our local server:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What reached the app in our live demo&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We ran an app bound to &lt;code&gt;127.0.0.1:64609&lt;/code&gt; and checked its HTTP request log. The reviewer reached the qURL access page while approval was pending. The app logged &lt;strong&gt;zero requests!&lt;/strong&gt; After we approved the reviewer's passkey, they clicked open in their browser and the app served its page/favicon.&lt;/p&gt;

&lt;p&gt;That was the behavior we were looking for: the reviewer could only receive the link and request access without generating any traffic to the app itself. Only after approval did the local server see requests!&lt;/p&gt;

&lt;p&gt;If you're building something locally and want to reproduce the same test, here's the workflow.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Try it with a reviewer&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;To try this, install the qURL CLI and run an app locally. Publish it in review mode:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;qurl publish http://127.0.0.1:3000 --access review&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Send the address the CLI prints to your reviewer. Ask them to request access in their browser, then approve the request. Keep the computer awake and the app running during the review. Here's a walkthrough that shows the approval and cleanup commands you'll need:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://qurl.link/share-without-deploying?utm_source=devto&amp;amp;utm_medium=community&amp;amp;utm_campaign=first-share-pilot" rel="noopener noreferrer"&gt;Try the qurl.link walkthrough&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We are still working on making this first-share workflow easier, especially for developers who are used to simply copying a tunnel URL. Feedback on the setup experience would be super helpful!&lt;/p&gt;

&lt;p&gt;If you want to help us compare first-share instructions, come volunteer in &lt;a href="https://github.com/layervai/qurl-integrations/discussions/2062" rel="noopener noreferrer"&gt;our pilot discussion&lt;/a&gt;!&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>opensource</category>
      <category>cybersecurity</category>
      <category>security</category>
    </item>
  </channel>
</rss>
