<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>QR Code on Phosphor BBS</title>
		<link>https://phosphorbbs.net/tags/qr-code/</link>
		<description>Recent content in QR Code on Phosphor BBS</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://phosphorbbs.net/tags/qr-code/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>A QR Code on a Text Screen: Pairing Phones to a BBS Without a Login</title>
				<link>https://phosphorbbs.net/blog/a-qr-code-on-a-text-screen-pairing-phones-to-a-bbs-without-a-login/</link>
				<pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://phosphorbbs.net/blog/a-qr-code-on-a-text-screen-pairing-phones-to-a-bbs-without-a-login/</guid>
				<description>&lt;p&gt;There&amp;rsquo;s a moment in every mobile-client story where the design gets embarrassing. Your BBS just grew a beautiful native iOS app — SwiftUI, an embedded terminal, SSH, the works. And then someone asks the question that matters: &lt;em&gt;how does the phone prove it&amp;rsquo;s you?&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;The boring answer is a login form on a touchscreen. Type your username. Type your password. Maybe paste a token. On a touch keyboard. For a terminal system whose whole identity is that it never needed a GUI.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
