Replied to a post by AmandaAmanda (arush.io)

OK   and , I have an official announcement.

John @whiskeydragon1 and I are getting married on June 19 2021.

There’ll be something virtual for those who can’t make it, and we’re still trying to figure out accessible wedding invitations because there is no way I am having a wedding that some of my friends can’t participate in.

We’re in the initial stages of planning, so we don’t have every detail worked out yet. But I am so happy and excited.

Best wishes Amanda! That’s great news!
Replied to a tweet by christina (Twitter)
Brid.gy can handle that for you.
Replied to a tweet (Twitter)
@withKnown supports Micropub, so you could use @ThreadReaderApp to do it in the other direction before WordPress could. 

https://boffosocko.com/2020/05/28/threadreaderapp-micropub-to-blog/
Replied to a thread by Dave Winer and @chaodoze (Twitter)
They released the feature earlier this year to work via Micropub. I wrote about their early UI here: ThreadReaderApp now has beta support for the Micropub Spec so you can publish Twitter threads directly to your blog. The nice part is that it works for a dozen or more platforms (not just WordPress) that already support Micropub.

Another interesting option is @KevinMarks’s noterlive.com which will compile your threaded tweets for cutting/pasting HTML to your site. Perhaps one day he’ll add Micropub functionality as well?

Replied to Automatically sending Webmentions from a static website by James Mead (jamesmead.org)
I'd also like to find a way to say thank you to Aaron Parecki who built webmention.io and Ryan Barrett, Kyle Mahan, et al who built brid.gy. However, I can't see a way to do either and, indeed, the latter explicitly say "We don't need donations, promise." 
In the past, I’ve heard many of them say to make a donation or support the IndieWeb Open Collective instead.
Replied to Jetpack 9.0 to Introduce New Feature for Publishing WordPress Posts to Twitter as Threads by Sarah Gooding (WordPress Tavern)
Jetpack 9.0, coming on October 6, will debut a new feature that allows users to share blog posts as Twitter threads in multiples tweets. A recent version of Jetpack introduced the ability to import and unroll tweetstorms for publishing inside a post. The 9.0 release will run it back the other way so the content originates in WordPress, yet still reaps all the same benefits of circulation on Twitter as a thread.
It’s awesome to see this feature added and that it expands the ability to do do this sort of workflow directly from one’s website instead of relying on posting to Twitter and relying on ThreadReaderApp to unroll a thread and post it to a WordPress site using the flexible Micropub specification. I’d love to see more POSSE (Post to your Own Site, Syndicate Elsewhere) syndication set ups within WordPress.

I’m hoping that future versions of this provide the Twitter permalinks for the syndicated copies there to be returned to my WordPress site for storage. In my case, I’m using the simple Syndication Links plugin which has storage and/or finds the storage location in WordPress to allow for the display of those permalinks in my post to indicate where I’ve syndicated the copies. This does two things: it’s a reminder of where my content lives elsewhere on the web (especially if I later want to go back and delete them, or to delete them if I’m deleting or making the original post private/unpublished) and it allows services like Brid.gy to find my original post and backfeed replies to the Twitter versions back into the comments section of my post using the Webmention spec (via the Webmention plugin and the Semantic Linkbacks plugin).

Replied to a post by Chris AldrichChris Aldrich (BoffoSocko)
Testing out adding email reply links to my RSS feed using the All In One SEO plugin documentation at: https://semperplugins.com/documentation/rss-content-settings.
It’s not exactly what I want yet because it doesn’t have an easy way to include the title of the post or the permalink to provide context, but it at least includes an email address.
Replied to a thread by Ian Guest, Aaron Davis, and John Johnston (Twitter)
Keeping my follows on my site as an OPML file allows me to use Inoreader for OPML subscribe. Then I can use their built-in search (and saved searches) to get information from personal websites I’m following.
Replied to IndieWebCamp: Domain of One’s Own Meetup by Jim GroomJim Groom (bavatuesdays.com)
This past Tuesday I attended the second Indie WebCamp generously hosted by Chris Aldrich focused on Domain of One’s Own. The format is a more focused 10-15 minute talk around a specific technology, in this meeting Tim gave folks a walk-though of Reclaim Cloud, and then opens up to the 21 attendees for anyone to share something they are working on. Tim shared the Cloud, and not only was I thrilled to see Jon Udell in attendance, but it’s always nice when one of your tech heroes tweets some love for your new project. Even better when you know they’re not one to offer empty interest and/or praise. Thanks Jon!

Soon after I finally took the leap and signed up for a mico.blog to explore that platform. 

Be sure to check out how you can post your content to your own website and syndicate your material into micro.blog (maybe via RSS or using plugins). If your site uses the Webmention and Semantic Linkbacks plugins, then any replies to your posts will be automagically ported directly back to the comment section of your post.

In addition to some of the others in education who you’ve mentioned, I’ve got a list with some others (be sure to check the comments too–both for the others you’ll find, but also for the example Webmentions I’ve received from Micro.blog.)
Annotated on September 26, 2020 at 01:57PM

I am going to start getting serious about headless WordPress development for my new website at jimgroom.net, inspired by Tom Woodward’s talk for #HeyPresstoConf20 

A lot of the posts I make to my WordPress site are done in a headless manner using the Micropub spec and the Micropub plugin with a huge wealth of Micropub clients.

