• Personal Hypertext Report #6

    Stephan Kreutzer doesn’t want to work on a WordPress enhancement: the current posts on the default installation broke XML processing by a non-browser client because of a named DTD entity and bugs in WordPress’ wpautop() function – both unnecessary problems caused by the general web context, too expensive to fix and difficult to work with. There’s great consensus that the first project, the jrnl, should be a WordPress enhancement project. I’m happy with that as a good practical compromise for bootstrapping ourselves: it’s readily available and many people know how to set it up and/or use it, it’s libre-freely licensed (not ideal though, GPLv2 makes no sense for software that…

  • What Sucks about Blogging

    We had the inaugural meeting of the jrnl project yesterday and we decided to write a blog post each of what sucks about blogging, with hopefully some useful issues coming out of that for us to work to improve. We could of course also list suggested improvements in the process. View Flexibility For me the single biggest issue is the lack of view flexibility. Even such a simple thing as viewing all the posts by a specific set of people in one timeline is only possible if they are on the same blog, it’s not possible cross-domains. Also, something as simple as saying I want to see all the paragraphs…

  • Initial Meeting Summary Report

    (As emailed to the team): Thank you to those of you who joined the call and those who tried 🙂 We had a good introductory chat and decided that we will reconvene in two weeks, on the 7th of September at the same time, 5pm UK time, 9am California time. I will upload the audio recording when I can, we are moving house today and tomorrow so it’s all a bit technically disorganised here right now. We decided on starting with EVERYONE writing a blog post on jrnl.global titled “Why Blogging Sucks’ where we outline the problems with current blogging, even if it’s simply a rant, and hopefully from that…

  • Re: jrnl launch meeting announcement (for Friday 24th of August 2018)

    This is a reply to “jrnl launch meeting announcement (for Friday 24th of August 2018)”. It’s a little surprising that the Journal/jrnl in an already very, very specific form is supposed to be the main topic, despite it’s still unclear to which extent the potential participants write about their research and work or plan to, or if that should be the main interest or first strategic goal for now. For a long time, I keep repeating that even WordPress comes with many problems, I wonder who’s supposed to work on these. The proposal continues to suggest that the jrnl should exist as just another blog or website, following the traditional…

  • Re: Friday

    Today, Frode Hegland officially confirmed the first meeting of the Future of Text Institute on the 2018-08-24. With that I received a mail from him, to which I was asked to reply, so I try to do it here. The meeting will introduce the “jrnl” software project, an attempt to make a more Engelbartian blog system, likely the first major topic for the FTI. As it became possible to study Douglas Engelbart’s ARC Journal in more detail, it looks like NLS and Journal are quite distinct and relatively independent from each other, which allows for both to be investigated and recreated as a capability separately. If we would want to…

  • Teodora Petkova

    Hello! I am Teodora. What brought me here, at jrnl is my interest in the way our textual existence on the Web evolves. My name is Teodora and I believe, on the Web, we exist in the form of textual threads. Something more, on the Semantic Web we are intertextual beings, weaving narratives into an ever expanding fabric of relationships. This digital intertextuality combined with the power arising out of open narratives made of data and stories, is what intrigues me. You will find me mostly in my writing at teodorapetkova.com and thebravenewtext.com. 

  • Stephan Kreutzer

    I maintain an updated profile on my about page that includes a collection of links which lead to my other online presences and projects. For the context of this effort, I also describe most of my earlier and current work in this article. My contributions to this initiative usually won’t reside on this site as I’m able to build and run my own hypertext systems that hopefully will compose material from different sources into a virtual space or combined rendering, something like that. My results can be found on publishing-systems.org for automated conversion workflows and single-source, multi-channel publishing (working with legacy, bookish-style material), complemented by hypertext-systems.org for the more hypertexty…

  • RFC: Glossary Data Formats

    First stage For now, we can use the following format to specify glossary entries for the Journal: <dl> <dt>Media Fragment</dt> <dt>Media Fragments</dt> <dd>Paragraphs, datasets, images, topic maps, glossaries… that go into forming one or more document(s).</dd> <dd>This glossary entry is a media fragment, and each of its parts could be as well.</dd> </dl> As the Journal is currently stored in WordPress, we might use its data model to some extend, but will abandon that more and more by abusing it as generic online data storage, where any arbitrary data is stored in the content-body of a blog post. This will render all plugins, themes and administrative tools on the server…