diff --git a/sosoft/generate-pdf.mjs b/sosoft/generate-pdf.mjs index b2fe96a523..818cc0721a 100644 --- a/sosoft/generate-pdf.mjs +++ b/sosoft/generate-pdf.mjs @@ -13,6 +13,7 @@ const outputPath = path.join(__dirname, "proposal.pdf"); const browser = await puppeteer.launch({ headless: true, + executablePath: process.env.PUPPETEER_EXECUTABLE_PATH || "/usr/sbin/chromium-browser", args: ["--no-sandbox", "--disable-setuid-sandbox"], }); @@ -23,7 +24,7 @@ await page.pdf({ path: outputPath, format: "Letter", printBackground: true, - margin: { top: "0.9in", bottom: "0.9in", left: "1in", right: "1in" }, + margin: { top: "0.65in", bottom: "0.65in", left: "0.75in", right: "0.75in" }, }); await browser.close(); diff --git a/sosoft/proposal.html b/sosoft/proposal.html index dbd67277e6..b5d517c1c5 100644 --- a/sosoft/proposal.html +++ b/sosoft/proposal.html @@ -3,241 +3,529 @@
--I want to use this cycle to develop the social choreography of Aesthetic Computer (AC) — the open-source creative computing platform I've been building since 2021. AC is a mobile-first runtime and social network where users write, publish, and share small interactive programs called pieces. It already has the technical infrastructure for social software: real-time chat, @handles with custom colors, ephemeral status updates (moods), a pixel painting gallery, a built-in Lisp dialect (KidLisp) for generative art, multiplayer WebSocket sessions, and user profiles that track creative output. +I'm submitting Aesthetic Computer (AC) — the open-source creative computing platform I've been building since 2021 — as a social software project in active development. I'm not proposing to build a new thing for this cycle. I'm bringing the thing I'm already building into the room for dialogue, feedback, and critical exchange as I continue to develop it alongside its community.
-What I haven't had the chance to develop is the social composition — deliberate structures for how people use this system together. The platform has 351 built-in pieces and ~2,800 registered handles, but the social dynamics are still largely emergent. I'd like to design and test specific social scores: structured rituals like a daily painting circle, weekly piece exchanges where members fork and remix each other's published programs, collaborative KidLisp jams, and constraint-based chat performances. I want to see what happens when a committed group performs these scores together over 10 weeks. +AC is a mobile-first runtime and social network where users write, publish, and share small interactive programs called pieces. It has real-time chat, @handles with per-character color customization, ephemeral status updates (moods mirrored to Bluesky via ATProto), a pixel painting system, a built-in Lisp dialect (KidLisp), multiplayer WebSocket sessions, and user profiles that track creative output. The codebase is open source with 4+ years of continuous development.
-Concretely, I'd build new AC pieces during the cycle — a cohort dashboard, multiplayer collaborative tools, and score templates that define social rules as playable software. I'd also write a "Write a Score" guide that documents how to compose social structures on the platform, parallel to AC's existing "Write a Piece" programming guide. +The score is simple: I develop AC in the open over 10 weeks, sharing what I'm working on, what decisions I'm facing, and what the community is doing on the platform. The cohort engages as users and as critics — trying the tools, reading the design choices, and giving me feedback I can't get from inside the project.
--The immediate audience is this cohort. The scores I want to test need real people showing up regularly — you can't evaluate social software alone. Longer term, anything built during the cycle would be live on the public platform for AC's existing community, and the documentation would be reusable for other educators running creative computing workshops. +I've been deep inside AC's architecture for years. I know how the systems work. What I lack is outside perspective on the social design — the questions I can't answer alone:
++These questions require sustained dialogue, not a single usability test. A cohort of practitioners thinking about social software from different angles is the right context for this kind of exchange. +
+ +SCORE.md; the process is as legible as the product
-AC's SCORE.md already uses the metaphor of a musical score to organize the project — the platform's interface is designed to function like an instrument where users discover memorizable paths, build literacy through play, and eventually improvise. Casey's framing of "scores for social software" maps directly onto this. I've been building the instrument; this cycle is a chance to compose for it with peers who are thinking about similar questions from different angles.
+Casey's framing of "scores for social software" maps directly onto how I already think about AC. The platform's SCORE.md literally uses the metaphor of a musical score to organize the project. The interface is designed to work like an instrument — users discover memorizable paths, build literacy through play, and eventually improvise. But I've been composing alone. This cycle is a chance to compose in conversation.
-I also want the critical feedback. I've been deep in the technical architecture for years and need outside eyes on the social design — what feels inviting, what's confusing, what rituals actually sustain participation. A flat cohort of practitioners working on their own social software projects is the right context for that kind of dialogue. +I'm at a specific inflection point. The technical infrastructure is mature. The question now is about social design: how do the features I've built actually shape the way people relate to each other and to creative computing? That's best answered through dialogue with people thinking critically about social software, not through more engineering.
-I'm an artist, educator, and software developer. I build software as a medium for art and education. Before AC, I created No Paint (2020), a pixel art tool whose community of non-technical users taught me how people learn computing through social participation in software they love. AC extends that into a full platform: anyone can write, publish, and share interactive programs at a URL. The codebase is open source and has been in continuous development for 4+ years. +I'm an artist, educator, and software developer. Before AC, I created No Paint (2020), a pixel art tool whose community of non-technical users taught me how people learn computing through social participation in software they love. AC extends that into a full platform: anyone can write, publish, and share interactive programs at a URL.
-I teach creative computing and have used AC as infrastructure in courses and workshops. +I teach creative computing and have used AC as infrastructure in courses and workshops. My interest in social software comes from watching people learn computation through social participation — first in No Paint, now in AC. I'm bringing this not as a finished project but as an ongoing practice I want to develop through critical exchange.
- - -- Live data from AC's MongoDB cluster as of March 2, 2026. This is the material a score composes over. -
+- Who makes things: - 1,067 users have painted · - 997 have posted moods · - 59 have written KidLisp · +
+ Who makes things: + 1,067 have painted · + 997 have posted moods · + 59 have written KidLisp · 19 have published pieces
-- Every document ties back to an authenticated user. Every user has a profile that counts their contributions. The question for this cycle: what social structures — what scores — can make these numbers move together instead of in isolation? -
+qxlDT5{uh9Cq^kSZHkEplixzHn-
zhuZ$$7Ll}mck*MdRLTU?YTrxkHv4y%^cR^`>$dE@wOs5W_mXFlE2XX8dfgBI9%YiL
z-|x|0vww@<<|$7!c}kat$a3V{)fX>)d3*2POX`KPu3kY)Pp{rvaz18~$L&uCx9Xis
zF*JL6>|E!Z2${(ljF(j|K8{u^H00J@Bkmq9IH}lrQKrGRDc8>(&5c`gXSdUnmx@Y-
zosNsNcSU;tT^~?TG55;JJ6n>rFRA&S_~H9+{$}pZ#N_0=?+!nB!1FasF6_0-kw>EC
zXEZ-9a$V!=Uwzl!sZ=u9_u<(cf|<1z8)RMH{S^GyZ@9O!TsFt7WX-jxn3(S!>X(x>
z?3->LyR&LbN|Ug7)5_kpr^G9dwPpov3|q6&Qg@4Qc6p1)9I5b)F`w>sJ?*~Jb5nbL
z(B?h=O^ueObn>>EMaIAH*PW+qdtUUv+p;^lqIK$@{zg6Hn06z~Rz1!#a*IvNw=HX#
zKQIQdKiC@kc&`wPFtZMeN#Y;d18X9+m2x(E=1%w6%;0#2f$P84qW6p|W+rSn H6#kOCFR=wPkKS_3{tH+4=GX7dB0QFaP6`LBQk4^QGrZ-(B9^R6m{L
zL7ffboOi1}N5=VC?zNr#eBPcfMJH`JKkfaqy6ZRlytTaZB{{x!G4jO=zxkQ@@RfA^
z9-{-V=P}M(zdg|A8_xl7$<=Sm{Cp~dpXc3-v;{}f-$|}G!|!p1UnjJs@$$?@q4%rS
zJXo3D&>q&s;OD7Zs6Lfp-l`*SRT%vDYV5eJ#Wk-g@B^EzmG|?1jq+#r#C#}YY%DF_
zvvdEC{J&c+WTh=Qy4m~u-+%Yx|LNJ5R&D!Mm&UMW&yKH8E?wUKPV&Haew`WeKbkxQ
z5*c`zdFQ>J_x-bC$dgOj+PWW#PQ6sxxBJx7Kf%YX>$mJY^{?@~l+?;~*-b&N(tGdw
zbBFtLU(r5%50tHL7&H97VVn@``BpaUd^KCr{{v!O1_s-Urh{F5s~Mty}EQ8xHDWfFfeiH^2BFdl=@+OGt65e80YP
z{)J}HfSBY1?f17%A3mUXeR4Y^Kl4ldN|k_<%!j}6o7gC<_^!L0#r1qDxa25&yzPOg
z^j}CM8zOeJt#`9to5wKk)0(%;4|KzrDs=dnnPD;fz@Q=K!Ndh&EbrwrW=NuxcPW>&
z&3?feSMRQWh>xt;YVa~tPTo-{
z@USan;NxT!G^paZ?k`>2zhY%z;#-ij_vJ}^@Ie|=J@vht0eMXI=e&syyX!#(&71jR
zVlzLVF@JK(m|63mwDoS*J|E {Ef9J2*
zq5qLSd9j
z0yOOp8q08~D*FD++VAhbzdnr^VJ`9Nef=tbc#k=L)3$e#8fSzg-pjvO&+{AFOYk{;
z`xmsA0G|AZbkbgZcFEVc{Fhmf&0;wRvmdyU$OuvSvFCgK!=?AxAA)AlOuzBi?6_>p
ztlIxxo?$)bqsxbyj>~tH6e=-6W^RZK_}~Zs8abGQ;Q?RWKapW3?+wtLK1vSgyJ0+G
zpX7=+@+Z#m7br^1DF%