👓 The Follower Factory | New York Times

Read The Follower Factory by Nicholas Confessore (New York Times)
Everyone wants to be popular online. Some even pay for it. Inside social media’s black market.
A great story which just touches on the fringes of the reasons why it would be useful for many bots (particular kinds) to be banned from social media websites.

👓 Why You Should Put Your Content on Both Medium and Your Own Domain | sendcheckit

Read Why You Should Put Your Content on Both Medium and Your Own Domain (sendcheckit.com)
How to leverage your own site and Medium without duplicate content issues.

👓 Medium Acquires Superfeedr by Julien Genestoux

Read Medium Acquires Superfeedr by Julien Genestoux (ouvre-boite.com)
Today’s web is very different from what it was 8 years ago. We’ve said it several times: publishing and consuming content are new frontiers for most of the web giants like Facebook, Google or Apple. We consume the web from mobile devices, we discover content on silo-ed social networks and, more importantly, the base metaphor for the web is shifting from “space” to “time”. Superfeedr, the open web’s leading feed API and PubSubHubbub hub has been an independent player for 8 years. Superfeedr exists in order to enable people to exchange information on the web more freely and easily. Today, we’re excited to announce Superfeedr has been acquired by Medium. In many ways, it’s a very natural fit: Medium wants to create the best place to publish, distribute and consume content on the web. Together, we are hoping to keep Medium the company a leader in good industry practices, and Medium the network a place where this conversation can gain even more traction.

👓 The “indie” fallacy by Julien Genestoux

Read The “indie” fallacy by Julien Genestoux (ouvre-boite.com)
I consider myself a member of the open web community and very friendly with the goals of the IndieWeb community. I too wish for a world where web giants have less power and where the user is in control of more of their data. Yet, I now work for a large (the largest?) publishing platform. It is not often easy to reconcile, but one thing that I can tell you for a fact is that your data is, on average, safer on large hosting provider than it is on your small indie site.
I’d be curious to see more concrete numbers on these statistics, though I suspect that for “mature” sites, it may actually be the case. Some of the small, middling platforms however… The other side of the coin though is that when airplanes do crash, the death toll is seemingly large, and this is also the case with major silos.

While he mentions personal sites disappearing, it’s typically something that the site owner can often at least make a conscious choice to do and they can also mothball the data for later use. With a silo death, they really have no choice and often can’t get any data at all.

This just goes to point out that we need better solutions for both openness and longevity. How much of what I write on line will survive the next 500+ years? More or less than what Copernicus or Newton wrote? (Of course, who will care is an entirely different question…)

I hope that perhaps Medium opens up in the future to do some of the functionality that he mentions.

👓 The Google Arts & Culture App and the Rise of the “Coded Gaze” | The New Yorker

Read The Google Arts & Culture App and the Rise of the “Coded Gaze” by Adrian ChenAdrian Chen (The New Yorker)
Adrian Chen writes about the Google Arts & Culture app’s facial-recognition algorithm and how it relates to the ideas of John Berger and Joy Buolamwini.
A more subtle take on the Google Arts & Culture App than I’m seeing everywhere else.

🎧 Micro.blog on Social Media with Manton Reece | Geekspeak

Listened to Micro.blog on Social Media with Manton Reece by Lyle Troxell and Brian Young from GeekSpeak
We have been talking about the problems with Twitter, Facebook, and social media throughout the last year. Our guest has too, and he’s trying to do something about it. Manton Reece, talks about Micro.blog, the technology it is built on, and how he is being thoughtful about building something new.

Microblogging by Paul Robert Lloyd

Bookmarked Microblogging by Paul Robert Lloyd (paulrobertlloyd.com)
I stopped using Facebook because I didn’t trust the people behind Facebook. I had grown weary of the sly and underhand tactics used to grow their network and was unwilling to remain part of it. But if I’m honest, I couldn’t trust myself either. Visiting Facebook would elicit behaviour you could only describe as stalking; trawling through the feeds of my friends, seeking out people I vaguely knew. I had better things to do with my time. Almost a decade later, I’m having similar thoughts about Twitter.
He’s got some interesting, but subtle references to pieces of the “old” web including Small Pieces, Loosely Joined.
​​​​​​

👓 The IndieWeb outside of Facebook is full of opportunities | The Garage

