38 lines
15 KiB
XML
38 lines
15 KiB
XML
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.2.0">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2021-04-11T14:13:26+00:00</updated><id>/feed.xml</id><title type="html">Digital Garden | Notes</title><subtitle>A digital garden or public notebook for The Bentway’s Digital and/as Public Space Micro-Residency.</subtitle><entry><title type="html">World Wide Web</title><link href="/world-wide-web" rel="alternate" type="text/html" title="World Wide Web" /><published>2021-04-11T14:13:26+00:00</published><updated>2021-04-11T14:11:44+00:00</updated><id>/world-wide-web</id><content type="html" xml:base="/world-wide-web"><p>TBD</p></content><author><name></name></author><summary type="html">TBD</summary></entry><entry><title type="html">Web Browser</title><link href="/web-browser" rel="alternate" type="text/html" title="Web Browser" /><published>2021-04-11T14:13:26+00:00</published><updated>2021-04-11T14:11:44+00:00</updated><id>/web-browser</id><content type="html" xml:base="/web-browser"><p>A web browser (commonly referred to as a browser) is a software application for accessing the <a class="internal-link" href="/world-wide-web">World Wide Web</a>. When a user requests a web page from a particular website, the web browser retrieves the necessary content from a web server and then displays the page on the user’s device.</p>
|
||
|
||
<p><a href="https://en.wikipedia.org/wiki/Web_browser">https://en.wikipedia.org/wiki/Web_browser</a></p></content><author><name></name></author><summary type="html">A web browser (commonly referred to as a browser) is a software application for accessing the [[World Wide Web]]. When a user requests a web page from a particular website, the web browser retrieves the necessary content from a web server and then displays the page on the user’s device. https://en.wikipedia.org/wiki/Web_browser</summary></entry><entry><title type="html">Statement of Intent</title><link href="/statement-of-intent" rel="alternate" type="text/html" title="Statement of Intent" /><published>2021-04-11T14:13:26+00:00</published><updated>2021-04-11T14:11:44+00:00</updated><id>/statement-of-intent</id><content type="html" xml:base="/statement-of-intent"><p><a class="internal-link" href="/hypha">Hypha</a>’s practice is situated across many topics that are present in the theme of <em>Adaptive Reuse &amp; Creative Misuse</em>. Drawing from our collective experiences, histories, and methodologies, our goal for the micro-residency to investigate how notions of digital <a class="internal-link" href="/infrastructure">infrastructure</a> can be reused, reinterpreted, and reconfigured, to realize a kind of <a class="internal-link" href="/public-space">public space</a>. 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 <a class="internal-link" href="/publishing">publishing</a> (<a class="internal-link" href="/hypertext">Hypertext</a>, <a class="internal-link" href="/rss">RSS</a>, <a class="internal-link" href="/peer-to-peer">Peer-to-peer</a>) in defining public spaces, and the possibilities of cooperative approaches to maintenance and repair. Our intent is to make the process of this investigation <a class="internal-link" href="/public-space">public</a> through online tools mapping our thinking about the theme (Open channels in Are.na as one example) and cultivating a <a class="internal-link" href="/digital-public-garden">Digital Public Garden</a> as part of Hypha’s contributions to the initiative (a <a class="internal-link" href="/rss">resyndicatable</a> adaptive online notebook). The outputs from the <a class="internal-link" href="/bentway">micro-residency</a> will be a written contribution to the <a href="https://www.are.na/from-later/field-guide-to-the-digital-real"><em>Field Guide to the Digital Real</em></a> 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.</p></content><author><name></name></author><summary type="html">[[Hypha]]’s practice is situated across many topics that are present in the theme of Adaptive Reuse &amp; 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 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.</summary></entry><entry><title type="html">RSS</title><link href="/rss" rel="alternate" type="text/html" title="RSS" /><published>2021-04-11T14:13:26+00:00</published><updated>2021-04-11T14:11:44+00:00</updated><id>/rss</id><content type="html" xml:base="/rss"><p>RSS (RDF Site Summary or Really Simple Syndication) is a web feed that allows users and applications to access updates to websites in a standardized, computer-readable format. These feeds can, for example, allow a user to keep track of many different websites in a single news aggregator. The news aggregator will automatically check the RSS feed for new content, allowing the list to be automatically passed from website to website or from website to user. This passing of content is called web syndication. Websites usually use RSS feeds to publish frequently updated information, such as blog entries, news headlines, or episodes of audio and video series. RSS is also used to distribute podcasts. An RSS document (called “feed”, “web feed”, or “channel”) includes full or summarized text, and metadata, like <a class="internal-link" href="/publishing">publishing</a> date and author’s name.</p>
|
||
|
||
<p><a href="https://en.wikipedia.org/wiki/RSS">https://en.wikipedia.org/wiki/RSS</a></p></content><author><name></name></author><summary type="html">RSS (RDF Site Summary or Really Simple Syndication) is a web feed that allows users and applications to access updates to websites in a standardized, computer-readable format. These feeds can, for example, allow a user to keep track of many different websites in a single news aggregator. The news aggregator will automatically check the RSS feed for new content, allowing the list to be automatically passed from website to website or from website to user. This passing of content is called web syndication. Websites usually use RSS feeds to publish frequently updated information, such as blog entries, news headlines, or episodes of audio and video series. RSS is also used to distribute podcasts. An RSS document (called “feed”, “web feed”, or “channel”) includes full or summarized text, and metadata, like [[publishing]] date and author’s name. https://en.wikipedia.org/wiki/RSS</summary></entry><entry><title type="html">Publishing</title><link href="/publishing" rel="alternate" type="text/html" title="Publishing" /><published>2021-04-11T14:13:26+00:00</published><updated>2021-04-11T14:11:44+00:00</updated><id>/publishing</id><content type="html" xml:base="/publishing"></content><author><name></name></author><summary type="html"></summary></entry><entry><title type="html">Public Space</title><link href="/public-space" rel="alternate" type="text/html" title="Public Space" /><published>2021-04-11T14:13:26+00:00</published><updated>2021-04-11T14:11:44+00:00</updated><id>/public-space</id><content type="html" xml:base="/public-space"><p>TBD</p></content><author><name></name></author><summary type="html">TBD</summary></entry><entry><title type="html">Protocol</title><link href="/protocol" rel="alternate" type="text/html" title="Protocol" /><published>2021-04-11T14:13:26+00:00</published><updated>2021-04-11T14:11:44+00:00</updated><id>/protocol</id><content type="html" xml:base="/protocol"><blockquote>
|
||
<p>A communication protocol is a system of rules that allows two or more entities of a communications system to transmit information via any kind of variation of a physical quantity. The protocol defines the rules, syntax, semantics and synchronization of communication and possible error recovery methods. Protocols may be implemented by hardware, software, or a combination of both.</p>
|
||
</blockquote>
|
||
|
||
<p><a href="https://en.wikipedia.org/wiki/Communication_protocol">https://en.wikipedia.org/wiki/Communication_protocol</a></p></content><author><name></name></author><summary type="html">A communication protocol is a system of rules that allows two or more entities of a communications system to transmit information via any kind of variation of a physical quantity. The protocol defines the rules, syntax, semantics and synchronization of communication and possible error recovery methods. Protocols may be implemented by hardware, software, or a combination of both. https://en.wikipedia.org/wiki/Communication_protocol</summary></entry><entry><title type="html">peer-to-peer</title><link href="/peer-to-peer" rel="alternate" type="text/html" title="peer-to-peer" /><published>2021-04-11T14:13:26+00:00</published><updated>2021-04-11T14:11:44+00:00</updated><id>/peer-to-peer</id><content type="html" xml:base="/peer-to-peer"><ul>
|
||
<li><a class="internal-link" href="/hypercore">Hypercore</a></li>
|
||
<li><a class="internal-link" href="/ipfs">IPFS</a></li>
|
||
</ul>
|
||
|
||
<p>TBD</p></content><author><name></name></author><summary type="html">[[Hypercore]] [[IPFS]] TBD</summary></entry><entry><title type="html">IPFS</title><link href="/ipfs" rel="alternate" type="text/html" title="IPFS" /><published>2021-04-11T14:13:26+00:00</published><updated>2021-04-11T14:11:44+00:00</updated><id>/ipfs</id><content type="html" xml:base="/ipfs"><p>The InterPlanetary File System (IPFS) is a <a class="internal-link" href="/protocol">protocol</a> and peer-to-peer network for storing and sharing data in a distributed file system. IPFS uses content-addressing to uniquely identify each file in a global namespace connecting all computing devices.</p>
|
||
|
||
<p><a href="https://en.wikipedia.org/wiki/InterPlanetary_File_System">https://en.wikipedia.org/wiki/InterPlanetary_File_System</a></p></content><author><name></name></author><summary type="html">The InterPlanetary File System (IPFS) is a [[protocol]] and peer-to-peer network for storing and sharing data in a distributed file system. IPFS uses content-addressing to uniquely identify each file in a global namespace connecting all computing devices. https://en.wikipedia.org/wiki/InterPlanetary_File_System</summary></entry><entry><title type="html">Initial Seeds</title><link href="/initial-seeds" rel="alternate" type="text/html" title="Initial Seeds" /><published>2021-04-11T14:13:26+00:00</published><updated>2021-04-11T14:11:44+00:00</updated><id>/initial-seeds</id><content type="html" xml:base="/initial-seeds"><p>Set of areas that guide our reveries?</p>
|
||
|
||
<ol>
|
||
<li>The history of <a class="internal-link" href="/hypertext-transfer-protocol">hypertext</a>, <a class="internal-link" href="/rss">rss</a>+adjacent protocols and standards.</li>
|
||
<li>The act of <a class="internal-link" href="/publishing">publishing</a> as “making something public” → publicness → hybrid <a class="internal-link" href="/public-space">public space</a>.</li>
|
||
<li>The possibilities for <em>the infrastructural</em> (maintenance/repair) to draw from the past to rethink the present through co-operative approaches.</li>
|
||
</ol>
|
||
|
||
<!--more-->
|
||
|
||
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Publish from RSS to arena?
|
||
RSS to twitter? The gram?
|
||
Use DPress to get it on SSB?
|
||
</code></pre></div></div>
|
||
|
||
<p><em>What if… we travel back in time and blow up BGP? Would Xanadu be realized? Would actual plural internetworking have persisted?</em></p>
|
||
|
||
<p>Publishing → making things public</p>
|
||
|
||
<p><strong>» COMMISSIONING BODIES «</strong> <br />
|
||
Economy as a form a expression</p>
|
||
|
||
<p>Antagonizing the separation of frontend/backend</p></content><author><name></name></author><summary type="html">Set of areas that guide our reveries? The history of [[hypertext transfer protocol hypertext]], [[rss]]+adjacent protocols and standards. The act of [[publishing]] as “making something public” → publicness → hybrid [[public space]]. The possibilities for the infrastructural (maintenance/repair) to draw from the past to rethink the present through co-operative approaches.</summary></entry></feed> |