Category: metablogging

subscribe to this category with rss

Posted on
by

In 1967 French literary critic Roland Barthes declared the death of the author (in English, no less). An author’s intentions and biography are not the means to explain definitively what the meaning of a text (of fiction) is. It’s the reader that determines meaning.

Barthes reduces the author to merely a scriptor, a scribe, who doesn’t exist other than for their role of penning the text. It positions the work fully separate of its maker.

I don’t disagree with the notion that readers glean meaning in layers from a text, far beyond what an author might have intended. But thinking about the author’s intent, in light of their biography or not, is one of those layers for readers to interpret. It doesn’t make the author the sole decider on meaning, but the author’s perspective can be used to create meaning by any reader. Separating the author from their work entirely is cutting yourself of from one source of potential meaning. Even when reduced to the role of scribe, such meaning will leak forth: the monks of old who tagged the transcripts they made and turned those into Indexes that are a common way of interpreting on which topics a text touches or puts emphasis. So despite Barthes pronouncement, I never accepted the brain death of the author, yet also didn’t much care specifically about their existence for me to find meaning in texts either.

With the advent of texts made by generative AI I think bringing the author and their intentions in scope of creating meaning is necessary however. It is a necessity as proof of human creation. Being able to perceive the author behind a text, the entanglement of its creation with their live, is the now very much needed Reverse Turing test. With algorithmic text generation there is indeed only a scriptor, one incapable of conveying meaning themselves.
To determine the human origin of a text, the author’s own meaning, intention and existence must shine through in a text, or be its context made explicit. Because our default assumption must be that it was generated.

The author is being resurrected. Because we now have fully automated scriptors. Long live the author!

Posted on
by

Bookmarked The 100 Year Plan (by Automattic/WordPress)

WordPress is offering a century of managed hosting for 38.000USD, I presume upfront.

In reply to I’d love to understand what prompted Automattic to offer a hosting plan for $38K. by Ben Werdmuller

I don’t think this is a serious proposition by Automattic / WordPress.

  1. Who is in a position to put 38.000USD on the table right now, that they can’t use more usefully elsewhere? (even if in terms of monthly rates it’s not a large sum)
  2. Who believes Automattic, or any company, is likely to be around anno 2123 (unless they pivot to brewing or banking)? Or that they or their successor will honor such century old commitments (State guaranteed Russian railway shares are now just over 100 years old)?

I think it’s a way of getting attention for the last part of Matt’s quote at the end:

I hope this plan gets people and other companies thinking about building for the long term.

Matt Mullenweg

That is a relevant thing to talk about. People’s digital estates after they pass are becoming more important. I know how much time it took me to deal with it after my parents died, even with their tiny digital footprint, and even when it wasn’t about digital preservation mostly. Building code, hardware and systems to last is a valuable topic.

However if I want to ensure my blog can still be read in 100 years there is an easy fix: I would submit it to the national library. I don’t think my blog is in the subset of sites the Dutch Royal Library already automatically tracks and archives, even though at 20+ years it’s one of the oldest still existing blogs (at the same url too). However I can register an ISBN number for my collected postings. Anything published in the Netherlands that has an ISBN number will be added to the national library’s collection and one can submit it digitally (preferably even).

I think I just saved myself 38.000 USD in exchange for betting the Royal Library will still exist in 2123! Its founding was in 1798, 225 years ago, so the Lindy effect suggests it’s likely a good bet to give it another century or two.

Posted on
by

On the internet nobody knows you’re a dog.

Peter Steiner, 1993

It seems after years of trollbots and content farms, with generative algorithms we are more rapidly moving past the point where the basic assumption on the web still can be that an (anonymous) author is human until it becomes clear it’s otherwise. Improving our crap detection skills from now on means a different default:

On the internet nobody believes you’re human.

until proven otherwise.

Posted on
by

Bookmarked Inside the secret list of websites that make AI like ChatGPT sound smart (by By Kevin Schaul, Szu Yu Chen and Nitasha Tiku in the Washington Post)

The Washington Post takes a closer look at Google’s C4 dataset, which is comprised of the content of 15 million websites, and has been used to train various LLM’s. Perhaps also the one used by OpenAI for e.g. ChatGPT, although it’s not known what OpenAI has been using as source material.

They include a search engine, which let’s you submit a domain name and find out how many tokens it contributed to the dataset (a token is usually a word, or part of a word).

Obviously I looked at some of the domains I use. This blog is the 102860th contributor to the dataset, with 200.000 tokens (1/10000% of the total).


Screenshot of the Washington Post’s search tool, showing the result for this domain, zylstra.org.

Posted on
by

For some time I have been able to directly post things to this blog from my feed reader. My feed reading client is connected to a simple feed server, the Yarns WordPress plugin. Now I have connected my feed reading client to the API of the FreshRSS instance I use for feedreading daily.

The Yarns feeds server works, but it requires a WordPress install to run in and is somewhat limited. I could run it in this here WordPress, but then the many feeds I follow would pollute my blogs database. So until now I ran it in a separate WordPress install. All a bit hacky, and more proof of concept than really a smooth fit for my daily routines.

I do however daily use FreshRSS, which I run as a self-hosted instance on a VPS. FreshRSS has an API, or rather it has two API’s, meaning that I could run my feed reading client on top of FreshRSS by talking to its API.

FreshRSS has two APIs, one is the Fever API, the other is the Google Reader API of old. Both aren’t very well documentend w.r.t. their implementation in FreshRSS, because they assume you’d use it for a mobile client using a local database. I don’t want to replicate the database, I want to only directly talk to the API to fetch the things I need. After some experimentation in Postman I could talk to the Fever API, but haven’t worked out how to talk to the Google Reader API of FreshRSS.
The Fever API doesn’t support calling items by feeds and feeds by groups, the way I actually read in my ‘reading by social distance set-up‘. It can give me groups, feeds and items, but not cross-referenced. In terms of content it can basically only give me a bunch of feed items, at most limited by the item number of the oldest unread item. But it works. The previous post was created directly from my feed reading client, while fetching the item itself from FreshRSS.

Now, I need to figure out how to use the other API, so I can do more of the things that I want from my ideal RSS reader.

In reply to Ik schrijf een blogpost vanuit… by Frank Meeuwsen

Helemaal eens. Maar ik merk ook hoe ik toch meestal in de back-end van WordPress begin te schrijven. Terwijl elke keer dat ik dat niet doe maar mijn eigen schrijfomgeving gebruik, het zoveel prettiger voelt. Dit schrijf ik vanuit mijn experimentele feedreader. Vanuit mijn Obsidian notities bloggen is helemaal frictieloos in mijn beleving. En toch is het nog lang geen automatisme om als ik denk dat ik wat wil bloggen het dan in Obsidian te doen. Toch grijp ik dan desondanks haast vanzelf naar WordPress. Ik weet nog niet hoe ik mezelf hierin tot een andere gewoonte breng.

…prettiger dan de blokkendoos die WordPress in zijn Gutenberg editor heeft. Het belangrijkste is dat je met je eigen blog net zo makkelijk je eigen schrijfomgeving kunt kiezen. Eén die bij jou past…

Frank Meeuwsen