I did a presentation on this at a WordCamp a while back: https://wordpress.tv/2019/06/26/chris-aldrich-micropub-and-wordpress-custom-posting-applications/
Annotated on September 26, 2020 at 01:59PM

Chris Aldrich 

By linking my site here, Jim has sent a Webmention notification, so I know he posted about my site: https://telegraph.p3k.io/webmention/14qD8olgI7lyGjRy0q/details
Annotated on September 26, 2020 at 02:27PM

Replied to a thread by Nicholas Rempel and Adam Greenough (Twitter)
I need to go back and revise it a bit, but I built a bit of UI for doing just this with Webmention: https://boffosocko.com/2017/12/24/adding-simple-twitter-response-buttons-to-wordpress-posts/

The other piece requires being able to thread conversations. Details for that here: https://boffosocko.com/2018/07/02/threaded-conversations-between-wordpress-and-twitter/

Replied to a tweet (Twitter)
I send Webmentions for reads and listens to notify authors, but I’m waiting for reading/podcast apps that will allow me to authenticate and make read/listen posts via micropub automatically, or versions that will send even generic notifications via webmention.

The nice part is that this sort of model allows the user to collect this data and send these notifications on an as-desired basis to the publisher.

Replied to @-mention when posting to Twitter · Issue #527 · snarfed/bridgy by Stephen Paul WeberStephen Paul Weber (GitHub)

Twitter interprets microsyntax whenever you post. There's no way around it. So if you have a post whose plain text says "Blah blah with @singpolyma" there is no way to tell twitter that "@singpolyma" is not the user named "singpolyma" and it will notify said user no matter what. In a silo this works, but when bridging to a federated environment it can cause issues (and especially annoyance of Twitter users).

One way to deal with this is to have my local implementation detect any such cases and not bridge them to Twitter, but this is not ideal. What should brid.gy do if it is asked to post something with the text @singpolyma in it? Here is my proposal:

  1. For the source HTML @singpolyma I would suggest changing it to "@ singpolyma", however I could see an argument to also leave it as-is, since some users might be writing plain-text microsyntax and expecting it is always going to Twitter? Hmm.
  2. For the source HTML @<a href="https://twitter.com/singpolyma">anything</a> put "@singpolyma" into the tweet.
  3. For the source HTML @<a href="https://singpolyma.net">anything</a> put "@ singpolyma.net" into the tweet.

Thoughts?

Not necessarily a permanent solution for all platforms and microsyntaxes depending on the number of syndicated copies, but potentially a clever stopgap for those who may need it. 

One can use a zero-width space (using something like &#8203;in their HTML) between the @ and a twitter user name on the original post and the syndicated copy will not have the traditional @mention link or notification functionality. 

Here’s an example

This reply can also serve as a test for the functionality within Github where I’ll “tag” both @kylewm and @​snarfed, but if it works, Ryan shouldn’t be auto-linked or notified.

Replied to Process for updating a proposed h-entry property · Issue #25 · microformats/h-entry by Tantek ÇelikTantek Çelik (GitHub)

The current h-entry change control process does not specify how to update the definition of a proposed feature, which means it falls back to being as strict as updating a stable feature which is more strict that desired for proposals. This issue is for considering a proposal for updating the definition of a proposed feature, as discussed during the recent Microformats Issue Resolution pop-up.

Proposal: the definition of a proposed feature may be updated to be more consistent with one or more real world public web sites publishing and or consuming the feature, by citing URLs for those examples in an edit summary. New proposed property or value definitions may also be added for consideration per the existing requirements for adding a proposed feature. If you’re not sure whether to update an existing definition or add a new definition, try to work with the proposer(s) of an existing definition to come to a consensus to update it. Lacking consensus, add a new definition for consideration, retaining any previous definition(s).

This proposal also adds a convergence requirement for moving a feature from proposed to draft. If there are multiple definitions for a proposed feature, an issue must be opened to discuss how to converge the definitions by consensus agreement among those with real world public web sites publishing and or implementations consuming the feature.

This is a rough first draft, feel free to propose alternatives, simplifications, editorial suggestions.

(Originally published at: https://tantek.com/2020/259/b2/)

This is acceptable to me. No further ideas or revisions at this time.
Replied to Social Interactions on the Web by James Gallagher (jamesg.blog)
I am using the Quill client to send data to my site. I have not tried out any other micropub clients but I could if I wanted to. They all support the same standard. 
Given the way you’ve described your uses, you might appreciate the browser extension Omnibear as a micropub client.

Replied to Social Interactions on the Web by James Gallagher (jamesg.blog)
When I think about it, likes and bookmarks are somewhat difficult to distinguish for my purpose. A bookmark inherently implies that I liked a post because I usually only bookmark posts on Pocket that I like and want to save for later. I use Firefox bookmarks to track the articles that I have not yet read and want to come back to later. There is a distinction. A like is clearer. It’s my way of saying that I did like your content. Not everybody will know my policy on bookmarks, so having a like feature is useful. 
My general heirarchy is that bookmarks are things I want to come back to (and usually read) later, reads are things that I’ve read, like are things I’ve read and want to send appreciation for, and replies are things that usually are both read, liked, and needed even a bit more.
Here’s more on how I’ve thought about it before: https://boffosocko.com/2018/03/10/thoughts-on-linkblogs-bookmarks-reads-likes-favorites-follows-and-related-links/