@huby plain old semantic HTML with microformats in combination with the webmention protocol allow one to post "likes" to one's own website and send them to others. Here's a simple example: http:/
@scott_gruber, sorry I didn't see this until this morning. Last night I had some issues connecting to the wifi for the first chunk of the meeting, so I didn't get the chance to document things into the chat as we went along.
It sounds to me like you got a lot of great things arranged and working on your site though! Congratulations on the Webmentions progress. That's awesome!!
RSVP invited · Issue #156 · pfefferle/wordpress-semantic-linkbacks https:/
When Brid.gy sends webmentions for people invited via a Facebook POSSE copy, the webmentions for these people don't show up properly in comments because `semantic_linkbacks_type` is set to "invite" instead of "rsvp:invited".
Manually effecting the change in the database provides the expected display. See: http:/
@mlncn @hongpong I suspected Dries would find you both via the wiki having blazed some of the trail beforehand, so I didn't want to extend the post to point out what I suspected he would find quickly enough.
Simultaneously, my intention was to do a "BCC Webmention" of sorts so that the two of you were at least aware of his original post if you hadn't seen it. Sorry if it read as spam to some extent, but I didn't really have specific posts on all of your sites that would have made a huge amount sense to highlight to get them in via a traditional mention or a reply. Thus I did a few homepage webmentions to get them in under the wire, so to speak.
I don't think it's a common pattern to ping someone's site this way, but given the precedent and prior art within email, it seemed like a somewhat useful way to send the notification without making it so explicit. I'm glad you received it and understood at least some of the intention.
I didn't see a webmention endpoint on Dan's homepage, so I'm glad to have the chance to explicitly @mention him on Twitter with this post.
#bcc + #webmention = #bccwebmention
#breakingtheweb
#drupal
Within the past month [it's guestimated that over 1 million webmentions](https:/
Mastodon already supports most microformats for webmention to be implemented more easily. https:/
There are already a number of open source tools that might also be bootstrapped for something like this as well: https:/
@MorrisPelzel @hypothes_is In some sense, but this is much more decentralized, lightweight, and I own and control it rather than farming it out to a 3rd party. Hypothesis also doesn't (yet?) send webmentions or notifications to my site when it's been marked up either.
@mrkrndvs I like emoji particularly for posting to micro sites like Twitter and micro.blog where one is more constrained. I don't like it as much for some of the gymnastics I need to pull off, and most of which you mention. Not all sites seem to be able to handle them properly, and I often wonder at my decision to have used them in the first place. I've also noticed some issues with emojis in permalinks causing Brid.gy not to be able to send backfeed webmentions.
One thing that may make it easier to deploy them across your site is to bake them into the templates for your site (either into the post templates or into the post kind templates directly). This will allow you to use them quickly and easily and deploy them to thousands of posts at once with the ability to remove them later if you like. It'll also save you a huge amount of time hard coding them into your posts.
@mrkrndvs I'm curious if you manually cut & paste your replies for others' sites (who may not support webmention or even pingback/trackback) into their old-school comments sections?
I often worry that without that, or without replying to versions on Twitter if they syndicated, they won't see my response via pingback/trackback or other means. Instead my reply sits all alone on my site and they don't have the benefit of seeing it at all unless they come across it organically otherwise.
Generally when I manually cut and paste replies, I'll often use the comment's "website" field to include the permalink for my comment and then I'll take the permalink for my comment and add it to my syndication links since I've manually syndicated it.
Sometimes I notice that including multiple links in a reply can also run afoul of spam filters.
One of my favorite set of machinations occurred recently when I wrote this reply to Jon Udell: http:/
Jon came back to his original post and appended his own comment to document my comment in the most circuitous of manners which included using his annotation tool Hypothes.is: https:/
Interestingly we both used WordPress, Hypothes.is, and Twitter to carry on the conversation. I was quite impressed that he took the time to circle back around and document my end of the conversation since he must have missed my pingback (he doesn't have webmentions) and my manual cut & paste, but did manage to see the notification on Twitter.
It all just goes to show that you've got to keep your eye on the tech that you and everyone else is using until it's broadly and evenly distributed. One day perhaps...
I suspect that next, with a tad bit of parsing using microformats, you can add some display elements to your webmentions to indicate the author, their url, date/time, and actually include the reply text to have a better UI for them. Then they'll look a bit more like the traditional comments you may have envisioned. (Something along the lines seen in my comments at http:/
If you've got incoming webmentions working, let me have the old school pleasure of saying:
"First!"
Aaron, I finally just made the jump into microcasting myself over the holidays in as low-tech a manner as possible.
http:/
I'll have to write up the details, but they're so scant as to make doing so more like a status update than an article. My advice, think of an idea, pull out your phone and set a 10 minute timer, hit record on the simplest recorder app you've got, and go. Post to your site and you're done. It's very liberating in comparison to all the grander plans I'd had to do something larger. And even better when you know you've only got an audience of one or two, you don't feel like you've spent thousands of hours for such a meager launch!
I do like John's idea about a slow-podcast, though I worry that the effort and time may be both painful and take some of the spontaneity and flow out of a conversation. Perhaps stringing together pieces of various microcasts using webmentions into a longer "playlist" of sorts to create a longer podcast could be an interesting idea?
The more I think about archiving the web this week, the more value and stability I think that the W3C's Webmentions spec could be adding to the internet and copies of it. #DtMH2017
https:/
@frank Webmentions are an extra generation or two beyond the traditional pingbacks/trackbacks. The receiver actually verifies that the sender is displaying the permalink on a physical page before accepting it, thereby cutting down on spam (there have been no reports of webmention spam in the wild yet.) Webmentions and their structure are also set up to allow the receiving site to better handle display which often includes the name, avatar, and either excerpts, or complete comment. I use them in WordPress and there's generally little if any difference in the display of Webmention replies and comments natively put into the system manually. Webmention also allows additonal types of mentions including likes, bookmarks, reads, listens, etc. to distinguish for context.
@alienlebarge @SaraSoueidan People who wanted to ask questions anonymously could ping with webmentions via https:/
@khurtwilliams POSSE for WordPress can be tricky in part because, compared to most other IndieWeb pieces for WordPress, there are multiple different and varying ways to do it. Using one method could potentially conflict with another depending on how you set things up, though I think these are relatively few.
Your best bet is to hop into the #WordPress channel of the IndieWeb chat https:/
In general, the more control and flexibility you want over the display of your POSSE posts, the more set up and work you have to put into it (e.g. SNAP), while the less control you have the more simple the set up (e.g. JetPack Publicize).
Things like Brid.gy publish functionality (or via the Brid.gy Publish plugin) can be more finicky for POSSE copies to silos because Brid.gy is parsing your site for the proper data to publish. (It does have a preview button built in to do manual tests if you need to.) This means that if your WordPress theme doesn't have the correct microformats markup (and often they don't), then you can get spurious results, particularly when it comes to crossposting photos.
Most of the main POSSE plugins and tech are very stable in fact, but they do require that you do a bit of reading and understanding what they do and don't do and what you can and can't control with them. Most all of them have GitHub repositories that you can post issues to and almost all the devs, maintainers, and community are happy to help you out and/or make changes to make the UI and documentation better.
As for backfeed from Brid.gy, it generally requires that the URLs of your post and the syndicated post have matching permalinks to be able to match the two up to send you the webmentions properly. You may have changed your settings, but one piece you appear to be missing is the Syndication Links Plugin which allows you to add u-syndication links to your posts so that Brid.gy knows which ones to send your responses to. Much of this is documented at https:/
I'm sure I've got a few odd posts from ages ago when I tested things out, but when you say "I can also see from some of the failed posts on your website that you may experience the same issues." I'm curious which particular posts you mean? To my knowledge things I intend to syndicate out are currently working as I expect them to (aside from one quirk that occasionally spams the Indieweb chat with micropubbed posts which continually redirect, but that's specific only to me because of some experimental code I've been running). It is the case that I don't always syndicate everything to each and every silo target I could. I do very much pick and choose which things to syndicate to particular networks.
We'll help you get there yet!