Activities

  • Record and publish a video series on version control
  • Automatically convert articles on Wakelet to PDF for print
  • Look into the prototypes by Ink & Switch
  • Develop GUI workflow for the change_instructions_executor_1
  • Look into _Prtcl by collectiveone.org
  • Look into systemschanges.com
  • Look into the pattern language and cards of Wise Democracy
  • Summarize and publish a text on the nature of information and its encoding
  • Continue looking into InfoCentral
    • Make existing introduction + description texts immutable
    • Write comments/feedback and explore Web Annotation
    • Set up a workspace for creating Web Annotations
    • Develop a way to display the comments/annotations on the base text
    • 2019-07-27T19:41:00Z: Automatically convert the description draft text to a DIN A6 booklet PDF for print.
    • Generate a glossary from Web Annotation and apply it onto the text
  • Continue looking into Montru
    • Watch the videos
    • First feedback/questions
    • Reply
  • Develop a CSV parser that converts to XML *
  • Write and publish a text on values
    • Collect material about the valuation of values
    • Figure out form
    • Add practical examples
    • Explore the nature of non-measurable, non-manifesting value discussions
    • Add a part about the importance of theoretical value discussions/considerations
  • Read Rainer Kuhlen’s book “Hypertext – Ein nicht-lineares Medium zwischen Buch und Wissensbank”
    • 2019-06-14T17:25:00Z: Reach 20% *
    • Reach 40% *
    • Reach 60% *
    • Reach 80% *
    • Reach 100% *
    • Write and publish a summary
  • Activity Format
    • 2019-05-12T21:12:00Z: Create an activity format and publish my activities
    • 2019-05-13T10:38:00Z: Translate everything into German
    • 2019-05-13T21:53:00Z: Generate renderings/visualizations from the format
    • 2019-05-14T19:02:00Z: Prepare and publish a repository for the generator workflow
    • 2019-05-18T23:13:00Z: Archive of Completed Activities for the Activity Format *
    • 2019-05-21T20:07:00Z: Publish stylesheets in German language
    • Add more types/states *
    • Add full output file for both, the archived/completed and current activities
    • Offer a website + endpoint that allows clients the selection of a particular format/rendering/language/status-selection via HTTP Header Content-Type/Language negotiation (and alternatively GET-parameters)
  • Write “The Work Is the Work” *
    • Write first draft
    • 2019-06-02T14:31:00Z: Edit and publish
    • 2019-06-02T14:51:00Z: Create hyperglossarized version of the text
    • Expand the topic to online audio/video conferences and conversation communities
    • Propose ways for introducing practical implementation
  • Read Michael Polanyi’s Book “Personal Knowledge” *
    • Reach 20% *
    • Reach 40% *
    • Reach 60% *
    • Reach 80% *
    • 2019-05-19T15:40:00Z: Reach 100% *
    • Write and publish a summary

Activity Description

Click an activity item marked with an asterisk (*) at its end to view its description.

Descriptions

Want to use it for audio e-mail messaging convenience, so that I can upload a file with a web interface. A little bit like ownCloud/Nextcloud. Could/should get a ReST API to become a hypertext/hypermedia server that delivers resources without exposing the internal specifics of their storage, effectively acting as a resolver/mapping/abstraction. See the initial commit.

Used “xhtml_to_latex_2.xsl” to generate a printed booklet for better reading/consumption convenience.

Allow to automatically copy the current span selection to the clipboard on completion as an option.

A csv2xml converter does already exist in the automated_digital_publishing package, but it’s buggy. Therefore, I probably should write my own with proper parsing techniques based on an implicit call tree instead of trying to fix the current implementation with its state machine strategy. I started an attempt some time ago, but failed, potentially by not recognizing the linebreak as the element of highest priority or some other reason. Unfortunately, I can’t find that code any more and likely have to start anew from scratch again.

70 pages.

140 pages.

209 pages.

279 pages.

348 pages.

Recently, completed top-level activities were removed from the main output file (in order to keep focus on actual activities, not loads of historical entries). Still, there needs to be a way to conveniently view the completed activities separately.

Visual rendering of “waiting”/“paused”/“blocked” (red), “abandoned” (red, crossed out), “rejected”/“cancelled” (black, crossed out) would be nice.

I did a Hyperglossary prototype (code, live) for Doug@50 (50th anniversary of Douglas Engelbart’s Great 1968 Demo, but that’s trapped in the browser (Same-Origin-Policy restricts it to a server) and limited to WordPress as a source, therefore a more generalized Hyperglossary capability is needed, preferably as a standalone program, that can apply any glossary in a compatible format onto any target text that’s in a compatible format.

Towards the use of the same input file for both, the glossary input and the base text input, therefore enabling the hyperglossarization of existing XHTML webpages that come with an unaugmented glossary.

The last release of the “Change Tracking Text Editor 1” in a practical scenario requires the user to manually copy files around, so a new version should introduce dialogs to select input sources and output targets

When opening a plain text file that ends with a linebreak and immediately leaving/saving, the import adds additional whitespace to the add instruction.

30 entries.

60 entries.

90 entries.

120 entries.

151 entries. This chunk included the FidoNet Tapes that count as one entry.

This is a discussion of the quote “the conversation is the work” by David Whyte, often cited by/in conversation communities for a description of what they do.

Only reading it because Gyuri Lajos said that it is important for understanding his approach. As suspected, the book hardly contains anything I didn’t already personally know myself before reading it.

82 pages.

163 pages.

245 pages.

326 pages.

407 pages.

This is a one-time manual process as I’m too lazy to adjust the wordpress_retriever_1 workflow a little to incorporate the publication date in the file name and import the text to a revision history.