Read The IndieWeb outside of Facebook is full of opportunities by Johannes Ernst (The Garage)
Promote your own site, or promote on Facebook? Turns out you can do both, and do even better: have your website join the IndieWeb.
Great piece, though I think it simplifies things a bit more than they’re easily capable of doing now for a Gen 2 person, which seems to be who this piece is geared towards.
I hadn’t been paying attention and Lanyrd, yet another social site I used to use, has apparently gone under. Wish I’d had some notice to extract my data out of the service before it raged into the dying of the light.

I ought to start a “dead pool” for making odds on the next social media sites to disappear.

Reply to What Was Known by Jim Groom

Replied to What Was Known by Jim Groom (bavatuesdays)
...the issue for me was Known was contextless for social media. I often post across various sites in response to things and share my photos as part of a conversation, so doing it through Known seemed a bit like working in a vacuum. I use Twitter less and less for discussion, so I wonder if I would feel different about this now, but what I wanted from Known was a way to also view and respond to Tweets, Facebooks statuses, photos on Flickr, Instagram, etc. A kind of reader for my content that would collapse those various conversations for me, and I could respond through my Known as if I was within those apps. I increasingly thought Known would make an awesome read//write feed reader if it had such a feature. The main reason Known fell by the wayside for me was I was not using it to publish in all these spaces, rather doing it post-facto if at all. Does that make sense?
Interestingly, Known had a lot of these features hidden in code under the hood. Sadly they weren’t all built out. It in fact, did have much of a reader (something which Ben indicated they were going to take out of the v1.0 release to slim down the code since it wasn’t being used). It also had a follow/following block of code (and even a bookmarklet at /account/settings/following) so you could follow specific sites and easily add them to your reader. Also unbeknownst to most was a built-in notifications UI which could have been found at /account/notifications.

It’s a shame that they put many of these half-built features on hold in their pivot to focus on the education market and creating a viable cash flow based company as this is the half that most CMSs lack. (If you think about what makes Twitter and Facebook both popular and really simple, I think it is that they’re 95% excellent feed readers with 5% built-in posting interfaces.)

I’ve managed to replace some of that missing functionality with Woodwind, a reader at http://woodwind.xyz, which one could connect with Known to do the reading and then integrate the posting, commenting, and replies to complete the loop. I do have a few very serious developer friends who are endeavoring to make this specific feed reader portion of the equation much easier to implement (and even self-host) to make the hurdle of this problem far lower, but I suspect it’ll be another 3-6 months before a usable product comes out of the process. For those looking to get more social into their feed readers, I often recommend Ryan Barrett’s appspot tools including https://twitter-atom.appspot.com/ which has instructions for extracting content from Twitter via Atom/RSS. It includes links at the bottom of the page for doing similar things with Facebook, Instagram and Google+ as well.

Interestingly there are now enough moving pieces (plugins) in the WordPress community to recreate all of the functionality Known has, one just needs to install them all separately and there are even a few different options for various portions depending on one’s needs. This includes adding reply contexts for social media as well as  both the ability to syndicate posts to multiple social sites for interaction as well as getting the comments, etc. backfeed from those social sites back into the comments section of your post the way Known did. Sadly, the feed reader problem still exists, but it may soon be greatly improved.

A Digital Food Diary on My Own Website

Food and Drink on my own website

I’ve been wanting to do it for a while, but I’ve finally started making eat and drink posts. The display isn’t exactly what I want yet, but it’s getting there. For myself and those reading, I’ll try to continue tweaking on templates, but with the start of the new year, I wanted to at least start capturing the basic data. Most of the heavy lifting will be done by David Shanske’s excellent Post Kinds Plugin.

I’m hoping that, much like the dieting advice about getting and using a clean plate for every single thing you eat, consciously posting will help me to subconsciously eat better too. I’ve already begun to notice some of the subtle effects, and not just for composing better photographs of my food.

I probably won’t post everything publicly after some time because, really, who really wants to see all this (perhaps aside from others interested in doing the same thing themselves)? Eventually it’ll probably devolve into only the more fabulous looking restaurant meals and specialty cocktails while I’m out.

🍴 Ham sandwich with muenster on rye, strawberries, oatmeal and raisin cookie with Coca-cola zero sugar

Since the ham sandwich post is so vaunted and maligned in the social media space and I can more properly support it, I’ve already made my obligatory first personal ham sandwich post.

Previous Food related posts on Silos

