Replied to Why I Started Microblogging by Bryan Bryan (Bryan Sebesta)
So, I’ve started to microblog. I was inspired by Alan Jacobs’ recent article, getting back to the open web via micro.blog. One of the big reasons he supports starting a microblog this way is is because he owns the content; it’s part of his own domain, his turf. And that’s appealing to me. Ad...
Welcome to the game Bryan! Curious why you’re hosting your microblog separate from your main site instead of running them both from WordPress (not that you need to/have to)?

I’ve enjoyed linkblogging. When I read something, I can share the link along with a quote or reflection on how it affected me. It’s a great space to think out loud. 

Annotated on August 05, 2020 at 01:51PM

As Austin Kleon notes, blogging is a great way to discover what you have to say. My microblog has given me a chance to have thoughts, and this longer blog has given me a space to figure out what it means–to discover what it is I have to say. In other words, my microblog is where I collect the raw materials; my blog is where I assemble them into questions and, perhaps, answers. It’s a place where I figure out what I really think. 

Annotated on August 05, 2020 at 01:54PM

Replied to a tweet by Aram Zucker-ScharffAram Zucker-Scharff (Twitter)
to the rescue. There are a few great options for this. None of which should require you to write any code! 

One of my favorite is Kevin Marks’ Noter Live (open source) which is great for live tweeting and creating long threads quickly, especially at conferences. When you’re done, it’s kept a record of everything which you can quickly cut/paste as HTML into your website for an instant archive post.

Another option if your website supports the Micropub spec (perhaps with a plugin?) ThreadReaderApp recently added support to let you unroll the thread and you can go to your account and authenticate to your website and post the thread with one click.

I’ll also note that WordPress’ Gutenberg just added the ability to unroll threads to websites built with it as well. 

In addition to general public use, these could actually be the backbone of an interesting journalistic live notebook for reporters in the field who could quickly compile/archive their threads for expanded articles later on.

Replied to a tweet (Twitter)
Ada, it’s a new feature, but if you go to https://threadreaderapp.com/account/author, you can authenticate to your website and post the thread to your blog as an article for posterity.
Replied to a tweet (Twitter)
I’ve always loved OPML subscription: you follow an OPML source that automatically updates your feed over time. Sadly @inoreader is one of the few apps that supports it.
Replied to a tweet by Ian BrownIan Brown (Twitter)
interoperability FTW!
Replied to thread
Another option, though without Micropub (yet!), is Kevin MarksNoterLive tool. It’ll let you create a thread and then (manually) copy over the rich data into your website pretty quickly. I love it especially for conferences.
Replied to a tweet by Tracy DurnellTracy Durnell (Twitter)
Tracy, you’re not shouting into the void. If you’re interested, a few of us are hosting a free pop-up session that will cover that issue (and a lot more) in just a few weeks: Getting Started with WordPress, an IndieWebCamp Pop-up Session. Also happy to discuss it at any of the upcoming Homebrew Website Club Meetups too!
Replied to a post by Xandra (biglizardbooks.net)
Articles on Quill don’t seem to have the ability to syndicate to twitter and mastodo, so I might end up using micropublish. Bit frustrating to figure this all out, but also kind of fun to be honest.
If you use the Syndication Links plugin and configure it, Quill should be able to find your Twitter and Mastodon “endpoints” on your site and provide you with buttons to syndicate to them. 

It looks like your theme has an extra u-photo on it that’s causing that avatar image to be sent to Twitter by the way. The way the microformats are set up is also causing them (Syndication Links) to display too, but it’s fixable with some tinkering. You might try IndieWeb chat to see if someone can help you troubleshoot it.

Replied to a tweet by James Van Dyne (Twitter)
I do that! Try Micropub plugin + Syndication Links plugin + Quill or any of the other micropub clients that support posting notes and syndication endpoints.

Reach out if you need help to get it set up.

If you want to go crazy and thread your Twitter conversations, that’s possible too…

Replied to a tweet by CeliaMcKee (Twitter)
We definitely need to normalize “failure”. I remember a CV of Failures from @jhaushofer from a few years back.

with additional coverage.

Replied to Hovercards by Joseph DicksonJoseph Dickson (linuxbookpro.com)
A Hovercard also known as a h-card is a bit of content that’s shared about you on your website kinda like a visual/interactive business card. Implementation looks like Gravitar. It can contain far more information and is self-hosted.
Joseph, I thought I caught you say it during the demos, but wasn’t 100% sure. Reading this, confirms it. You’re conflating two different but very similar ideas.

h-card is a microformat class around the mark up of data about identity elements like names, addresses, cities, countries, and often including an avatar or photo. Hovercard is a UI element that creates a visual card when one hovers over a name or similar element that would contain h-card details. 

Gravatar serves some of these functions for WordPress from a centralized perspective. The data you would imput there would be wrapped with the h-card class, while Jetpack would give you the ability to display Gravatars as hovercards, so that when you hover over an avatar it will display more detail about the person in a small card-like UI.

For your experimentation purposes, you should be able to use just one post to test against my site. Once you’ve modified your theme, you can simply resend the webmention to my site and that will automatically update your original post. You don’t need to create new posts each time to test it out.

If you haven’t gotten it cleared up, do join us in the IndieWeb #WordPress channel, or catch us at an upcoming HWC event.

 

Outline for Webmentions in Conjunction with Academic Citations

Replied to a tweet by Terence EdenTerence Eden (Twitter)
I’ve noted before how Altmetric does what some would call backfeed, though I’m not sure what or how their mechanism works other than some heavy search and extreme processing from social media platforms.

Pingbacks are essentially dead and in personal experience some of the few sites that still support them are in academia, but they’re relatively rare and have horrible UI in the best of times. Webmention is a much better evolutionary extension of the pingback idea and have been rapidly growing since before the spec was standardized by the W3C. 

I’ve sketched out how individual academics could use their own websites and publish pre-prints and syndicate them to pre-print servers and even to their final publications while still leveraging Webmentions to allow their journal articles, books, other works, to accept and receive webmentions from other web publications as well as social media platforms that reference them. 

I think the Microformats process is probably the best standardized way of doing this with classes and basic HTML and there is a robust offering of parsers that work in a variety  of programming languages to help get this going. To my mind the pre-existing h-cite is probably the best route to use along with the well-distributed and oft-used <cite> tag with authorship details easily fitting into the h-card structure. 

As an example, if Zeynep were to cite Tessie, then she could write up her citation in basic HTML with a few microformats and include a link to the original paper (with a rel=”canonical” or copies on pre-print servers or other journal repositories with a rel=”alternate” markup). On publishing a standard Webmention would be sent and verified and Tessie could have the option of displaying the citation on her website in something like a “Citation” section. The Post Type Discovery algorithm is reasonably sophisticated enough that I think a “citation” like this could be included in the parsing so as to help automate the way that these are found and displayed while still providing some flexibility to both ends of the transaction.

Ideally all participants would also support sending salmentions so that the online version of the “officially” published paper, say in Nature, that receives citations would forward any mentions back to the canonical version or the pre-print versions.

Since most of the basic citation data is semantic enough in mark up the receiver with parsing should be able to designate any of the thousands of journal citation formats that they like to display any particular flavor on the receiving website, which may be it’s own interesting sub-problem.

Of course those wishing to use schema.org or JSON-LD could include additional markup for those as well as parsing if they liked.

Perhaps I ought to write a longer journal article with a full outline and diagrams to formalize it and catch some of the potential edge cases.