@ -6,6 +6,22 @@ Here documentation is seen as a surface that could host principles in close cont
__Sections:__
__Sections:__
A first part of theoretical examples of technology and worlding: Trans\*feminist Servers, Zach Blas, Tiger Ding Sun, James Bridle, Soon and Geox, Richard Gabriel.
A first part of theoretical examples of technology and worlding: Trans\*feminist Servers, Zach Blas, Tiger Ding Sun, James Bridle, Soon and Cox, Richard Gabriel.
A second part of case studies. The soupboat. Avantwhatever.net. Queer Motto API. The Screenless Office. The uxn ecosystem. `list wip`
A second part of case studies. The soupboat. Avantwhatever.net. Queer Motto API. The Screenless Office. The uxn ecosystem. `list wip`
## Going with the flows
There could be several approaches for making worlds around software. Here are some keywords that refer to the kind of flow these worlding techniques activate. There are three directions: to reclaim is to demand something back: something that was stolen, or taken away, or lost, or forgotten. To reenchant means to intercept and reorientate towards different directions. To readjust a process, or to move for a different purpose. To reassure serves as a prompt to keep going. It helps making meaning, and refresh ideas. It offers way to register choices, and keep track of what has been done so far.
These labels are open and loose, overlapping and not mutually exclusive, temporary and on the move. They are meant to change, to expire fast, and going bad even faster: they require continuous treatments and repeated efforts. That's why I'm renaming them all after the _re_ prefix: to aknowledge their being in progress, again second hand, already contaminated. Borrowed by friends and foes, that had borrowed themselves from someone else. Nonetheless, they offer ways to visualize different strategies to create worlds around software.
