I’m hanging out on Beatsense playing some music if anyone wants to join in: https://beatsense.com/limbo#/ cc @girlvsplanet @jdragz @spiffiness03

Francesco Schwarz Francesco Schwarz on francescoschwarz.com:
Thanks a lot for the explanation!

I’m already sending webmentions via Bridgy Publish. I altered your module to optionally include the publish URLs for (in my case) Twitter and Mastodon. I’ve done this in this file around that line. I’ve added a checkbox in my notes called “Post to Bridgy?”, and when that is checked I append the Bridgy publish URLs to $page->{$field} as additional URLs to process for webmentions.

The core of what I need is what you wrote here:

I wrote some more code that processes that response to get the tweet’s URL and updates the syndication link on the note.

That’s basically exactly what I’m looking for. I see if I can achieve that by myself, playing a bit around with it.

But thanks again for you reply, that clarifies a lot for me. And it’s also a bit sobering to see that apparently it’s really not that easy to automate the process. Looking around at all the #indieweb blogs and seeing all the syndicated links on notes frankly I felt quite stupid not understanding how all this folks are doing this automatically. Also one really can’t find a whole lot information around the web, which adds to the problem.

That’s an interesting approach to add the Bridgy Publish webmention. I’m glad it’s working well for you.

My approach is still part of the template files. I just reviewed it and it’s fairly simple, so I’m comfortable sharing it. Here is a gist. Let me know if you have any questions.

I’m excited to see more ProcessWire sites with webmention. I’ve not heard from a lot of people using the module yet. I’m definitely interested in improving the indieweb experience on ProcessWire. Bridgy Publish is an area that I have not worked on yet, partly because people can have templates set up a variety of ways and I’m not sure how to make a plugin that works with different setups.

By the way, we’ve been having weekly virtual indieweb meetups if you’d like to join. I think the closest timezone would be the London meetup. Check out events.indieweb.org for upcoming events. We have an active community chat as well: indieweb.org/discuss.

Francesco Schwarz Francesco Schwarz on twitter.com:
@gRegorLove How is your workflow when posting a note in ProcessWire and automatically posting it to Twitter via Bridgy? Where do you add the Bridgy webmention endpoint URLs? Or do you use another method?

I’ve used a variety of approaches over the years, from manual to semi-automatic. Here’s some different things I’ve done:

Initially I would publish a note, then use the interactive Bridgy Publish form from my account page. Your account page is https://brid.gy/twitter/isellsoap. Paste the URL of your note there, choose the options whether you want your original link appended to the tweet, then preview it. If it looks good, publish it. I then would copy the tweet’s URL and add it on my original note as a syndication link. See below on this note for an example of that syndication link.

After I did that for a while and it was working smoothly, I started to automate it more. Bridgy Publish lets you send a webmention to trigger the publish. I set up a custom bit of PHP code that would let me click a button to send off that webmention for the note I wanted to publish. Sending a webmention is a pretty simple POST request, so I used the WireHTTP class for that. When publishing to Twitter, the successful Bridgy response includes the Twitter API data for the tweet. I wrote some more code that processes that response to get the tweet’s URL and updates the syndication link on the note.

Note that all of this is separate from the Webmention plugin itself. The code for my semi-automatic publishing isn’t part of a plugin and isn’t very polished code, so I haven’t released any of it. If I can find a way to make it more user-friendly, I might release it, or at least write a tutorial with more guidance.

https://php.microformats.io is a useful tool to debug the microformats in your posts, by the way. Here’s the parsed result of this very note. The in-reply-to property is what Bridgy Publish uses to post a reply tweet. The syndication property is one way Bridgy maps your original post to the Twitter copy for sending responses back to you — particularly if you don’t include your original post link in the tweet.

I am proposing a session for IndieWebCamp West Coast: “Keeping Track of Books and Reading Progress.”

I would like to discuss the use-cases and experiences of using our websites to:

  1. track books we want to read
  2. categorize (or “shelve”) books
  3. track reading progress

Most of my personal experience has been around tracking books I want to read. It is probably more accurate to classify those as want posts instead of read posts. I’d like to discuss the differences between these three types of posts and what they look like on our sites. Regarding categorizing books, we should also discuss Library JSON.

This session is broader than indiebookclub but will likely have an impact on it. indiebookclub creates posts with a status of to-read, reading, or finished. The first is probably a want post and the others seem to be reading progress posts.

@sonicrocketman: I noticed I wasn’t seeing your feed in Monocle. It looks like your jsonfeed doesn’t validate: https://validator.jsonfeed.org/?url=https%3A%2F%2Fpine.blog%2Fu%2Fsonicrocketman%2Ffeed.json

