figure 1: Total number of messages on Nettime
diff --git a/docs/index.md b/docs/index.md index 7ff9633..89c8c7b 100644 --- a/docs/index.md +++ b/docs/index.md @@ -89,11 +89,11 @@ Though this is only subscriptions. Not everyone post to the list. So what about  -What we colloquially call a "cohort" resembles, to some degree, the notion of subscription rate, which ultimately speaks to the idea of Nettime's "newcomers". Though rather than consisting of the sheer amount of subscriptions over time (data which is not available from the archive), we consider when a message first appeared on the list given an email address provenance. The graph of _figure 0_ displays the sum of these "first message" instances per month (50 months quintiles). A spike in the graph could be read as the formation of a new cohort, that is, an increase in the activity of newcomers, which may signify, albeit hypothetically, that an aggregate of common interests are brought forth on the list. Nettime's Nettimes so to speak. +What we colloquially refer to as a "cohort" resembles, to some degree, the notion of subscription rate discussed above. Both notions speak to the idea of Nettime's "newcomers". Though rather than consisting of the sheer amount of subscriptions over time (data which is not available from the archive), we consider when a message first appeared on the list given an email address provenance. The graph of _figure 0_ displays the sum of these "first message" instances per month (50 months quintiles). A spike in the graph could be read as the formation of a new cohort, that is, an increase in the activity of newcomers, which may signify, albeit hypothetically, that an aggregate of common interests are brought forth on the list. Theres are observable spikes that appear here and there through out the months and years in _figure 0_, however, these are short lived (max 6 months). What is more striking is the sustained activity that occurred in first two quintiles of the graph (1996-2004). This activity can be correlated with the high subscription rate described earlier. Though, unlike subscriptions, the amount of "first messages" peaked around the year 2000, rather than between 2001-2002 (66 subscriptions/month). Let us call this peak the 2000 cohort. -After 2004, the number of first messages declines. As noted below, this can be attributed to the creation of nettime-ann in 2005, which rerouted announcement-type activity out off nettime-l. Nonetheless, it can be argued that, in considering the low subscription rate in the interval 2005-2011 (6 subscriptions/month), the barely noticeable peaks of 2008 and 2011 are significant. Thus Nettime may harbor more than a single 2000 cohort, 2008 and 2011 being the other two though remarkably less momentous than the first one. +After 2004, the number of first messages declines. As noted below, this can be attributed to the creation of nettime-ann in 2005, which rerouted announcement-type activity out off nettime-l. Nonetheless, it can be argued, when considering the low subscription rate in the interval 2005-2011 (6 subscriptions/month), that the barely noticeable peaks of 2008 and 2011 are significant. Thus Nettime may harbor more than a single 2000 cohort, 2008 and 2011 being the other two though remarkably less momentous than the first one.  @@ -109,7 +109,6 @@ In our conversations with Geert Lovink, we derived a few observations on the dat Was Nettime's heyday only part of the first decade of its existence? Judged solely in terms of sheer amount of postings to the list (activity), it clearly can be seen to have diminished. However, in what follows, we propose different schemata, measuring the amount of dialog on the list (vigour) as well categorizing that dialog by the most prolific contributors (outspokeness). - ##Vigour A mailing list certainly lay itself to announcements-type messages where a single message is posted to the list while no one does and/or is expected to reply. Yet, more importantly, what mailing lists also allow is to produce 'threads' which are formed around a varying amount of replies to an initial message. These threads form the basis of an asynchronous 'dialog' so to speak. As introduce in the previous section, we came up with the term 'vigour' to account for this practice of replying to messages, which, in turn, create 'dialogical' dynamics between some of the list's members. diff --git a/docs/makefile b/docs/makefile index f5eb41c..bb72808 100644 --- a/docs/makefile +++ b/docs/makefile @@ -3,19 +3,25 @@ ARCHIVE := arch/nettime-l_2016-12-31.json.gz CMDSCRIPT := command-script.json -all: init index.html clean-stage +all: init index.html txt.txt clean-stage init: @command -v pandoc > /dev/null 2>&1 || (echo 'pandoc not found... please visit -- http://johnmacfarlane.net/pandoc/installing.html' && exit 1) -%.stage.md: index.md - python ../report.py -i $(CMDSCRIPT) -o index.stage.md -t index.md -a $(ARCHIVE) +%.md.stage: index.md + python ../report.py -i $(CMDSCRIPT) -o $@ -t $< -a $(ARCHIVE) -%.html: %.stage.md +%.html: %.md.stage pandoc -s --template style/template.html5 -c style/style.css -o $@ $< +%.txt.stage: txt.d + python ../report.py -i $(CMDSCRIPT) -o $@ -t $< -a $(ARCHIVE) + +%.txt: %.txt.stage + fold -sw 80 $< > $@ + clean-stage: - rm -rf *.stage.md + rm -rf *.stage clean: rm -rf *.hml *.txt diff --git a/nettime/report.py b/nettime/report.py index 662017d..73bf3ab 100644 --- a/nettime/report.py +++ b/nettime/report.py @@ -186,7 +186,7 @@ class Report: def tab_replies_ranking(self, rank=10): d = self.query.replies_ranking(rank=rank) - return format.Tab.from_dataframe(d, name_map={'nbr-replies': 'nbr. replies'}) + return format.Tab.from_dataframe(d, name_map={'nbr_replies': 'nbr. replies'}) def tab_replies_avg_ranking(self, rank=10): d = self.query.replies_avg_ranking(rank=rank)