Yes!
- HTML for semantics and accessibility
- CSS for layout and visual aesthetics, and
- JavaScript, progressively enhanced, for interactivity when it cannot be achieved natively
NetzArtist
I use a personalised feedreader (running on top of a self-hosted instance of FreshRSS‘s API that handles the RSS subscriptions) since about 4 years.
My feedreader allows me to interact with the Web, not just read it. I can post to this blog (and a few other websites) directly from it and keep reading my feeds. Same for adding an annotation to Hypothes.is, and for adding a note in markdown to my filesystem in the folder where Obsidian lives.
Recently I mentioned I want to make my habit of annotating web postings in my Hypothes.is easier to keep up.
As I wrote then:
… currently from within my feedreader I can post to either my blog or to Hypothes.is, but not both. I want to change that, so that the same thing can serve two purposes simultaneously.
I now have adapted my feedreader interface and related scripts to do just that.
It can post to a few websites AND to hypothes.is AND to Obsidian all at the same time now. It used to be either just one of the sites, hypothes.is or Obsidian. Posting to both hypothes.is and Obsidian simultaneously won’t happen a lot in practice as my hypothes.is annotations already end up in Obsidian anyway. I use the saving to Obsidian mostly to capture an entire posting, where I use hypothes.is in my feedreader to just initially bookmark a page so I might return later to annotate more. The current version of the response form in my feedreader is shown below.
One element I added to the interface that I haven’t coded yet in the back-end: posting to my personal and/or my business Mastodon accounts. [UPDATE I did that now too]. When Now that is done, I can write to all the places I write the web, right from where I read it, as in Tim Berners Lee’s original vision:
The idea was that anybody who used the web would have a space where they could write and so the first browser was an editor, it was a writer as well as a reader. Every person who used the web had the ability to write something. It was very easy to make a new web page and comment on what somebody else had written, which is very much what blogging is about.
In reply to a bookmark by John Johnston
The templates contain what I want to have inside a blogposting for a reply, favourite, bookmark, rsvp or check-in. I apply them before I submit something to WordPress, so they are fully outside of my blog and get send as HTML to my blog.
Two main ways: if I type something in my editor (e.g. WordPress back-end or in my local text editor) I have text expansion snippets that paste the right template into my text. The little header above this post with the SVG image and the bit that contains the right microformat, I add by typing .ureply, and I have similar set-ups for .ufav, .ubmark, .ursvp and .uplaze. This is what I did to reply to you now.
A second way is that I have integrated these same little templates into the response form I have in my feedreader, and in a little blogform on my local device. There I indicate with a radio button if something is a reply etc, and the php script that processes the form adds in the right HTML before sending it to my WordPress site’s micropub endpoint.
I wonder if these are an alternative to IndieBlocks or something else.
John Johnston
What makes the plugin useful is that it allows you to turn postings into different, well, kinds of posts. Such as a reply, or a check-in, rsvp, bookmark or favourite. It adds the right microformats so that computers can semantically analyse a post’s purpose, and adds the styling to display them.
My main issue with it was that it places key elements such as the weblink you’re responding to outside the posting itself. It gets stored in the database as belonging to the PostKinds plugin. Meaning if you ever switch it off, that gets wiped from your posting (although it’s still in the database then). This was a dependency I needed to get rid of.
For new postings from summer 2021 I did that by deploying small templates that allow me to mark a posting as reply, rsvp, favourite, bookmark, or check-in, within the postings I’m writing.
I used the PostKinds plugin heavily for 3 years, and most heavily in 2019. That legacy from 2018-2021 was still there, requiring the PostKinds plugin to remain enabled. Until today. Over time I had slowly changed posts when I encountered them, and in the past week I did the remainder.
Another issue is that PostKinds only works in the classic WordPress editor, and not in the now default Gutenberg editor. At some point that would hinder the ability to upgrade WordPress.
Solong PostKinds, thanks for all the fish!
In reply to Een rsvp op Seblog by Sebastiaan Andeweg
Have fun, it’s been a while since I visited (or rather organised) an IndieWebCamp. Dropped of the radar somewhat. Mostly as I was playing around with the local stuff that interacts with my website but isn’t my website, and with ActivityPub. Less IndieWeb in other words than indie personal tools. Didn’t feel those tangents fit the IndieWebCamp community or efforts.
Maybe we should organise an IndieWebCamp in NL at some point again?
I will be going to IWC Nuremburg this weekend.
Sebastiaan Andeweg
Bookmarked Twitter Has Stopped Working in NetNewsWire (by NetNewsWire)
By the end of the month the free tier of the Twitter API will disappear. Some apps using the API will stop doing so because of too high costs to continue, such as Brid.gy. Others are being kicked out by Twitter itself even before the deadline at the end of April, such as Netnewswire. These steps have one thing in common: they disable the ability of reading Twitter without using Twitter directly. Tightening the walls of the silo, in short. The Web is much better off with at least semi-permeable boundaries between services, so that one can interact and read from their own preferred perch. That of course clashes with various business models, although at this point I’m not sure Twitter knows what its businessmodel is supposed to be.
Twitter suspended NetNewsWire today. …. Twitter has stopped working a little sooner than expected. We’ll have updates to NetNewsWire soon that stop trying to connect to Twitter
English