I subscribed to your microformats feed and that’s working smoothly!

Todd Grotenhuis Todd Grotenhuis on blog.grotenhuis.info:
Remember all those apps/sites where you could create a daily/weekly newspaper from links and posts in your social feeds? Do any of those still exist?

https://paper.li/ still exists. If you use it, please don't have it auto-tweet them though. XD

Want to read: How to Be an Antiracist by Ibram X. Kendi (ISBN 9780525509288)

via Episode 229 - White Homework with Tori Williams Douglass

selfie while laying on the couch with my arm behind my head

Felt cute, might quarantine later

giant robot face with text 'made in austin'

Remembering my trip to Austin in the Before Times (February).

Want to watch Give Me Sex Jesus

What happens when a generation of Christian youth pledge sexual abstinence until marriage? Since the 1990s, the Purity Movement has been at the center of the national sexual conversation extending past the pew and all the way into the Oval Office. Including some of the leading experts on Evangelicalism today, Give Me Sex Jesus invites you into the guilt, pleasure, shame, and humor of sorting out faith and sex in America.

Michael Gungor Michael Gungor on twitter.com:
The reason I don’t just PR this and say that I agree with these advocates to save myself from the mob of cancel culture is because I believe this sort of thinking that is prominent in progressive circles is a type of fundamentalism that actually hurts people more than it helps.

“save myself from the mob of cancel culture” does not read as a good faith interpretation of the reactions you received.

screenshot of my Animal Crossing avatar wearing an IndieWebCamp shirt

Represent the #indieweb on your Animal Crossing island! To get your own, access the kiosk in the Able Sisters store and search for Design ID MO-5MDH-M0LJ-3MX1.

Also, if you want to visit my island, add me as a Switch friend.

cover of Mike McHargue's book, You're a Miracle (And a Pain in the Ass)

Really looking forward to reading Mike McHargue’s new book! I also highly recommend his podcast, Ask Science Mike, and his first book, Finding God in the Waves.

Jeremy Keith Jeremy Keith on adactio.com:
At the beginning of the year, Remy wrote about extracting Goodreads metadata so he could create his end-of-year reading list. More recently, Mark Llobrera wrote about how he created a visualisation of his reading history. In his case, he’s using JSON to store the information.

This kind of JSON storage is exactly what Tom Critchlow proposes in his post, Library JSON - A Proposal for a Decentralized Goodreads:

Thinking through building some kind of “web of books” I realized that we could use something similar to RSS to build a kind of decentralized GoodReads powered by indie sites and an underlying easy to parse format.

His proposal looks kind of similar to what Mark came up with. There’s a title, an author, an image, and some kind of date for when you started and/or finished reading the book.

Matt then points out that RSS gets close to the data format being suggested and asks how about using RSS?:

Rather than inventing a new format, my suggestion is that this is RSS plus an extension to deal with books. This is analogous to how the podcast feeds are specified: they are RSS plus custom tags.

Like Matt, I’m in favour of re-using existing wheels rather than inventing new ones, mostly to avoid a 927 situation.

But all of these proposals—whether JSON or RSS—involve the creation of a separate file, and yet the information is originally published in HTML. Along the lines of Matt’s idea, I could imagine extending the h-entry collection of class names to allow for books (or films, or other media). It already handles images (with u-photo). I think the missing fields are the date-related ones: when you start and finish reading. Those fields are present in a different microformat, h-event in the form of dt-start and dt-end. Maybe they could be combined:

<article class="h-entry h-event h-review">
<h1 class="p-name p-item">Book title</h1>
<img class="u-photo" src="image.jpg" alt="Book cover.">
<p class="p-summary h-card">Book author</p>
<time class="dt-start" datetime="YYYY-MM-DD">Start date</time>
<time class="dt-end" datetime="YYYY-MM-DD">End date</time>
<div class="e-content">Remarks</div>
<data class="p-rating" value="5">★★★★★</data>
<time class="dt-published" datetime="YYYY-MM-DDThh:mm">Date of this post</time>

That markup is simultaneously a post (h-entry) and an event (h-event) and you can even throw in h-card for the book author (as well as h-review if you like to rate the books you read). It can be converted to RSS and also converted to .ics for calendars—those parsers are already out there. It’s ready for aggregation and it’s ready for visualisation.

I publish very minimal reading posts here on adactio.com. What little data is there isn’t very structured—I don’t even separate the book title from the author. But maybe I’ll have a little play around with turning these h-entries into combined h-entry/event posts.

Have you tried the indiebookclub Micropub client? Based on my usage of that, I wrote up some brief thoughts about using separate citation and review posts. That doesn't capture reading progress yet, but it's on the list of things I'm thinking about for indiebookclub.