||3 years ago|
|bin||3 years ago|
|etherpump||3 years ago|
|etherpump.egg-info||3 years ago|
|.gitignore||3 years ago|
|LICENSE.txt||7 years ago|
|README.md||3 years ago|
|padinfo.sample.json||7 years ago|
|setup.py||3 years ago|
pumping text from etherpads into publications
A command-line utility that extends the multi writing and publishing functionalities of the etherpad by exporting the pads in multiple formats.
Many pads, many networks
Etherpump is a fork of etherdump, a command line tool written by Michael Murtaugh that converts etherpad pages to files. This fork is made out of curiosities in the tool, a wish to study it and shared sparks of enthusiasm to use it in different situations within Varia.
Etherpump is a stretched version of etherdump. It is a playground in which we would like to add features to the initial tool that diffuse actions of dumping into pumping. So most of all, etherpump is a work-in-progress, exploring potential uses of etherpads to edit, structure and publish various types of content.
Added features are:
- opt-in publishing with the
publicationcommand, that listens to custom magic words such as
Etherdump is a tool that is used from the command line. It dumps all pads of one etherpad installation to a folder, saving them as different text files, such as plain text and HTML. It also creates an index file, that allows one to easily navigate through the list of pads. Etherdump follows a document-driven idea of publishing, which means that it converts pads as database entries into pads as files. This seems to be a redundant act of copying, but is actually an important in-between step that allows for many different publishing projects and experiments.
We started to get to know etherdump through various editions of Relearn and/or the worksessions organized by Constant. Collaborative writing on an etherpad has been an important ingredient for these situations. The habit of using pads branched into the day-to-day practice of Varia, where we use etherpads for all sorts of things, ranging from organising remote-meetings with 10+ people, to writing and designing PDF documents collaboratively.
After installing etherdump on the Varia server, we collectively decided to not want to publish pads by default. Discussions in the group around the use of etherpads, privacy and ideas of what publishing means, led to a need to have etherdump only start the indexing work after it recognizes a
__PUBLISH__ marker on a pad. We decided to work on a
__PUBLISH__ vs. __NOPUBLISH__ branch of etherdump, which we now fork into etherpump.
Change log / notes
Forking etherdump into etherpump. (Work in progress!)
May - September 2019
Etherdump is used to produce the Ruminating Relearn section of the Network Of One's Own 2 (NOOO2) publication.
A new command is added to make a web publication, based on the custom magic word
Multiple conversations around etherdump emerged during Relearn Curved in Varia, Rotterdam.
Including the idea of executable pads (etherhooks), custom magic words, a federated snippet protocol (etherstekje) and more.
Installation of etherdump on the Varia server.
__PUBLISH__ vs. __NOPUBLISH__ was added to the etherdump repository by decentral1se.
Originally designed for use at: Constant.
More notes can be found in the git repository of etherdump.
- requests (settext)
- python-dateutil, jinja2 (used by the index subcommand)
$ pip install python-dateutil jinja2 html5lib
$ python setup.py install
$ mkdir mydump $ cd myddump $ etherdump init
The program then interactively asks some questions:
Please type the URL of the etherpad: https://pad.vvvvvvaria.org/
The APIKEY is the contents of the file APIKEY.txt in the etherpad folder.
Please paste the APIKEY: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The settings are placed in a file called
.etherdump/settings.json and are used (by default) by future commands.
- publication (etherpump)
To get help on a subcommand:
$ etherdump revisionscount --help
GNU AFFERO GENERAL PUBLIC LICENSE, Version 3