Back in the day, I’d used services like Eat.ly and Foodspotting. The former was bought out by the latter and development and customer acquisition seems to have died altogether. These did a reasonable job of melding eating and checkin post types, but the genre seems to have died out for lack of interest and or development. Since some of what they did was interesting and useful to me, I’m recreating portions of it on my own site.

Courtesy of David’s Simple Location Plugin, I’ll also be able to add location data to my eating-related posts to also make them checkins in a sense much like some of the functionality of these older silos.

I did like some of the health related and calorie data that Eat.ly made possible, and might consider adding some of that into my site in the future as well. I’ll have to take a look at services like WeightWatchers that I would expect might add that type of functionality as well. This also reminds me that Leo Laporte has a wi-fi scale that Tweets out his weight every time he stands on it. That sounds like useful quantified self data, though I don’t think I’d go so far as to post it publicly on my site (or syndicate it) in the future.

Feeds for these posts

I can’t imagine that anyone but potential stalkers would care, but for posterity, here are the feeds associated with these posts:
Eat: http://www.boffosocko.com/kind/eat/feed/
Drink: http://www.boffosocko.com/kind/eat/feed/
Eat & Drink (combined): http://www.boffosocko.com/feed/?kind=eat,drink

If you’re subscribed to my full feed and don’t want these in it, it’s possible to redact these posts from your stream, just drop me a line and I can help you subscribe to just the content you desire. Those subscribed to the “Food” category needn’t worry as I don’t expect to be clogging that category up with these posts.

Books on Micro.blog by Manton Reece

Replied to Books on Micro.blog by Manton Reece (manton.org)
Today we’re introducing a search collection using emoji, starting with books. Just include the books emoji with your microblog text about a book you’re reading or related topic, and your post will automatically be collected on /discover/books.
@Manton has added an interesting new feature to micro.blog. He’s created a special book discovery page which users can use to see what others are reading or recommending.

Simply by including the books emoji 📚 in one’s post, the page will collect all those posts and display them at http://micro.blog/discover/books. In a sense, he’s using an emoji almost like a hashtag, though the mechanics of how things work are slightly different. I’m curious to see how it evolves.

Based on what I’m able to discern, I have the proud place of ownership for being the fourth book post to micro.blog with “The Library is finally unpacked” from several months ago. It isn’t a book recommendation, but it’ll give you and idea about what I think about books.

The sad part for me though is that he chose the books emoji 📚 . Why sad? Because for quite a while now I’ve been posting updates on my own site about what I read using various book-related emoji to indicate where I’m at with a book. I’ll use the bookmark emoji 🔖 to indicate things that I want to read. I use a green book emoji 📗 to indicate that I’ve started reading something, an open book emoji 📖 to indicate that I’m making progress, and a red book emoji 📕 to indicate that I’ve just finished or stopped reading a particular book. Most of my book status updates also have some notes or thoughts about what I’m reading as well as quotes, highlights, and other marginalia.

Since micro.blog’s discover page only uses one emoji, it’s missing out on all my past updates. For those who’d like to see them on my site, this link should have the entire archive. Not all of them are syndicated to Twitter, but this link will give folks an idea what these posts all look like there.

In a similar vein, I also often post what I’m reading online with glasses 👓 emoji. One of the things that’s always bothered me about Twitter was that people often share articles, but research has shown that very few actually bother to read them before sharing. (I’ve always gotten the impression that many don’t even bother to read the headlines.) Thus, following reading.am’s lead, I post everything I actually read online to my own website, but to indicate that it was read (from start to finish), I add the glasses emoji to the title. If I haven’t read it yet, it’s more likely hidden on my back end or, if it’s something I really want to advertise, promote, or highly expect I’ll come back to later, it will have a bookmark emoji 🔖.

I don’t publish all my reads publicly, a large number are published privately. You can find all of the public read posts here.

Lastly, for movies and television I’m watching, I include either TV emoji 📺 or film emoji 🎞️. I find that these emoji do really well for microblogging spaces which often have space restrictions.

Overall, I’ve quite enjoyed the evolution of micro.blog’s discovery features. While there are a few follow recommendations available, the service has a page with recent photos, so one can scan photos as a means of finding interesting people to follow on the service.

I can’t wait to see how the reading discovery page works out or what other new discovery tools Manton implements in the future. It’s nice to see a service that continues to evolve and change in reaction to its community.

Thanks Manton!

Adding Simple Twitter Response Buttons to WordPress Posts

