notes add

_layouts/note.html

@@ -5,20 +5,20 @@ layout: default
   <article id="note-container"  class="w-50 pa3 pr0 relative z-1">
     <div class="container bg-white min-vh-100-header-comp pa3 br4 flex flex-column justify-between">
       <header>
-        <div class="note-meta flex f7 justify-between code items-center">
+        <div class="note-meta flex f7 lh-copy justify-between code items-center">
           {% if page.date_created %}
             <time class="ml3 flex-auto" datetime="{{ page.date_created | date_to_xmlschema }}">{% if page.type != 'pages' %}
-              Created on {{ page.date_created | date: "%B %-d, %Y" }}
+              Created <br> {{ page.date_created | date: "%B %-d, %Y" }}
               {% endif %}
             </time>
           {% else %}
               <time class="ml3 flex-auto" datetime="{{ page.date | date_to_xmlschema }}">{% if page.type != 'pages' %}
-              Created on {{ page.date | date: "%B %-d, %Y" }}
+              Created <br> {{ page.date | date: "%B %-d, %Y" }}
               {% endif %}
             </time>
           {% endif %}
           <time datetime="{{ page.last_modified_at | date_to_xmlschema }}">{% if page.type != 'pages' %}
-            Last updated on {{ page.last_modified_at | date: "%B %-d, %Y" }}
+            Last updated <br> {{ page.last_modified_at | date: "%B %-d, %Y" }}
             {% endif %}
           </time>
         </div>

_notes/beaker-browser.md

