THE CONNECTED RECORD
Ask
the work.
Find the question. Follow the work. Return to the source.
4 THREAD · 4 SYSTEMS · 31 NOTEBOOK ENTRIES · 2 QUESTIONS · 242 FILMS · 239 CHAPTERS
Search the authored text, its questions and refusals, and the films around it. Drafts keep their status. Chapters identify a topic and a time; only the 2 indexed transcripts provide spoken passages, and their automatic captions are unreviewed. This edition retrieves sources rather than generating an answer. Explore what is connected ↗
2 RESULTS FOR “It wrote the right address. Only the link was opened.”
PUBLISHED RECORD · PARTIALLY SUPPORTED · V1.0
It wrote the right address. Only the link was opened. ↗
NATIVE-001b Phase 0b gave consumer ChatGPT an index page whose access code was one relative path away, written as plain text. In both trials ChatGPT wrote the correct absolute URL and reported it inaccessible; no request reached the server, and neither answer invented a code. A frozen amendment changed only the presentation of that path to a hyperlink: both trials requested the page and returned the exact code. The presentation-dependent difference is supported in the tested setup. Whether link availability governs retrieval more generally, and which component prevented the plain-text requests, remains unresolved.
ORIGINAL SOURCE ↗PUBLISHED RECORD · PARTIALLY SUPPORTED · V1.0
It wrote the right address. Only the link was opened. / observation ↗
TWICE, THE ADDRESS WAS RIGHT. In both Phase 0b trials, the server logged ChatGPT-User/1.0 retrieving the index page. Both answers quoted the instruction and wrote out the correct absolute URL for the code page. Both then reported it inaccessible: “returned an access error when I tried to open it”; “inaccessible through my browsing tool.” The server recorded no request for either code page under any user-agent. Independent checks 41 and about 20 seconds later each returned the correct code.
ORIGINAL SOURCE ↗