Back at IndieWebCamp Austin, I became enamored of adding additional methods of interacting with my website, particularly for those who weren’t already on the IndieWeb train. I’d seen these types of interactions already on Tantek Çelik’s site in the past, so naturally I figured I would start there.

Web Actions

Some basic searching revealed that in IndieWeb parlance, these types of functionalities are known as web actions. While they’re often added to make it easier for one site with the proper infrastructure to interact with another, they’re also designed for social web silos (Like Twitter, Facebook, et al.) to do this type of interaction simply as well.

As a small scale experiment, I thought I would begin manually and add some simple interface to allow Twitter users (who may not yet have their own websites to use to respond to me instead) to be able to quickly and easily reply to, repost, or like posts on my site. A little bit of reading on the wiki and Twitter’s developer site allowed me to leverage something into existence pretty quickly.

Interestingly, although there are many plugins that help users simply share a blog post to Twitter, I couldn’t easily find a WordPress plugin that already allows these other interactions as options at all. I suspect it may be because the other side of the interaction of bringing the replies back to one’s site isn’t commonly known yet.

Example

I was able to write a post, syndicate it to Twitter, upload the button images, and then inject the Twitter post ID (939650287622434816 in this example) for my syndicated copy into my post like so:

<span class="syn-text">Respond via Twitter:
<ul class="relsyn">
<li><a href="https://twitter.com/intent/tweet?in_reply_to=939650287622434816" target=""><img src="/reply-icon-16.png" alt="" width="16" height="11" /> Reply</a></li>
<li><a href="https://twitter.com/intent/retweet?tweet_id=939650287622434816" target=""><img src="/retweet-icon-16.png" alt="" width="16" height="10" /> Repost</a></li>
<li><a href="https://twitter.com/intent/favorite?tweet_id=939650287622434816" target=""><img src="/like-icon-16.png" alt="" width="16" height="16" /> Like</a></li>
</ul><script type="text/javascript" async src="https://platform.twitter.com/widgets.js"></script></span>

And voila! My new post now had some simple buttons that allow users a simple one click interaction with a popup window to reply to, repost, or like my post.

Displaying responses

Naturally, through the “magic” of Brid.gy, I’m able to collect these responses via backfeed with the Webmention protocol using the Webmention Plugin for WordPress back to my own website. In simpler and less technical terms, if you use one of these buttons, your interaction with my website as posted to Twitter comes back to live on my website. Thus users can use Twitter to write a comment or reply on Twitter and it will display in my comments section just as if they had written it directly in my comments box. Likes and reposts are sent to my site and are displayed relatively naturally as facepiles under the comment headings “Likes” and “Reposts”.

I’ll do another manual example with this particular post, so feel free to use the buttons at the bottom of this post to make your response via Twitter if you wish.

Future Improvements

Taking some of this code and abstracting into a plugin for others to use would be a nice feature. Doing this would also potentially make it available as a potential plugin in the larger IndieWeb suite of WordPress plugins. Perhaps it could be easily added into the codebase in one or another pre-existing plugins? I might think that David Shanske’s  Syndication Links plugin or Bridgy Publish plugin might make sense as they’re already adding functionality for part of the publishing half of the cycle by either publishing to Twitter and/or importing the Tweet ID back into one’s WordPress site for potential display. One or the other could do a simple if/then on the existence of a syndicated Tweet, then extract the Twitter ID, and add the buttons to the interface appropriately.

It would be interesting to add full mark up to make <indie-action> functionality possible for a broader class of web actions, particularly if it could be integrated directly into WordPress in a more interesting manner to work with the Post Kinds Plugin or the IndieWeb PressThis type of bookmarklet functionality.

Instead of having these types of interactions injected at the bottom of the post, it may make more sense to have it display in the comment block instead.

I suspect that Facebook, Instagram, and others also enable some types of functionality, so adding the ability to use them the same way would be awesome. And even more so in the case of RSVP’s to events since Brid.gy handles those relatively well between Facebook and WordPress sites. (See this example.)

Try it yourself

Go ahead and use the buttons below to interact with this post via Twitter.

👓 An Open Letter on Why We’re Removing Usernames, Addressed to the Worst Ones We’ve Ever Seen | OKCupid