@@ -0,0 +1,33 @@
+---
+date: 2021-04-18
+---
+
+![Beaker browser 1.0 screenshot](assets/images/beaker-browser.png)
+
+Beaker uses a [[peer-to-peer]] [[protocol]] called [[Hypercore]], or Hyper for short. "Hyperdrives" are like websites. They store webpages, pictures, media, user data, and so on. Hyperdrives power a lot of Beaker's best features.
+
+"Hyperdrives" are folders you host from your computer. They contain web pages which you can browse and edit. You can create and share hyperdrives using Beaker. [Learn more](https://docs.beakerbrowser.com/beginner/creating-new-hyperdrives).
+
+## Why is Beaker different?
+
+Beaker is built with Chromium and should feel exactly like any other [[Web browser]]. The big difference: Beaker can host websites.
+
+Hosting a website is traditionally done by "servers" which are specialized computers in the cloud. Servers require a variety of skills to run, and while there are some great services out there to make it easier, we wanted to try something new. We figured, what if anybody could host a website from their laptop?
+
+We call those self-hosted sites "Hyperdrives."
+
+- "Hyper" because they're kind of magical, and
+- "Drives" because they're collections of files.
+- It's not just a harddrive, it's a Hyperdrive!
+
+You can create a Hyperdrive from Beaker, add your website's HTML, and then share the Hyperdrive link with any other Beaker user. Their computer will connect directly to yours, as if you were running a server up in the cloud.
+
+## What does Beaker do better than other browsers?
+
+Beaker makes building a Website weirdly easy. We have a builtin editor, tools to sync folders with your website, and some pretty fun APIs for reading and writing the files in your website.
+
+If you're a teacher in a digital classroom, especially if you're teaching web development, Beaker is really handy. Your students don't need to learn Git, the commandline, or any other piece of server administration. They can download Beaker and get straight into the business of building Websites.
+
+Dev teams may also find Beaker handy for working on site prototypes. All you have to do is load the prototype into Beaker and share the hyper:// link around the office. If somebody wants to make a change, they can fork the site and share their version back.
+
+Beaker takes the drudge work out of hosting sites.

_notes/hypha.md

@@ -3,6 +3,7 @@ title: Hypha
 ---
 
 <https://hypha.coop>  
+<https://twitter.com/HyphaCoop>
 
 We cultivate collective growth and meaningful livelihoods through learning and building technologies together.
 

_notes/initial-seeds.md

@@ -6,7 +6,7 @@ Set of areas that guide our reveries?
 
 1. The history of [[hypertext transfer protocol|hypertext]], [[rss]]+adjacent protocols and standards.
 2. The act of [[publishing]] as "making something public" → publicness → hybrid [[public space]].
-3. The possibilities for *the infrastructural* (maintenance/repair) to draw from the past to rethink the present through co-operative approaches.
+3. The possibilities for *the infrastructural* ([[maintenance]]/repair) to draw from the past to rethink the present through co-operative approaches.
 
 <!--more-->
 

_notes/maintenance.md

@@ -0,0 +1,27 @@
+---
+date: 2021-04-18
+---
+
+## Maintenance and Care
+### A working guide to the repair of rust, dust, cracks, and corrupted code in our cities, our homes, and our social relations.
+
+> What we really need to study is how the world gets put back together. I’m not talking about the election of new officials or the release of new technologies, but rather the everyday work of maintenance, caretaking, and repair. Steven Jackson’s now-classic essay “Rethinking Repair,” written in the before-time — way back in 2014 — proposes that we “take erosion, breakdown, and decay, rather than novelty, growth, and progress, as our starting points” in considering relations between society and technology. His sober exercise in “broken world thinking” is matched with “deep wonder and appreciation for the ongoing activities by which stability … is maintained, the subtle arts of repair by which rich and robust lives are sustained against the weight of centrifugal odds.” 2
+
+> In many academic disciplines and professional practices — architecture, urban studies, labor history, development economics, and the information sciences, just to name a few — maintenance has taken on new resonance as a theoretical framework, an ethos, a methodology, and a political cause. This is an exciting area of inquiry precisely because the lines between scholarship and practice are blurred. To study maintenance is itself an act of maintenance. To fill in the gaps in this literature, to draw connections among different disciplines, is an act of repair or, simply, of taking care — connecting threads, mending holes, amplifying quiet voices.
+
+<https://placesjournal.org/article/maintenance-and-care>
+Shannon Mattern, Places Journal, November 2018
+
+---
+
+## Mierle Laderman Ukeles
+
+![Mierle Laderman Ukeles, Touch Sanitation Performance, 1979-1980](assets/images/Mierle-Laderman-Ukeles.jpeg)
+_Mierle Laderman Ukeles, Touch Sanitation Performance, 1979-1980. Image from  artist and Ronald Feldman Fine Arts, New York._
+
+>Mierle Laderman Ukeles (born 1939, Denver, Colorado) is a New York City-based artist known for her feminist and service-oriented artwork, which relates the idea of process in conceptual art to domestic and civic "maintenance". She is the Artist-in-Residence at the New York City Department of Sanitation and creates art that brings to life the very essence of any urban center: waste flows, recycling, sustainability, environment, people, and ecology.
+
+<https://en.wikipedia.org/wiki/Mierle_Laderman_Ukeles>
+
+---
+

_notes/public-space.md

@@ -1,4 +1,13 @@
 ---
+date: 2010-03-28
 ---
 
-TBD
+## Public Spaces
+
+![Spirit Surfers animated wordmark](assets/images/spirit-surfers.gif)
+
+> Are the internet’s privately owned public spaces available for contemplation? Or does the speed of information and the constant movement of data make that impossible?
+
+> “Space” is a discourse of phenomena, the “public” is a discourse  of politics. Private ownership is a discourse of economics that warps the others to accommodate the habits of using things and abstractions. It constructs protocols that make space and public as ephemeral as money. Communities can take shape around these protocols but they grow their own, unarticulated systems of interaction and affinity that change more subtly and unpredictably than terms of service and zoning laws. The latter are brittle. Communities—even the minimal communions that are established between two people, or between one person and an image or object of contemplation—adapt easily to new conditions, and thrive in discourses beyond those of the marketplace. There aren’t enough terms of service to manage all the publics and space in the world, or the people who live in them.
+
+<https://thenewinquiry.com/public-spaces/> Brian Droitcour, The New Inquiry, October 29, 2012

_notes/social-stories.md

@@ -7,8 +7,8 @@ We are exploring the protocols, languages, and material of the internet as a pla
 
 **Can you provide a great, existing example (that we can share with audiences who may be unfamiliar with this line of thinking/work)?**
 
-- <https://github.com/ournetworks>: the conference Dawn, myself, and friends, have been organizing. We've had great talks/workshops/happenings that weave network protocols and materially. Our GitHub org is where we organize openly
+- <https://github.com/ournetworks>: the conference [[Dawn Walker|Dawn]], [[Garry Ing|Garry]], and friends, have been organizing. We've had great talks/workshops/happenings that weave network protocols and materially. Our GitHub org is where we organize openly
 - <https://handbook.hypha.coop/>: [[Hypha]]'s (living) handbook that gives a sense of how we work and operate through online spaces
-- <https://pmvabf.org/>: Printed Matter’s Virtual Art Book Fair. We think their shift to virtual this year was really neat to experience. They had a lot of support from folks and created an experience that feels unique and "of-the-net" instead of directly replicating the in-person event. We were also are thinking about https://www.anarchistbookfair.ca/tablers-2020/
+- <https://pmvabf.org/>: Printed Matter’s Virtual Art Book Fair. We think their shift to virtual this year was really neat to experience. They had a lot of support from folks and created an experience that feels unique and "of-the-net" instead of directly replicating the in-person event. We were also are thinking about <https://www.anarchistbookfair.ca/tablers-2020/>
 - <http://designforthe.net/workshops/ascii/>: A workshop Mindy Seu hosted as part of A-B-Z-TXT. Pulling together concrete poetry and typewriter art, to create imaginary internet dwellings
-- <http://contemporary-home-computing.org/turing-complete-user/>: Essay from Olia Lialina expanding on the concept of General Purpose Users
+- <http://contemporary-home-computing.org/turing-complete-user/>: Essay from Olia Lialina expanding on the concept of _General Purpose Users_

_notes/statement-of-intent.md

@@ -2,4 +2,4 @@
 title: Statement of Intent
 ---
 
-[[Hypha]]’s practice is situated across many topics that are present in the theme of _Adaptive Reuse & Creative Misuse_. Drawing from our collective experiences, histories, and methodologies, our goal for the micro-residency to investigate how notions of digital [[infrastructure]] can be reused, reinterpreted, and reconfigured, to realize a kind of [[public space]]. Our approach to this theme will be composed of a few, very preliminary, subjects that will ground the residency: the situated histories of digital infrastructure, the implications of protocols for [[publishing]] ([[Hypertext]], [[RSS]], [[Peer-to-peer]]) in defining public spaces, and the possibilities of cooperative approaches to maintenance and repair. Our intent is to make the process of this investigation [[public space|public]] through online tools mapping our thinking about the theme (Open channels in Are.na as one example) and cultivating a [[Digital Public Garden]] as part of Hypha’s contributions to the initiative (a [[RSS|resyndicatable]] adaptive online notebook). The outputs from the [[bentway|micro-residency]] will be a written contribution to the [_Field Guide to the Digital Real_](https://www.are.na/from-later/field-guide-to-the-digital-real) and a micro-website containing the synthesis of our investigations and our evolving practice. The outputs will be textual and visual, and draw from our collaborative practices as a cooperative. They will explore ways to represent relationships with existing and emergent technologies within our communities. Through our micro-residency we will capture a poetic interpretation of the theme and provide prompts for institutions in the city on how they could reconfigure technology to create radically creative platforms.
+[[Hypha]]’s practice is situated across many topics that are present in the theme of _Adaptive Reuse & Creative Misuse_. Drawing from our collective experiences, histories, and methodologies, our goal for the micro-residency to investigate how notions of digital [[infrastructure]] can be reused, reinterpreted, and reconfigured, to realize a kind of [[public space]]. Our approach to this theme will be composed of a few, very preliminary, subjects that will ground the residency: the situated histories of digital infrastructure, the implications of protocols for [[publishing]] ([[Hypertext]], [[RSS]], [[Peer-to-peer]]) in defining public spaces, and the possibilities of cooperative approaches to [[maintenance]] and repair. Our intent is to make the process of this investigation [[public space|public]] through online tools mapping our thinking about the theme (Open channels in Are.na as one example) and cultivating a [[Digital Public Garden]] as part of Hypha’s contributions to the initiative (a [[RSS|resyndicatable]] adaptive online notebook). The outputs from the [[bentway|micro-residency]] will be a written contribution to the [_Field Guide to the Digital Real_](https://www.are.na/from-later/field-guide-to-the-digital-real) and a micro-website containing the synthesis of our investigations and our evolving practice. The outputs will be textual and visual, and draw from our collaborative practices as a cooperative. They will explore ways to represent relationships with existing and emergent technologies within our communities. Through our micro-residency we will capture a poetic interpretation of the theme and provide prompts for institutions in the city on how they could reconfigure technology to create radically creative platforms.

_notes/togethernet.md

@@ -0,0 +1,18 @@
+---
+date: 2021-04-18
+---
+
+> Togethernet is a collaborative archiving software in the form of a desktop web app that allows both [[peer-to-peer]] (P2P), traceless messaging as well as archived communications.
+
+> Designed around the ethos of data transparency and consent, the goal of the software is to transform digital rights practices such as the [right to be forgotten](https://gdpr.eu/right-to-be-forgotten/) into an embodied practice through the reimagination of software architecture and user experience.
+
+> The software contains two types of communication channels: the Ephemeral Channel and the Archival Channel.
+
+> The Ephemeral Channel uses the WebRTC peer-to-peer protocol, which means conversations do not go through a centralized server (bye google facebook AWS 👋🏼) and are permenantly erased once the browser closes.
+
+> The Archival Channel publishes meeting notes to a centeralized database that your organization may self-host or host on a third party’s server.
+
+![Togethernet interface](assets/images/togethernet.jpg)
+
+<https://togethernet-website.herokuapp.com/>
+<https://www.eyebeam.org/residents/xin-xin/>

_notes/unwalled-garden.md

@@ -0,0 +1,23 @@
+---
+date: 2021-04-18
+---
+
+An open protocol for building social Web applications.
+
+Part of the [[Beaker browser]] project.
+
+Unwalled.Garden is a kind of “Souped up [[RSS]].” Every user has a website, they publish their content as files, and they subscribe to each others’ sites.
+
+While [[RSS]] was primarily for blogging, Unwalled.Garden includes data types for many kinds of use-cases. These data types are spread across many JSON files which have pre-defined schemas.
+
+The schemas are simple, obvious, and syntax-free. A “post” record looks like this:
+
+```json
+{
+  "type": "unwalled.garden/post",
+  "body": "Hello, world!",
+  "createdAt": "2019-05-21T21:27:45.471Z"
+}
+```
+
+<https://unwalled.garden/>

_sass/_digital-garden.scss

@@ -161,6 +161,18 @@
     height: auto;
     display: block;
   }
+
+  hr {
+    border-width: 0;
+    border-top: 1px solid var(--foreground-text);
+  }
+
+  pre {
+    padding: 1rem;
+    background-color: rgba(var(--internal-link-rgb), 0.2);
+    border-radius: 6px;
+    font-size: .875rem;
+  }
 }
 
 // Link previews