mud/docs/why/text-worlds.txt
Jared Miller 25bb565091
Move notes to docs/how, docs/why, docs/lessons
how/  - how things work (terrain generation, command system)
why/  - design philosophy (telnet-first, text worlds)
lessons/ - things we learned the hard way (charset vs mtts)

Removes notes/ — DAYDREAMING.txt became DREAMBOOK.md, charset-vs-mtts
expanded into docs/lessons/ with the connect_maxwait fix documented.
2026-02-07 13:31:02 -05:00

26 lines
1.1 KiB
Text

why text
========
from the dreambook, drawing on david jacobson's research at brandeis:
narrow bandwidth doesn't impoverish experience, it enriches imagination. when
you read "a torch flickers against wet stone walls" your brain builds a
cathedral. VR hands you someone else's cathedral.
text worlds are collaborative hallucinations between the author and the reader.
the MOO community proved this for decades. LambdaMOO, MediaMOO, PMC-MOO —
people formed real relationships, built real communities, lived real social
lives through nothing but text on a terminal.
presence isn't about polygons. presence is about engagement, attention, the
feeling that you are *there* and that what happens *matters*.
what the research showed
------------------------
- presence comes from engagement, not fidelity
- identity is constructed through language (description, emotes, speech)
- community forms through shared space and shared creation
- the mask enables authenticity — removing physical cues lets people construct
identity more deliberately. that's not deception, it's freedom.