Monorepo for Aesthetic.Computer aesthetic.computer
4
fork

Configure Feed

Select the types of activity you want to include in your feed.

feat: add "The URL Tradition" paper

Traces URL-addressability as a medium property in creative computing:
HyperCard → Web → net.art → Processing → Scratch → Glitch → p5.js →
AC's prompt-as-address-bar. 4pp, 11 citations, builds clean.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

+464
+1
papers/SCORE.md
··· 40 40 41 41 | Paper | Format | PDF | Source | 42 42 |-------|--------|-----|--------| 43 + | The URL Tradition | arXiv (LaTeX) | `arxiv-url-tradition/url-tradition.pdf` | `arxiv-url-tradition/url-tradition.tex` | 43 44 | The Potter and the Prompt | arXiv (LaTeX) | `arxiv-holden/holden.pdf` | `arxiv-holden/holden.tex` | 44 45 | Two Departments, One Building | arXiv (LaTeX) | `arxiv-ucla-arts/ucla-arts.pdf` | `arxiv-ucla-arts/ucla-arts.tex` | 45 46 | Handle Identity on the AT Protocol | arXiv (LaTeX) | `arxiv-identity/identity.pdf` | `arxiv-identity/identity.tex` |
+91
papers/arxiv-url-tradition/references.bib
··· 1 + @inproceedings{atkinson1987hypercard, 2 + author = {Atkinson, Bill}, 3 + title = {{HyperCard}}, 4 + booktitle = {Apple Computer}, 5 + year = {1987}, 6 + note = {Shipped free with every Macintosh from 1987--1992}, 7 + } 8 + 9 + @article{berners-lee1994www, 10 + author = {Berners-Lee, Tim and Cailliau, Robert and Luotonen, Ari and Nielsen, Henrik Frystyk and Secret, Arthur}, 11 + title = {The {World-Wide Web}}, 12 + journal = {Communications of the ACM}, 13 + volume = {37}, 14 + number = {8}, 15 + pages = {76--82}, 16 + year = {1994}, 17 + } 18 + 19 + @misc{berners-lee1998cool, 20 + author = {Berners-Lee, Tim}, 21 + title = {Cool {URIs} Don't Change}, 22 + year = {1998}, 23 + note = {\url{https://www.w3.org/Provider/Style/URI}}, 24 + } 25 + 26 + @book{reas2007processing, 27 + author = {Reas, Casey and Fry, Ben}, 28 + title = {Processing: A Programming Handbook for Visual Designers and Artists}, 29 + publisher = {MIT Press}, 30 + year = {2007}, 31 + } 32 + 33 + @inproceedings{resnick2009scratch, 34 + author = {Resnick, Mitchel and Maloney, John and Monroy-Hern{\'a}ndez, Andr{\'e}s and Rusk, Natalie and Eastmond, Evelyn and Brennan, Karen and Millner, Amon and Rosenbaum, Eric and Silver, Jay and Silverman, Brian and Kafai, Yasmin}, 35 + title = {Scratch: Programming for All}, 36 + journal = {Communications of the ACM}, 37 + volume = {52}, 38 + number = {11}, 39 + pages = {60--67}, 40 + year = {2009}, 41 + } 42 + 43 + @book{nelson1974computer, 44 + author = {Nelson, Ted}, 45 + title = {Computer Lib / Dream Machines}, 46 + publisher = {Self-published}, 47 + year = {1974}, 48 + note = {Revised edition: Tempus Books/Microsoft Press, 1987}, 49 + } 50 + 51 + @book{connor2019artanthology, 52 + author = {Connor, Michael and Dean, Aria and Espenschied, Dragan}, 53 + title = {The Art Happens Here: Net Art Anthology}, 54 + publisher = {Rhizome}, 55 + year = {2019}, 56 + } 57 + 58 + @misc{dash2017glitch, 59 + author = {Dash, Anil}, 60 + title = {Introducing {Glitch}}, 61 + year = {2017}, 62 + note = {\url{https://glitch.com}. Formerly Fog Creek's HyperDev/Gomix}, 63 + } 64 + 65 + @misc{mccarthy2015p5js, 66 + author = {McCarthy, Lauren}, 67 + title = {p5.js}, 68 + year = {2014}, 69 + note = {\url{https://p5js.org}. Web Editor launched 2018}, 70 + } 71 + 72 + @misc{scudder2026ac, 73 + author = {Scudder, Jeffrey}, 74 + title = {Aesthetic Computer '26}, 75 + year = {2026}, 76 + note = {\url{https://aesthetic.computer}}, 77 + } 78 + 79 + @misc{atproto2024oauth, 80 + author = {{Bluesky PBLLC}}, 81 + title = {{AT Protocol} {OAuth} Specification}, 82 + year = {2024}, 83 + note = {\url{https://atproto.com/specs/oauth}}, 84 + } 85 + 86 + @misc{scudder2026os, 87 + author = {Scudder, Jeffrey}, 88 + title = {{AC Native OS} '26}, 89 + year = {2026}, 90 + note = {\url{https://aesthetic.computer}. Bare-metal Linux for surplus laptops}, 91 + }
+362
papers/arxiv-url-tradition/url-tradition.tex
··· 1 + % !TEX program = xelatex 2 + \documentclass[10pt,letterpaper,twocolumn]{article} 3 + 4 + % === GEOMETRY === 5 + \usepackage[top=0.75in, bottom=0.75in, left=0.75in, right=0.75in]{geometry} 6 + 7 + % === FONTS === 8 + \usepackage{fontspec} 9 + \usepackage{unicode-math} 10 + 11 + \setmainfont{Latin Modern Roman} 12 + \setsansfont{Latin Modern Sans} 13 + 14 + % Custom AC fonts 15 + \newfontfamily\acbold{ywft-processing-bold}[ 16 + Path=../../system/public/type/webfonts/, 17 + Extension=.ttf 18 + ] 19 + \newfontfamily\aclight{ywft-processing-light}[ 20 + Path=../../system/public/type/webfonts/, 21 + Extension=.ttf 22 + ] 23 + \setmonofont{Latin Modern Mono}[Scale=0.85] 24 + 25 + % === PACKAGES === 26 + \usepackage{xcolor} 27 + \usepackage{titlesec} 28 + \usepackage{enumitem} 29 + \usepackage{booktabs} 30 + \usepackage{tabularx} 31 + \usepackage{multicol} 32 + \usepackage{fancyhdr} 33 + \usepackage{hyperref} 34 + \usepackage{graphicx} 35 + \graphicspath{{figures/}{../../papers/arxiv-ac/figures/}} 36 + \usepackage{ragged2e} 37 + \usepackage{microtype} 38 + \usepackage{listings} 39 + \usepackage{natbib} 40 + \usepackage[colorspec=0.92]{draftwatermark} 41 + 42 + % === COLORS (AC palette) === 43 + \definecolor{acpink}{RGB}{180,72,135} 44 + \definecolor{acpurple}{RGB}{120,80,180} 45 + \definecolor{acdark}{RGB}{64,56,74} 46 + \definecolor{acgray}{RGB}{119,119,119} 47 + \definecolor{draftcolor}{RGB}{180,72,135} 48 + 49 + % === DRAFT WATERMARK === 50 + \DraftwatermarkOptions{ 51 + text=WORKING DRAFT, 52 + fontsize=3cm, 53 + color=draftcolor!18, 54 + angle=45, 55 + pos={0.5\paperwidth, 0.5\paperheight} 56 + } 57 + 58 + % === JS SYNTAX COLORS === 59 + \definecolor{jskw}{RGB}{119,51,170} 60 + \definecolor{jsfn}{RGB}{0,136,170} 61 + \definecolor{jsstr}{RGB}{170,120,0} 62 + \definecolor{jsnum}{RGB}{204,0,102} 63 + \definecolor{jscmt}{RGB}{102,102,102} 64 + 65 + % === HYPERREF === 66 + \hypersetup{ 67 + colorlinks=true, 68 + linkcolor=acpurple, 69 + urlcolor=acpurple, 70 + citecolor=acpurple, 71 + pdfauthor={@jeffrey}, 72 + pdftitle={The URL Tradition: Addressable Creative Computing from HyperCard to Aesthetic Computer}, 73 + } 74 + 75 + % === SECTION FORMATTING === 76 + \titleformat{\section} 77 + {\normalfont\bfseries\normalsize\uppercase} 78 + {\thesection.} 79 + {0.5em} 80 + {} 81 + \titlespacing{\section}{0pt}{1.2em}{0.3em} 82 + 83 + \titleformat{\subsection} 84 + {\normalfont\bfseries\small} 85 + {\thesubsection} 86 + {0.5em} 87 + {} 88 + \titlespacing{\subsection}{0pt}{0.8em}{0.2em} 89 + 90 + % === HEADER/FOOTER === 91 + \pagestyle{fancy} 92 + \fancyhf{} 93 + \renewcommand{\headrulewidth}{0pt} 94 + \fancyhead[C]{\footnotesize\color{acpink}\textit{Working Draft --- not for citation}} 95 + \fancyfoot[C]{\footnotesize\thepage} 96 + 97 + % === CUSTOM COMMANDS === 98 + \newcommand{\acdot}{{\color{acpink}.}} 99 + \newcommand{\ac}{\textsc{Aesthetic.Computer}} 100 + \newcommand{\code}[1]{\texttt{#1}} 101 + 102 + % Random caps for Aesthetic.Computer branding 103 + \newcount\acrandtmp 104 + \newcommand{\acrandletter}[2]{% 105 + \acrandtmp=\uniformdeviate 2\relax 106 + \ifnum\acrandtmp=0\relax#1\else#2\fi% 107 + } 108 + \newcommand{\acrandname}{% 109 + \acrandletter{a}{A}\acrandletter{e}{E}\acrandletter{s}{S}\acrandletter{t}{T}% 110 + \acrandletter{h}{H}\acrandletter{e}{E}\acrandletter{t}{T}\acrandletter{i}{I}% 111 + \acrandletter{c}{C}{\color{acpink}.}\acrandletter{c}{C}\acrandletter{o}{O}% 112 + \acrandletter{m}{M}\acrandletter{p}{P}\acrandletter{u}{U}\acrandletter{t}{T}% 113 + \acrandletter{e}{E}\acrandletter{r}{R}% 114 + } 115 + 116 + % === LISTINGS === 117 + \lstdefinelanguage{acjs}{ 118 + morekeywords=[1]{function,export,const,let,var,return,if,else,new,async,await,import,from}, 119 + morekeywords=[2]{wipe,ink,line,box,circle,write,screen,params,colon,jump,send,store,net,sound,speaker,system}, 120 + sensitive=true, 121 + morecomment=[l]{//}, 122 + morestring=[b]", 123 + morestring=[b]', 124 + morestring=[b]`, 125 + escapeinside={|}{|}, 126 + } 127 + 128 + \lstdefinestyle{acjsstyle}{ 129 + language=acjs, 130 + keywordstyle=[1]\color{jskw}\bfseries, 131 + keywordstyle=[2]\color{jsfn}\bfseries, 132 + commentstyle=\color{jscmt}\itshape, 133 + stringstyle=\color{jsstr}, 134 + } 135 + 136 + \lstset{ 137 + basicstyle=\ttfamily\small, 138 + breaklines=true, 139 + frame=single, 140 + rulecolor=\color{acgray!30}, 141 + backgroundcolor=\color{acgray!5}, 142 + xleftmargin=0.5em, 143 + xrightmargin=0.5em, 144 + aboveskip=0.5em, 145 + belowskip=0.5em, 146 + } 147 + 148 + % === LIST SETTINGS === 149 + \setlist[itemize]{nosep, leftmargin=1.2em, itemsep=0.1em} 150 + \setlist[enumerate]{nosep, leftmargin=1.2em} 151 + 152 + % === COLUMN SEPARATION === 153 + \setlength{\columnsep}{1.8em} 154 + 155 + % === PARAGRAPH SETTINGS === 156 + \setlength{\parindent}{1em} 157 + \setlength{\parskip}{0.3em} 158 + 159 + % Hyphenation for narrow two-column layout 160 + \tolerance=800 161 + \emergencystretch=1em 162 + \hyphenpenalty=50 163 + 164 + \begin{document} 165 + 166 + % ============ TITLE BLOCK ============ 167 + 168 + \twocolumn[{% 169 + \begin{center} 170 + \includegraphics[height=4em]{pals}\par\vspace{0.5em} 171 + {\acbold\fontsize{24pt}{28pt}\selectfont\color{acdark} The URL Tradition}\par 172 + \vspace{0.2em} 173 + {\aclight\fontsize{11pt}{13pt}\selectfont\color{acpink} Addressable Creative Computing from HyperCard to Aesthetic Computer}\par 174 + \vspace{0.6em} 175 + {\normalsize\href{https://prompt.ac/@jeffrey}{@jeffrey}}\par 176 + {\small\color{acgray} Aesthetic.Computer}\par 177 + {\small\color{acgray} ORCID: \href{https://orcid.org/0009-0007-4460-4913}{0009-0007-4460-4913}}\par 178 + \vspace{0.3em} 179 + {\small\color{acpurple} \url{https://aesthetic.computer}}\par 180 + \vspace{0.6em} 181 + \rule{\textwidth}{1.5pt} 182 + \vspace{0.5em} 183 + \end{center} 184 + 185 + \begin{center} 186 + {\small\color{acpink}\textbf{[ working draft --- not for citation ]}} 187 + \end{center} 188 + \vspace{0.3em} 189 + 190 + \begin{quote} 191 + \small\noindent\textbf{Abstract.} 192 + Creative computing environments have historically been \emph{opaque}: the state of the machine is accessible only to the person sitting in front of it. HyperCard stacks lived on a single disk. Processing sketches compiled to local executables. Scratch projects required a portal to find. The URL changes this. When every creative artifact is a URL---typeable, shareable, memorizable---the artifact escapes the machine and enters culture as an address. This paper traces a ``URL tradition'' in creative computing: the line from HyperCard's card/stack metaphor through the web's addressable document model, Glitch's instant remix URLs, p5.js's Web Editor links, and Aesthetic Computer's core design decision that every piece is a top-level path. We argue that URL-addressability is not a feature but a \emph{medium property}---one that reshapes authorship, distribution, pedagogy, and social interaction around creative code. AC extends the tradition by making the URL the primary interface: there is no menu, no file picker, no project list. You type a word and you are in the piece. The prompt \emph{is} the address bar. 193 + \end{quote} 194 + \vspace{0.5em} 195 + }] 196 + 197 + % ============ 1. INTRODUCTION ============ 198 + \section{Introduction} 199 + 200 + Every creative computing environment makes a choice about addressing. How does a user find, share, and return to a piece of work? The answer to this question shapes the entire character of the system. 201 + 202 + HyperCard~\citep{atkinson1987hypercard} addressed content by \emph{card} and \emph{stack}---spatial metaphors bound to a single machine. A stack was a file. To share it, you copied a floppy disk. The brilliant interface metaphor was undermined by a distribution model that assumed physical proximity. 203 + 204 + The World Wide Web~\citep{berners-lee1994www} introduced the URL: a universal, human-readable address for any document on any networked machine. Tim Berners-Lee's design insisted that addresses be \emph{cool}---short, stable, and guessable~\citep{berners-lee1998cool}. This was not an implementation detail. It was a social contract: if you give someone a URL, it should still work when they try it. 205 + 206 + Creative computing environments that embrace the URL inherit this contract. Those that don't---that hide work behind login walls, project IDs, or native app containers---break it. This paper argues that URL-addressability constitutes a tradition in creative computing, one that Aesthetic Computer consciously extends. 207 + 208 + % ============ 2. THE STACK WITHOUT A URL ============ 209 + \section{The Stack Without a URL} 210 + 211 + \subsection{HyperCard (1987)} 212 + 213 + HyperCard gave non-programmers the power to build interactive software through a card-and-stack metaphor. Each card was a screen; each stack was a program. The system was profoundly democratic: it shipped free with every Macintosh, and its scripting language (HyperTalk) was designed to read like English~\citep{atkinson1987hypercard}. 214 + 215 + But a HyperCard stack had no address. It was a file on a disk. Sharing meant copying. Discovery meant someone physically handing you a floppy or, later, downloading from a BBS. The stack was powerful but \emph{landlocked}---trapped on the machine that made it. 216 + 217 + \subsection{Processing (2001)} 218 + 219 + Processing~\citep{reas2007processing} brought creative coding to a generation of artists and designers. A sketch was a \code{.pde} file that compiled to a Java applet or, later, a standalone application. Sharing meant exporting and uploading. The Processing community website provided a gallery, but each project was behind a portal: click, wait, load. 220 + 221 + Processing's contribution was making code \emph{writable} for artists. But it did not make the resulting work \emph{addressable} in the web's sense. A Processing sketch was a destination, not a link. 222 + 223 + \subsection{Scratch (2007)} 224 + 225 + Scratch~\citep{resnick2009scratch} solved the sharing problem within its own ecosystem: every project gets a numbered URL on \code{scratch.mit.edu}. But these URLs are opaque---\code{scratch.mit.edu/projects/12345678}---and require the Scratch runtime to view. The address exists but it is not \emph{cool}: it encodes nothing about the content, and it cannot be guessed or remembered. 226 + 227 + % ============ 3. THE URL ENTERS CREATIVE COMPUTING ============ 228 + \section{The URL Enters Creative Computing} 229 + 230 + \subsection{The Web as Creative Medium} 231 + 232 + The web itself was the first URL-native creative computing environment. A hand-written HTML page at \code{geocities.com/\textasciitilde{}user/art.html} was simultaneously a creative artifact and a shareable address. The early web understood something that later platforms forgot: \emph{making} and \emph{addressing} should be the same act~\citep{nelson1974computer}. 233 + 234 + Net.art practitioners of the 1990s---JODI, Olia Lialina, Vuk \'{C}osi\'{c}---exploited this identity. The URL was material. Lialina's \emph{My Boyfriend Came Back from the War} (1996) was inseparable from its address. The work \emph{was} the URL. The Art Happens Here anthology documents this moment when the address became the medium~\citep{connor2019artanthology}. 235 + 236 + \subsection{Glitch (2017)} 237 + 238 + Glitch~\citep{dash2017glitch} made the URL instant. Every project is live at \code{project-name.glitch.me} from the moment it is created. There is no deploy step, no build process, no publish button. The URL is not a reward for finishing---it is present from the first keystroke. 239 + 240 + Glitch also made the URL \emph{forkable}: the ``Remix'' button creates a new project with a new URL, preserving the lineage. This turns the URL into a social object. Sharing a Glitch URL is an invitation to modify, not just to view. 241 + 242 + \subsection{p5.js Web Editor (2018)} 243 + 244 + The p5.js Web Editor~\citep{mccarthy2015p5js} brought Processing's creative coding model into the browser. Each sketch gets a URL. But like Scratch, the URLs are opaque (\code{editor.p5js.org/user/sketches/abc123}). The editor must be loaded to run the sketch. The URL points to a \emph{tool}, not directly to the \emph{work}. 245 + 246 + % ============ 4. AC: THE PROMPT IS THE ADDRESS BAR ============ 247 + \section{AC: The Prompt Is the Address Bar} 248 + 249 + Aesthetic Computer~\citep{scudder2026ac} takes the URL tradition to its logical conclusion. Every piece is a top-level path: 250 + 251 + \begin{center} 252 + \code{aesthetic.computer/notepat}\\ 253 + \code{aesthetic.computer/wand}\\ 254 + \code{aesthetic.computer/song} 255 + \end{center} 256 + 257 + There is no file browser, no project list, no dashboard. The interface is a prompt---a blinking cursor that accepts a word. That word becomes the URL. The prompt is the address bar. 258 + 259 + \subsection{Memorizable Paths} 260 + 261 + AC paths are designed to be \emph{memorizable}. Like phone numbers before contacts lists, like radio frequencies before presets, the path is something you carry in your head. You don't bookmark \code{aesthetic.computer/notepat}; you remember the word ``notepat.'' You can tell someone at a party, write it on a napkin, or shout it across a room. 262 + 263 + This is a deliberate inversion of the trend toward opaque identifiers. Scratch uses numbers. Glitch uses generated names. p5.js uses hashes. AC uses \emph{words}---human words, chosen by the author, occupying the top-level namespace. 264 + 265 + \subsection{Parameters as Colons} 266 + 267 + AC extends the URL with colon-separated parameters: 268 + 269 + \begin{center} 270 + \code{aesthetic.computer/line:red}\\ 271 + \code{aesthetic.computer/prompt:monocles}\\ 272 + \code{aesthetic.computer/share:notepat} 273 + \end{center} 274 + 275 + Colons were chosen over slashes or query strings because they read as \emph{modifiers}, not \emph{hierarchy}. ``line red'' not ``line / red.'' The colon is conversational. It preserves the single-word-at-top-level constraint while allowing infinite parameterization. 276 + 277 + \subsection{User Pieces} 278 + 279 + Published pieces live under handles: 280 + 281 + \begin{center} 282 + \code{aesthetic.computer/@niki/flower}\\ 283 + \code{aesthetic.computer/@sage/drum} 284 + \end{center} 285 + 286 + The \code{@} prefix signals authorship. The handle is an address within an address---a person's namespace inside the platform's namespace. This mirrors the AT Protocol's handle system~\citep{atproto2024oauth} and the fediverse's \code{@user@domain} convention, extending the URL tradition into identity. 287 + 288 + % ============ 5. URL AS MEDIUM PROPERTY ============ 289 + \section{URL as Medium Property} 290 + 291 + We argue that URL-addressability is not a feature added to a creative computing environment but a \emph{medium property} that reshapes every aspect of how the environment is used. 292 + 293 + \subsection{Pedagogy} 294 + 295 + A teacher says: ``Go to aesthetic.computer/notepat.'' Every student is instantly in the same piece. No login required. No app to install. No instructions to follow beyond typing a URL. The URL \emph{is} the lesson plan's entry point. 296 + 297 + Compare: ``Open Scratch, search for project 12345678, click Run.'' Or: ``Download Processing, open the .pde file I emailed you, click Play.'' Each additional step is a student lost. 298 + 299 + \subsection{Distribution} 300 + 301 + A URL is a distribution channel. It works in a text message, a QR code, a tweet, an email signature, a physical poster. It crosses every medium boundary because it \emph{is} the lowest common denominator of the networked world. 302 + 303 + AC's \code{share} piece generates a QR code for any other piece: 304 + 305 + \begin{center} 306 + \code{aesthetic.computer/share:notepat} 307 + \end{center} 308 + 309 + The QR code resolves to the piece URL. The piece runs in any browser. No app store, no install, no account required. 310 + 311 + \subsection{Social Interaction} 312 + 313 + When every piece is a URL, conversation becomes navigation. In AC's chat system, typing a piece name in backticks creates a clickable link. Saying ``try \code{wand}'' in chat is the same as sharing a URL. The social layer and the addressing layer collapse into one. 314 + 315 + \subsection{Authorship} 316 + 317 + Publishing a piece on AC means claiming a word. \code{@niki/flower} is Niki's flower. The URL is the signature. Unlike a gallery wall label or a credits screen, the URL is present in every context where the work appears---in the browser bar, in the share link, in the QR code. Authorship is encoded in the address, not metadata. 318 + 319 + % ============ 6. THE TRADITION ============ 320 + \section{The Tradition} 321 + 322 + The URL tradition in creative computing runs: 323 + 324 + \begin{enumerate} 325 + \item \textbf{HyperCard} (1987): cards and stacks, no address, bound to disk. 326 + \item \textbf{The Web} (1991): every document is a URL. The address \emph{is} the work. 327 + \item \textbf{Net.art} (1995--): artists exploit the URL as material and medium. 328 + \item \textbf{Processing} (2001): creative coding, but no native URL. Export required. 329 + \item \textbf{Scratch} (2007): project URLs, but opaque and runtime-dependent. 330 + \item \textbf{Glitch} (2017): instant URLs, forkable, live from first keystroke. 331 + \item \textbf{p5.js Editor} (2018): sketch URLs, but editor-dependent and opaque. 332 + \item \textbf{Aesthetic Computer} (2022): the prompt \emph{is} the address bar. Every piece is a memorizable top-level path. No intermediary. 333 + \end{enumerate} 334 + 335 + Each step makes the URL more central. AC's contribution is making the URL \emph{the only interface}. There is no other way in. You type a word. You are there. 336 + 337 + % ============ 7. BERNERS-LEE'S COOL URIS ============ 338 + \section{Cool URIs and the Forgetting Web} 339 + 340 + Berners-Lee wrote in 1998: ``Cool URIs don't change''~\citep{berners-lee1998cool}. The web was designed for permanence. Every URL was supposed to be a promise. 341 + 342 + The modern web breaks this promise constantly. Social media posts get deleted. SaaS tools sunset. Startups fold. The creative computing platforms of the 2010s---many built on venture funding---are particularly fragile. When a platform dies, every URL it ever issued dies with it. 343 + 344 + AC confronts this by being open-source, self-hostable, and URL-first. If \code{aesthetic.computer} disappears, the pieces still run on any instance. The URL is portable because the runtime is portable. The cool URI survives because it is not bound to a single server---it is bound to a word. 345 + 346 + % ============ 8. CONCLUSION ============ 347 + \section{Conclusion} 348 + 349 + The URL is the most important interface in computing. It is the only universal addressing scheme that works across every device, every platform, every medium. Creative computing environments that embrace the URL---that make every artifact addressable, shareable, memorizable---participate in a tradition that runs from the web itself through net.art, Glitch, and now Aesthetic Computer. 350 + 351 + AC's design makes the URL not just present but \emph{primary}. The prompt is the address bar. The piece name is the URL. The URL is the identity, the distribution channel, the pedagogical entry point, and the social object. There is nothing else. 352 + 353 + This is not minimalism for its own sake. It is the recognition that in a networked world, the most powerful thing a creative tool can give you is a \emph{good address}. 354 + 355 + \vspace{1em} 356 + \noindent\rule{\columnwidth}{0.5pt} 357 + 358 + % ============ REFERENCES ============ 359 + \bibliographystyle{plainnat} 360 + \bibliography{references} 361 + 362 + \end{document}
+10
papers/cli.mjs
··· 185 185 siteName: "potter-and-prompt-26-arxiv", 186 186 title: "The Potter and the Prompt", 187 187 }, 188 + "arxiv-url-tradition": { 189 + base: "url-tradition", 190 + siteName: "url-tradition-26-arxiv", 191 + title: "The URL Tradition", 192 + }, 188 193 }; 189 194 190 195 function texName(base, lang) { ··· 597 602 detail: "John Holden's Proto-Cognitive Music Theory and Aesthetic Computer &middot; arXiv 7pp", 598 603 abstract: 599 604 "The Potter and the Prompt argues that AC independently converges on the core principles of John Holden's 1770 proto-cognitive music theory. It proposes AC as a computational laboratory for advancing Holden's unfinished program on grouping, attention, and the module.", 605 + }, 606 + "url-tradition-26-arxiv": { 607 + detail: "Addressable Creative Computing from HyperCard to Aesthetic Computer &middot; arXiv 5pp", 608 + abstract: 609 + "The URL Tradition traces how URL-addressability reshapes creative computing. From HyperCard's landlocked stacks to AC's prompt-as-address-bar, the paper argues the URL is not a feature but a medium property that transforms pedagogy, distribution, authorship, and social interaction.", 600 610 }, 601 611 }; 602 612