Welcome to Constant Etherpad!

These pads are archived each night (around 4AM CET) @ http://etherdump.constantvzw.org/
An RSS feed from the etherdump also appears on http://constantvzw.org/

To prevent your public pad from appearing in the archive and RSS feed, put or just leave the following (including the surrounding double underscores) anywhere in the text of your pad:

    __NOPUBLISH__

Changes will be reflected after the next update at 4AM.
michael and seda meet to discuss constant archives
(see seda for her notes made in notebook form)

libraries
(long discussion about Etherdump, digital platforms as Public Libraries, also the need host an unknown public (the comparison with homeless communities use of public libraries), constant etherpad vs. piratepad.
http://etherdump.constantvzw.org/

Portable servers : 
    Relearn (2) in variable was the first place we made a point of a local server

STATIC HTML as archival, durable, editable (though "slower" than platforms like etherpad, cms)

how to build an alternative to "yet another monolithic platform" for archiving or sharing files etc.
and instead create a "center-less" system that's more about
rewarding distributed files,

concrete example:
    youtube as a platform drives web visits to a central point away from say an event page that might embed a video clip in it.
    how to push around the "rim" of a webring: imagine the same clip is embedded in 3 different organisations websites (constant, lgm, pzwart)
    taking a "torrent" approach where more distribution, the more peers the better, ... what's

so where are we now?
webring embedded video poc ( http://automatist.org/blog/botopera-opening/)
lgm archive http://libregraphicsmeeting.org/2015/program/##peter-sikking-metapolator:-designing-interaction-for-creative-pros
and looked at the extracted microdata feed from 2014... https://www.w3.org/2012/pyMicrodata/extract?uri=http%3A%2F%2Flibregraphicsmeeting.org%2F2014%2Fprogram%2Findex.html&format=json
applying to vj13 page: http://www.vj13.constantvzw.org/site/transmission/extended

In the end a couple of core questions/issues:
    When we talk about a "vandalist" interface allowing random pages (such as those of constant, but indeed also those of arbitrary sites like nytimes.com) ... it maybe slides too freely between various quite different uses / scenarios. It would be useful to narrow the work to specific uses (a tool for "nucleus" use ... a tool for a larger Constant community (and who is that?) ... an arbitrary tool for anyone...

In a similar vein, it would be useful to make specific some different scenarios for dealing with for instance undesired use or misuse / abuse. For instance, having a git based system with a protected public master branch (similar to moderated edits in a wiki), versus for instance making a PAIR of branches public (moderated and "open") and thinking through what these different models could mean.

We talked about the idea of having TWO views or sides to the archive interface in the sense of:
    (1) The documents that become enriched through the use of archive materials (such as http://www.vj13.constantvzw.org/site/transmission/extended)
    (2) The "listings" pages such as: http://video.constantvzw.org/VJ13/ and http://video.constantvzw.org/Collaborative_Online_Video/AAindex.html