Stek (NL) = Graft (EN) = Greffe (FR)
Stekje = Little graft


* Varia etherdump (semi-public) https://etherdump.vvvvvvaria.org/
* Constant etherdump (public) http://etherdump.constantvzw.org/
* Relearn etherdump (local, public to the group) http://relearn.local/etherdump/
* Etherdump https://gitlab.constantvzw.org/aa/etherdump
* Varia's __PUBLISH__ branch https://gitlab.constantvzw.org/decentral1se/etherdump/tree/publish-vs-nopublish

etherStekje is the name of the current thoughts emanating from the Relearn.Curved.Rotterdam session around Publishing vs Indexing vs Dumping through etherpads and etherdump.

Visual reference: Sokol Beqiri @ documenta14 — Oak grafting between Kassel and Athens

Etherdump exists as a tool to archive / backup / save / publish / dump / reformat an etherpad instance. This tool came to be from a realisation of a certain dependency on the etherpad tool itself. Organisations such as Constant, Varia and Relearn use etherpads heavily. The very nature of the software means that if you have the url of the pad, it is 'publicly accessible' and therefor 'published'.

etherStekje from Rotterdam
Discussions on the etherdump software quickly "stek-ed" into multiple conversations. We realised that talking about Etherdump installed at Constant, Varia or Relearn are actually three different conversations, as there are two versions of the Etherdump involved (opt-out and opt-in) (__ NOPUBLISH __ or __ PUBLISH __ keys), there are different notions of "public" (public as in the internet, public as in the changing group of relearners) and different modes of writing, creating all sorts of content (notes, texts, executables or otherwise).

Etherstekje proposes to facilitate exchange of * (processes, ideas, code, references, methodologies...) within and outside of Relearn, both within pads at a specific point of the curve and from one point of the curve to the next. Etherstekje could bring elements from pads into terminal use (ssh sessions — through motd) and into browser through relearn.local homepage, and creates transversal etherdump connections. It creates interdependencies and entanglements between vocabularies, contexts, files...

The idea of a stekje in a pad came from usage of markup syntax like HIGHLIGHT{} inside the pad. Publishing vs Indexing was a table discussion during which Relearn attendants fantasized about other __KEY__ declarations that could be made at the top of or in the body of pads. A list of these dream-keys exists in: http://relearn.local:9001/p/publish-index . Later the HIGHLIGHT{} markup was considered as it was used before in Christoph Haag's makefile publishing process (used for the conversations.tools book for example).

In an earlier conversation on Saturday evening, after a long energetic day of working, there was a moment of realisation that the word "etherdump" did not cover the Relearn use of tool anymore. The etherdump was flying and there were many directions it was taking and could take. One of the groups started to work on using the etherpad and etherdump as a place to write executable files, which triggered a possible convertion of the ether"dump" into an ether"stack". It reminded us to Relearn 2017, where the "unibash" scripts were already running from multiple etherpads.

Thinking about using the etherDump process to broadcast outwards of the pad and etherdump environment lead us to think about how elements of one pad often cross-seeds to another research / writing topic. If a regular pad dumping / pad publishing process let us set a __PAD_OF_THE_MONTH__ could it also let us extract ETHERSTEKJE{} lines to a non pad destination. Like a planting shed of graphs that are being nurtured by a tree surgeon.

Etherstekje could be a form of federation. It could allow for processes to happen in a specific place and moment, without losing contact with the others.

There are multiple ideas at the moment, of how snippets of pads can be selected to be "etherstek-ed". One strategy would be to collect potential-stek-messages on an etherpad. Another strategy would be to add mark-up within the lines, notes, drafts, scribbles and scripts on the pads.


A "stekje" supports the potential to grow its own roots. 

Would this be an act of copying or cutting?


How could etherstekje be executed ?

OE! The roaming server teams stepped in for a second. :)
Etherdump is now being executed from a pad: http://relearn.local:9001/p/etherstekjes
The pad has a symbolic link to the executed file of the etherdump.

/ / / 

Why doesn't the etherpad not support local, peer-to-peer, ...
It works, as it is accessible (bash in browser, cross-system, ... )
Possible connections to other protocols? 

Generate etherdumps ... for different uses.
Each one having a specific set of magic words, convert to * actions, 
Changing the tools to fit your collective experience ...

granular outputs / formats / usages 
granular input protocol / ?

- input from local (your favourite text editor)
- input from federation (ether2ether / dump2dump / )

how to make it soft software?

What could be a socket to use for inputs 
and the same for outputs?

writing modes
- local
- private (only me)
- collaborative 
- software-of-choice (choose your software of choice while sharing the same writing environment)

What do we want to sync?

Are we reinventing the file system?
filesystem through the browser is read-only,

Is this still etherstekje?
Or etherOS?

A version of etherOS and see if we can think of a version of this system, that still runs without etherpad.
What are the aspects of etherpad, that makes us need etherpad.
etherpad-central-thinking or non-etherpad-central-thinking

/ / /

file A(1) on computer 1
file A(2) on computer 2

Script(s) in between that do
- conflict resolution
- detect A(2)'s presence, when A(1) is in the same network

the dat protocol is close to doing this?

/ / /

federated etherstekje .........

ActivityPub ?

Parallel jokes ...
an irc bot that speaks to the #relearn channel
an email being send out to once the relearn server is connected to the 

EtherFed !! 

Sending messages from the etherdump via ActivityPub
Receiving messages from others to the etherdump via ActivityPub

Long tails
<https://networksofonesown.constantvzw.org/etherbox/manual.html> - Etherbox documentation (2018)
<http://pipelines.constantvzw.org/> - Promiscuous Pipelines worksession (2014)
etherbox documentation <https://networksofonesown.constantvzw.org/etherbox/manual.html#guide-to-using-your-etherbox>