Read An Open Letter on Why We’re Removing Usernames, Addressed to the Worst Ones We’ve Ever Seen by OkCupid (Medium)
Or best, depending on how you look at it—sorry, DoritoprincessXO What’s in a name? You see, DaddyzPrincess29*, we all have names. Good, noble names that took weeks, perhaps months to choose— from Hannah to Jordan to Lady Bird. And what we’ve discovered is that those names actually work best—better than usernames—when it comes connecting with people. So listen closely laidback___stu, because this applies to you — even if you are straight chilling right now on a basement futon. Ahead of the new year, we’re removing OkCupid usernames. It’s starting with a test group and will soon be rolled out to everyone on OkCupid, so all users will need to update their profiles with what they want their dates to call them. We know, this is tough to hear — especially for StayingPawwsitive, Dootdootledootd0 and Britney__Tears. It’s because, like the recent goodbye we said to AIM screen names, it’s time to keep up with the times. We want you, BigDaddyFlash916, to go by who you are, and not be hidden beneath another layer of mystique. Even if that mystique is crucial to you and your dating life, unicorn__jizz.
A somewhat funny, but very germane take on online identities and usernames.

Threaded Replies and Comments with Webmentions in WordPress

Introduction to what one would consider basic web communication

A few days ago I had written a post on my website and a colleague had written a reply on his own website. Because we were both using the W3C Webmention specification on our websites, my site received the notification of his response and displayed it in the comments section of my website. (This in and of itself is really magic enough–cross website @mentions!)

To reply back to him I previously would have written a separate second post on my site in turn to reply to his, thereby fragmenting the conversation across multiple posts and making it harder to follow the conversation. (This is somewhat similar to what Medium.com does with their commenting system as each reply/comment is its own standalone page.)

Instead, I’ve now been able to configure my website to allow me to write a reply directly to a response within my comments section admin UI (or even in the comments section of the original page itself), publish it, and have the comment be sent to his reply and display it there. Two copies for the price of one!

From the comments list in my Admin UI, I can write a reply and it not only lives on my site but it can now be sent as a comment to the site that made the original comment! As an example, here’s my first one and the resultant copy on the site I was replying to.

This means that now, WordPress-based websites (at least self-hosted versions running the WordPress.org code) can easily and simply allow multiple parties to write posts on their own sites and participate in multi-sided conversations back and forth while all parties maintain copies of all sides of the conversation on their own websites in a way that maintains all of the context. As a result, if one site should be shut down or disappear, the remaining websites will still have a fully archived copy of the entire conversation thread. (Let’s hear it for the resilience of the web!)

What is happening?

This functionality is seemingly so simple that one is left wondering:

  • “Why wasn’t this baked into WordPress (and the rest of the web) from the start?”
  • “Why wasn’t this built after the rise of Twitter, Facebook, or other websites which do this as a basic function?”
  • “How can I get it tout suite?!” (aka gimme, gimme, gimme, and right now!!!)

While seeming simple, the technical hurdles aren’t necessarily because there had previously never been a universal protocol for the web to allow it. (The Webmentions spec now makes it possible.) Sites like Facebook, Twitter, and others enable it because they’ve got a highly closed and highly customized environment that makes it a simpler problem to solve. In fact, even old-school web-based bulletin boards allowed this!

But even within social media one will immediately notice that you can’t use your Facebook account to reply to a Twitter account. And why not?! (While the web would be far better if one website or page could talk to another, these sites don’t for the simple economic reason that they want you using only their site and not others, and not enabling this functionality keeps you locked into what they’re selling.)

I’ll detail the basic set up below, but thought that it would be highly illustrative to have a diagram of what’s physically happening in case the description above seems a bit confusing to picture properly. I’ll depict two websites, each in their own column and color-coded so that content from site A is one color while content from site B is another color.

A diagram of where comments live when sent via webmention.
Each site composes and owns its own content and sends the replies to the other site.

It really seems nearly incomprehensible to me how this hasn’t been built into the core functionality of the web from the beginning of at least the blogosphere. Yet here we are, and somehow I’m demonstrating how to do this from one WordPress site to another via the open web in 2017. To me this is the entire difference between a true Internet and just using someone else’s intranet.

Implementation

Prerequisites

While this general functionality is doable on any website, I’ll stick to enabling it specifically on WordPress, a content management system that is powering roughly 30% of all websites on the internet. You’ll naturally need your own self-hosted WordPress-based website with a few custom plugins and a modern semantic-based theme. (Those interested in setting it up on other platforms are more than welcome to explore the resources of the IndieWeb wiki and their chat which has a wealth of resources.)

Plugins

As a minimum set you’ll want to have the following list of plugins enabled and configured:

