A candidate for CSCSJS or a Mocha Fetchlet

Michi pinged to check tag the net out once more, which I did. Clearly a candidate for wrapping in a mocha fetchlet (you'll read me write that more often in the foreseeable future):

<script src="/tagthenet" 

     id="tagthenet-fetchlet"

     text="foo foo bar" 

     response="mochaBus.suggestedTags" />

Welcome to CSCSJS - client-server-client-server-javascript. More's to follow.

:-)

Consensus vs Direct Democracy

Regarding technocracy, ...when you delegate decision making to a group of people that are willing to spend time to involve themselves in "the system", there is always a big risk that it's breeding technocracy.

Richard writes, "In places like Cuba, and Porto Allegra, where participatory opportunities exist, people generally do tend to participate."

Even if it were true that in these places "people generally participate", you can never achieve a system in which "everybody" participates. By definition, the people that *do* participate are "the new elite", since they are the ones making the decisions.

Because of this, I still see harmonization "only" as a - very important - administrative process, that does not take the responsibility for the final decision making away from the individual. In addition to a harmonization process which develops a suggested consensus, we need a direct democratic control system that can veto the suggested consensus if need be.

Rails' greatest contribution

[...] "This is Rails' greatest contribution , the one that will last longest, because eventually Rails itself will be usurped and something else will come along to pick at its sun-bleached carcass. But the ecosystem it will have left behind will be healthier because of its contributions."

trackAllComments

The following is just a quick draft updating the instructions for embedding coComment into your blogs. With this new approach, you will be able to track *all* the comments posted, not just the ones by fellow coComment users.

This first section you can skip, if coComment already extracts the correct information automatically. You only need it if the automatic extraction on your blog does not work or does not work reliably. This step is already documented in more detail at http://cocomment.com/integrate

<script type="text/javascript">

    var blogTool              = "MyBlogManufacturer";

    var blogURL               = "http://www.domain.com/~myblog";

    var blogTitle             = "My Blog";

    var postURL               = "http://www.domain.com/~myblog/?p=42″;

    var postTitle             = "This is Roger’s \"great\" post";

    var commentTextFieldName  = "messageTextArea";

    var commentButtonName     = "SubmitButton";

    var commentAuthorLoggedIn = true;

    var commentAuthor         = "Douglas Adams";

    var commentFormName       = "commentForm";

  </script>

In the following second section you'll see the two additional attributes that you will need to include in the script tag if you want to track all comments:

<script id="cocomment-fetchlet"

    trackAllComments="true"

    src="http://www.cocomment.com/js/enabler.js">

  </script>

Note that in this example I linked to the new enabler.js file instead of the cocomment.js file. Pointing directly to the cocomment.js file should work as well, but I hope loading the enabler.js file first will provide a performance benefit. Hearing from you about your experiences with this will be highly appreciated. This stuff is experimental and I'm note sure how it will behave in the real world :-)

Anno 2003: deployZone

>>> Anno 1998: crossnet