<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ClaudeBridge on Defender TD5</title><link>https://td5.390er.de/claudebridge/</link><description>Recent content in ClaudeBridge on Defender TD5</description><generator>Hugo</generator><language>de</language><lastBuildDate>Sat, 25 Jul 2026 09:55:26 +0200</lastBuildDate><atom:link href="https://td5.390er.de/claudebridge/index.xml" rel="self" type="application/rss+xml"/><item><title>What the 68k Mac Needs for ClaudeBridge — Almost Nothing</title><link>https://td5.390er.de/claudebridge/guest-setup-for-claudebridge/</link><pubDate>Sat, 25 Jul 2026 09:55:26 +0200</pubDate><guid>https://td5.390er.de/claudebridge/guest-setup-for-claudebridge/</guid><description>&lt;blockquote&gt;
&lt;p&gt;The interesting answer to &amp;ldquo;what do I have to install on the vintage Mac?&amp;rdquo; is: nothing. In &lt;a href="https://td5.390er.de/claudebridge/claudebridge-2-0-on-a-1996-macintosh/"&gt;ClaudeBridge 2.0&lt;/a&gt; the old machine is a pure client. No server runs there, no daemon, no helper — the entire codebase lives on the host. The Mac sends HTTP requests and renders HTML, and that is the whole of its job.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;em&gt;Deutsche Fassung: &lt;a href="https://pit.390er.de/68000/claudebridge-2-0/gast-einrichtung-claudebridge/"&gt;Was der 68k-Mac für ClaudeBridge braucht&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Server, install instructions and source: &lt;a href="https://github.com/LoetLuemmel/ClaudeBridge"&gt;github.com/LoetLuemmel/ClaudeBridge&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;What follows are therefore two &lt;strong&gt;settings&lt;/strong&gt;, not two installations. Both already exist on any System 7.6.1 machine.&lt;/p&gt;</description></item><item><title>ClaudeBridge 2.0 — Claude on a Macintosh from 1996</title><link>https://td5.390er.de/claudebridge/claudebridge-2-0-on-a-1996-macintosh/</link><pubDate>Sat, 25 Jul 2026 09:11:59 +0200</pubDate><guid>https://td5.390er.de/claudebridge/claudebridge-2-0-on-a-1996-macintosh/</guid><description>&lt;blockquote&gt;
&lt;p&gt;A question to a language model sits on the screen. The cursor blinks in a &lt;code&gt;&amp;lt;TEXTAREA&amp;gt;&lt;/code&gt; rendered by Netscape Navigator 3, under System 7.6.1, on a machine whose architecture is older than the phrase &amp;ldquo;search engine&amp;rdquo;. Between clicking &lt;em&gt;Send to Claude&lt;/em&gt; and the answer lie thirty years of web history — and somebody has to bridge them.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;ClaudeBridge 2.0&lt;/strong&gt; is that somebody: an HTTP server running on the host that makes Claude reachable from a browser built in 1996. No porting effort, no emulation trick. The server simply speaks the language of the older shore.&lt;/p&gt;</description></item><item><title>Five Bugs in THINK C — A Benchmark for Code Assistants</title><link>https://td5.390er.de/claudebridge/five-bugs-in-think-c/</link><pubDate>Sat, 25 Jul 2026 09:10:51 +0200</pubDate><guid>https://td5.390er.de/claudebridge/five-bugs-in-think-c/</guid><description>&lt;blockquote&gt;
&lt;p&gt;How do you test whether a tool really understands Classic Mac code — or merely C? You hand it a program that compiles, looks like a hundred others from that era, and still does not work. The interesting bugs are not the ones the compiler finds.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The source below was written as a test case for the Code Assistant in &lt;a href="https://td5.390er.de/claudebridge/claudebridge-2-0-on-a-1996-macintosh/"&gt;ClaudeBridge 2.0&lt;/a&gt;. It contains five deliberate bugs, graded from &amp;ldquo;fails immediately&amp;rdquo; to &amp;ldquo;crashes eventually, under load&amp;rdquo;.&lt;/p&gt;</description></item><item><title>A Conversation with Claude on a 1996 Macintosh</title><link>https://td5.390er.de/claudebridge/a-conversation-on-a-1996-macintosh/</link><pubDate>Sat, 25 Jul 2026 09:09:31 +0200</pubDate><guid>https://td5.390er.de/claudebridge/a-conversation-on-a-1996-macintosh/</guid><description>&lt;blockquote&gt;
&lt;p&gt;A language model, a browser from 1996, and an operating system older than the word &amp;ldquo;chatbot&amp;rdquo;. This transcript records four rounds that ran over &lt;a href="https://td5.390er.de/claudebridge/claudebridge-2-0-on-a-1996-macintosh/"&gt;ClaudeBridge 2.0&lt;/a&gt; on the morning of 25 July 2026 — unedited, including the bugs they brought to light.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;em&gt;Deutsche Fassung: &lt;a href="https://pit.390er.de/68000/claudebridge-2-0/claudebridge-dialog-1996/"&gt;Ein Gespräch mit Claude auf einem Macintosh von 1996&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The server this conversation ran through: &lt;a href="https://github.com/LoetLuemmel/ClaudeBridge"&gt;github.com/LoetLuemmel/ClaudeBridge&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The screenshots here are evidence rather than decoration. Each shows the Netscape window inside the emulator, the URL in the address bar (&lt;code&gt;10.0.2.2:8080/result/n&lt;/code&gt;), and the answer as it actually rendered.&lt;/p&gt;</description></item><item><title>Five Question Marks: An Encoding Bug and the Plausible Wrong Answer</title><link>https://td5.390er.de/claudebridge/five-question-marks-encoding-bug/</link><pubDate>Sat, 25 Jul 2026 09:04:51 +0200</pubDate><guid>https://td5.390er.de/claudebridge/five-question-marks-encoding-bug/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Someone types &lt;code&gt;äöüÄÖÜß&lt;/code&gt; into a text field in Netscape Navigator 3, running under System 7.6.1. What arrives on the server is &lt;code&gt;?????? &lt;/code&gt;. Seven characters in, seven question marks out. The explanation seems obvious — and the obvious explanation is wrong.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is a short account of an encoding bug in &lt;a href="https://td5.390er.de/claudebridge/claudebridge-2-0-on-a-1996-macintosh/"&gt;ClaudeBridge 2.0&lt;/a&gt;, and of the detour taken while fixing it. The detour is the interesting part: the wrong fix looked like progress.&lt;/p&gt;</description></item></channel></rss>