2026-05-03 Sun
- this morning while reading articles in Readwise, had a few ideas for how to make different types of readers App/Idea/Flyover reader. wild stuff. influenced by recent Person/bashbunni/YouTube/26/04/Why every dev needs paper notebook science vid about importance of physicality in reading.
garddiff
Filed
- stubs
- a few of my favorite things
- nerdz
- games
- Co/Nintendo/Game/Super Mario
Flyover reader
- The human brain is uniquely designed for tasks of navigation and location.
- Picture a Read/Later/App that is more like a Game/Video that lets you pick various reading modes.
- Similar to any read-it later app, one could import text.
- The app would enable one to turn the whole text into a Game/Video/Platformer where one could jump around the paragraphs like Mario
- It could also turn the whole text into a vast landscape where the words are actually plants, and one could fly over, crop-dusting with a little by-plane
- It could turn it into a long road, where the words were on the road, and one ran over them
- This could be especially fun if one was literally on a treadmill
- The game could include mechanics for commenting that would spatially embed comments
- ideas
- Math/pi/Six nines
Agent Experience (AX)
- Similar to UX or DX, AX represents the agent's experience, particularly of a software system.
- opposites
- toolz 4 readerz
- technically, apps
- categories
- Font/Tofu
- to what should we give our notes?
- terminal glyphs
- Logseq/Entity
- for some reason my rulesync/Skills related to this were doubling up the definitions of the entities. instead, the skill was intended to depend upon the logseq repository to contextualize its repo-local taxonomy. trust but verify your ai tools, y'all
- entity pages
- beautiful standards
- apps for understanding
- math