Last updated May 10, 2022

• Evergreen
• Technical

• wave function collapse for poetry
  • bringing shape-shifting text to its most literal form
  • https://oskarstalberg.com/Townscaper/ for words
  • base representation is word vectors
    • you can jiggle word vectors around
    • apply transformations to vectors (e.g. the past tense vector)
    • some sort of 1d marching cubes which modifies a vector depending on context?
      • potentially transformer related
  • image <-> text interop using CLIP/unCLIP/DALL-E?
• better search
  • searching through vectors
    • (no clue if this would work) integral images but applied to vector similarity search in text documents
    • viola-jones for text embeddings
    • https://github.com/facebookresearch/faiss
  • how do we encode sentences/paragraphs/documents as vectors?
    • https://beta.openai.com/docs/guides/embeddings/text-search-using-embeddings
    • https://github.com/ryankiros/skip-thoughts
    • https://github.com/pytorch/fairseq/tree/main/examples/data2vec
• phone as wiimote
• hand position to gesture toolkit
• baba is you but for browser interactions
  • data plane is main source of truth
    • optionally replicated using Rhizome
  • data inputs like webcam, keyboard, mouse, window size, etc.
  • relations are from data plane → data plane (no functions!)
    • e.g. x bounces off of y
  • rendering using canvas (higher performance games/interactions) or plain html elements (UI)
• data provenance
  • https://www.cs.cmu.edu/~NatProg/whyline.html
• how do we design better UI that reflects true application state?
  • https://www.scattered-thoughts.net/writing/relational-ui/
  • CRDTs as reducers over event-logs… that produce a view?
• data lensing for databases
  • using https://www.inkandswitch.com/cambria/ maybe?
  • some cool interoperability things
  • CRDTs for databases? https://archive.jlongster.com/using-crdts-in-the-wild
    • https://cse.buffalo.edu/tech-reports/2014-04.pdf
  • distributed state
• tools for thought applied to IDEs?
  • IDEs as graph editors?
• more on decentralized tech in Rhizome Proposal
• permaweb npm?
  • pinning specific code versions
• LRU blockchain
  • RBAC blockchain???
  • groups of roles
  • mutability in a window
  • permanence outside of it
  • edit only the last message you send
• recaptcha model for moderation / proof of humanity
• website inspo
  • fun interactions
    • https://victoiredouy.com/about
    • http://www.narrowdesign.com/
    • https://remix.run/
    • https://lynnandtonic.com/
    • https://thebrowser.company/
  • misc
    • https://shapefarm.net/
  • 3d
    • https://chartogne-taillet.com/en
    • https://flowersforsociety.com/
    • https://bruno-simon.com/
    • https://danny-garcia.com/
    • http://richardmattka.com/prototypes/red-shift
    • https://ventureworks.io/
    • https://henryheffernan.com/
• LayoutLM + screenshots → auto-categorization of knowledge
  • https://screenotate.com/ but with atlas recall
  • maybe turn this into an app which auto-extracts semantic info from screenshots/images on webpages and does something w it idk
  • how do we prevent https://twitter.com/rsnous/status/1130910375795277824
• Marginalia for the web? browser as a graph database, chronological browsing?
  • what if you could 3 finger swipe up on a browser to see what pages this page is connected to in a graph
  • and you could write on the margins of pages and share those with friends
    • a little annotated web
• location-based ephemeral social groups with zero-knowledge proofs on location
  • each location/city has a chat group which has a compound hash of all people in that location, derive only a boolean of whether a person is in a city or not without revealing exact location
  • when a person leaves/arrives at a city, city hash is updated
• p2p reddit w custom chain crawlers and the ability to bake keys into content
• autocomplete for rendered latex with a computer algebra system
• Conversational GPS
  • why do we even look at a screen when we can just ask for directions as if it was a normal person lol
• Discord bot for interacting with DAOs
• sound-based hashing for cryptographic verification
• google photos + olo radio (see attention economy)

• web3 action-space exploration
  • Possible referents/verses extension?
  • chain crawlers indexing smart contracts → creating logical relations
  • prolog goal-first search? how can i prove that I can transmute resource A into resource B using relations on the network?
  • suggesting what you can do with existing resources in your wallet
    • over time, emergent best-practices develop (i.e. whats the most obvious thing to do after you buy BTC, what does this NFT enable me to do?)
• DreamCoder boolsat
  • Creating a LISP-like higher-order language to exploit reusable sub-proofs in specific domains (e.g. graph colouring)
  • kinda iffy on the sat problem solver using dreamcoder, not a lot of exploitable structure in the proofs (otherwise we’d have a more reliable human method)
  • Background:
    • https://en.wikipedia.org/wiki/Boolean_satisfiability_problem
    • https://searchworks.stanford.edu/view/13250178
  • NeuroSAT Paper:
    • https://arxiv.org/pdf/1802.03685.pdf
  • DreamCoder Paper:
    • https://arxiv.org/pdf/2006.08381.pdf
    • https://www.youtube.com/watch?v=qtu0aSTDE2I
• Shale: the cloud-native scripting language
  • things to prioritize
    1. great tooling and extensibility
       1. static type hinting (great compile errors that detail relevant variables and possible fixes)
       2. full HTTP server and request engine
       3. compiles down to bytecode using LLVM (find some go/rust bindings for this)
       4. URL-based module imports
    2. easy to read code
    3. features u love
       1. pattern matching match n { ... }
       2. a block a = { ... } is just a zero-arg anon fn a = () => { ... }
       3. object and array destructuring (same as JS)
       4. option container
          1. built-in retry mechanisms on failure
          2. null coalescing for sensible defaults (converting Option[Int] to Int for example)
       5. function chaining (really just function composition) 123 -> a -> b is equivalent to b(a(123))
       6. fat arrow fns someFn = a => b
    4. proper stderr for errors (works well with UNIX pipes, can also read STDIN using input)
  • notes on syntax
    1. function chaining using the pipe ->
    2. fat arrow functions => return by default unless you include curly braces (then explicit return is required)
    3. type checking is OPTIONAL (using ::)but if annotations are provided, will be caught at compile time (default type is Unknown)
       1. explicit casting can be done using the as() function
       2. can include const to prevent mutations
• Better personal analytics
  • small js bundle
  • doesn’t sell user data!!
  • things to track
    • rough location of each user
    • total users
    • user visit distribution vs time
• living room
  • recreating communal living spaces in digital space
  • ephemerality and digital permanence

• tabfs but for emails
  • https://bazil.org/fuse/
  • https://blog.gopheracademy.com/advent-2014/fuse-zipfs/
  • listen on any email server
  • cli based for configuring backend
    • or just yaml
  • react/electron frontend
    • ability to add plugins
      • modular by design, creating workflows
• deep foveal VR rendering