Other instructions and help for setting these up and configuring them can be found on the IndieWeb wiki, though not all of the steps there are necessarily required for this functionality.

Themes

Ideally this all should function regardless of the theme you have chosen, but WordPress only provides the most basic support for microformats version 1 and doesn’t support the more modern version 2 out of the box. As a result, the display of comments from site to site may be a bit wonky depending on how supportive your particular theme is of the microformats standards. As you can see I’m using a relatively standard version of the TwentySixteen theme without a lot of customization and getting some reasonable results. If you have a choice, I’d recommend one of the following specific themes which have solid semantic markup:

Plugin

The final plugin that enables sending comments from one comment section to another is the WordPress Webmention for Comments plugin. As it is still somewhat experimental and is not available in the WordPress repository, you’ll need to download it from GitHub and activate it. That’s it! There aren’t any settings or anything else to configure.

Use

With the plugin installed, you should now be able to send comments and replies to replies directly within your comments admin UI (or directly within your comments section in individual pages, though this can not require additional clicks to get there, but you also don’t have the benefit of the admin editor either).

There is one current caveat however. For the plugin to actually send the webmention properly, it will need to have a URL in your reply that includes the microformats u-in-reply-to class. Currently you’ll need to do this manually until the plugin can properly parse and target the fragmentions for the comments properly. I hope the functionality can be added to the plugin to make the experience seamless in the future.

So what does this u-in-reply-to part actually look like? Here’s an example of the one I used to send my reply:

<a class="u-in-reply-to" href="https://islandinthenet.com/manually-adding-microfomats-markup/">Khürt</a>

The class tells the receiving site that the webmention is a reply and to display it as such and the URL is necessary for your webmention plugin to know where to send the notification. You’d simply need to change the URL and the word (or words) that appear between the anchor tags.

If you want to have a hidden link and still send a webmention you could potentially add your link to a zero width space as well. This would look like the following:

<a class="u-in-reply-to" href="http://www.example.com">&​#8203;​</a>

Based on my experiments, using a <link> via HTML will work, but it will send it as a plain webmention to the site and it won’t show up natively as a reply.

Sadly, a plain text reply doesn’t work (yet), but hopefully some simple changes could be made to force it to using the common fragmentions pattern that WordPress uses for replies.

Interestingly this capability has been around for a while, it just hasn’t been well documented or described. I hope now that those with WordPress sites that already support Webmentions will have a better idea what this plugin is doing and how works.

Future

Eventually one might expect that all the bugs in the system get worked out and the sub-plugin for sending comment Webmentions will be rolled up into the main Webmentions plugin, which incidentally handles fragmentions already.

Caveats

In addition to the notes above, I will say that this is still technically experimental code not running on many websites, so its functionality may not be exact or perfect in actual use, though in experimenting with it I have found it to be very stable. I would recommend checking that the replies actually post to the receiving site, which incidentally must be able to accept webmentions. If the receiving website doesn’t have webmention support, one will need to manually cut and paste the content there (and likely check the receive notification of replies via email, so you can stay apprised of future replies).

You can check the receiving site’s webmention support in most browsers by right clicking and viewing the pages source. Within the source one should see code in the <head> section of the page which indicates there is a webmention endpoint. Here is an example of the code typically injected into WordPress websites that you’d be looking for:

<link rel="webmention" href="http://example.com/wp-json/webmention/1.0/endpoint" />
<link rel="http://webmention.org/" href="http://example.com/wp-json/webmention/1.0/endpoint" />

Also keep in mind that some users moderate their comments, so that even though your mention was sent, they may need to approve it prior to it displaying on the page.

If you do notice problems or issues or have quirks, please file the issue with as full a description of what you did and what resulted as you can so that it can be troubleshot and made to work not only for you, but hopefully work better for everyone else.

Give it a try

So you’ve implemented everything above? Go ahead and write a reply on your own WordPress website and send me a webmention! I’ll do my best to reply directly to you so you can send another reply to make sure you’ve got things working properly.

Once you’re set, go forward and continue helping to make the web a better place.

Special Thanks

I wanted to take a moment to give special thanks to Aaron Parecki, Matthias Pfefferle, and David Shanske who have done most of the Herculean work to get this and related functionality working. And thanks also to all who make up the IndieWeb community that are pushing the boundaries of what the web is and what it can accomplish. And finally, thanks to Khürt Williams who became the unwitting guinea pig for my first attempt at this. Thank you all!

​​​​​​