Aaron Parecki

#webmention

Day 10: HTML status pages for webmention.io #100DaysOfIndieWeb

Yesterday I added a Webmention form at the bottom of my posts. If you used this form, it would show you a "check status" link after accepting the Webmention request. My Webmentions are all handled by webmention.io, and its status URLs return a JSON response. This isn't particularly friendly when someone views one of these URLs in a browser, since they just see a raw JSON blob.Today I updated webmention.io to return all responses in HTML if they're made from a browser. It checks to see if there is text/html in the Accept header, and returns HTML if so, otherwise returns JSON as normal. Now when you view one of these status links, you'll see something like this.
continue reading...

3 mentions

Fri, Dec 30, 2016 1:21pm -08:00 #100daysofindieweb #indieweb #webmention
Day 9: Webmention form #100DaysOfIndieWeb

I finally brought back the Webmention form on my website! At the bottom of my posts, you'll see a Webmention form now!
continue reading...

1 like 1 reply 4 mentions

Thu, Dec 29, 2016 9:27am -08:00 #100daysofindieweb #indieweb #webmention
Day 3: Resized avatars for comments and other reactions #100DaysOfIndieWeb

Whenever my website receives a comment, like, repost, or other mention, I display those responses on the post's permalink, along with author information if available. For likes and reposts, I show the profile photo in a list, so there are sometimes lots of photos there.
continue reading...

3 mentions

Fri, Dec 23, 2016 12:41pm -08:00 #100daysofindieweb #100days #indieweb #webmention
@Jeffro@wptoots.social https://twitter.com/jeffr0 • Dec 15
Other than not using XMLRPC to send and receive them, what makes Webmentions better than Ping/Trackbacks? https://indieweb.org/Webmention

@jeffr0 Frankly not using XMLRPC is enough, but Webmention also supports updates and deletes, as well as extensions https://indieweb.org/Webmention-faq#Why_webmention_instead_of_pingback

Portland, Oregon, USA

1 like

Thu, Dec 15, 2016 12:42pm -08:00 #webmention
A Brief Intro to My Website Architecture

This is a description of all the pieces and tools that I use to post to my website and handle comments and responses. Many of the pieces are open source and/or based on open protocols that you can implement yourself.WritingI write posts using an app called Quill. It's an open source application that I wrote. I run a hosted version at quill.p3k.io, and you can run it on your own server if you want as well. Quill provides an interface for posting longer blog posts with embedded images like this, as well as short text notes, and a handful of other kinds of posts like bookmarks.Quill doesn't actually store any posts itself. It is just an interface for writing posts.When I click the "post" button in Quill, it sends a Micropub request to my own website, which then creates the post and displays it on my website. Micropub is an API standard for creating short notes and posts, and it supports photos and videos too!You can start using Quill if your website supports Micropub. There are some Micropub plugins for various CMSs, and it's also not too hard to write an endpoint yourself if you're into that sort of thing.Posting to Twitter/FacebookI never write posts directly on Twitter or Facebook. Instead, I write a post in Quill, and then check the boxes for where I want to syndicate the post.
continue reading...

2 likes 1 mention

Mon, Dec 12, 2016 1:24pm -08:00 #indieweb #webmention #micropub #bridgy #architecture
Tony Garnock-Jones https://twitter.com/leastfixedpoint • Nov 6
OK, that's neat. Thanks. So the "rel" would be in the source doc; what do I read to find out common "rel" usages?

@leastfixedpoint Check out https://indieweb.org/responses for common uses. Lots of Microformats2 use with Webmention, enabling cross-site comments.

Portland, Oregon, USA

1 like

Sun, Nov 6, 2016 8:23am -08:00 #webmention
Tony Garnock-Jones https://twitter.com/leastfixedpoint • Nov 6
So with WebMention there are source=...&target=... params, but no rel=... or property=... param. I wonder what the story there is!

@leastfixedpoint The Webmention is just the notification that one URL links to another. What the link means is described at that URL.

Portland, Oregon, USA

1 repost 4 replies

Sun, Nov 6, 2016 8:10am -08:00 #webmention
Webmentions Are Pingbacks For The Open Web (blog.nexcess.net)

Fri, Nov 4, 2016 10:14am -07:00 #webmention #indieweb
Webmention is a W3C Proposed Recommendation | W3C News (www.w3.org)

Tue, Nov 1, 2016 10:20am -07:00 #webmention #w3c #socialwg
Just finished implementing support for receiving Private Webmentions in https://webmention.io and my website! If you're using webmention.io, you will notice a new "private" property when you list mentions or get callbacks.

When you send a private webmention for a comment on one of my posts, you'll see the comment counter increment but you won't see the comment appear. When I log in, I will see the comment along with a little "lock" icon so that I know it's a private post.

Portland, Oregon, USA

Thu, Oct 20, 2016 12:45pm -07:00 #webmention #indieweb #private #p3k
Jared Hanson https://twitter.com/jaredhanson • Oct 1
There's an existing "oauth2-token" link rel which would be nice to use instead of "token_endpoint" https://tools.ietf.org/html/draft-wmills-oauth-lrdd-07#section-3.2

@jaredhanson oh funny! I got token_endpoint from OpenID Connect: http://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata I will take a look at the OAuth 2 link rels tho.

Portland, Oregon, USA

Sat, Oct 1, 2016 7:14am -07:00 #oauth2 #webmention #oauth
First draft of Private Webmention sending

The thing I was most excited about at IndieWebCamp Brighton was coming up with a Private Webmention extension to Webmention. The version we outlined in Brighton was drastically simplified from previous iterations of potential ways to send private Webmentions.Nearly a week after speccing it out, I now have a first draft implementation of sending. My goal this week was to finish implementing sending private Webmentions, to get some real-world feedback on the spec.
continue reading...

8 likes 3 replies 2 mentions

Fri, Sep 30, 2016 2:31pm -07:00 #webmention #indiewebcamp #indieweb #private #p3k
My #indiewebcamp day 2 project: wrote up a Webmention extension for handling private posts! https://indieweb.org/Private-Webmention

Brighton, East Sussex, GBR

6 likes 1 repost 2 replies 2 mentions

Sun, Sep 25, 2016 4:20pm +01:00 #indiewebcamp #webmention #private
Private Webmention (indieweb.org)

"The Private Webmention protocol is an extension to Webmention that supports sending and verifying Webmentions for posts that require access control."

Sun, Sep 25, 2016 4:17pm +01:00 #webmention
https://kylewm.com/2015/11/thinking-about-friends-only-posts

Funny you mention that private webmention is daunting to implement. For me, the opposite is true. While I haven't actually implemented it yet, I feel like making private webmentions work is just figuring out the mechanics of doing the token exchange at this point. The real struggle is figuring out how I want the UX of private posts to work when you're logged in to my site. Should you see additional posts on my home page because you're signed in? Should there be a separate place you go to see private or semi-private posts? Should I only post private posts in separate "channels"? How should the post visually indicate that it's not public? Do I want people to know that they're viewing this post because they're part of a certain group, or leave that information hidden?

Portland, Oregon

1 like

Wed, Aug 17, 2016 6:18pm -07:00 #private #webmention
find me at @anildash@me.dm or anildash.com https://twitter.com/anildash • Aug 10
A lot of open infrastructure that made social media work has disappeared. Can it be rebuilt? https://medium.com/@anildash/the-lost-infrastructure-of-social-media-d2b95662ccd3

@anildash Working on it:

Responses -> https://www.w3.org/TR/webmention/
API -> https://www.w3.org/TR/micropub/

Portland, Oregon, USA

5 likes 1 reply

Wed, Aug 10, 2016 1:32pm -07:00 #webmention #micropub
Francis Hwang https://twitter.com/fhwang • Aug 1
Has anyone suggested a decentralized protocol that would solve the spam problem we saw with pingbacks? (Is this possible?)

@fhwang Vouch is an extension to Webmention (successor to Pingback) meant to address the spam issue: http://indieweb.org/vouch

Portland, Oregon, USA

Mon, Aug 1, 2016 8:53am -07:00 #vouch #webmention
https://github.com/aaronpk/webmention/issues/46

Just for clarification since some people seem to be unclear, this issue is specifically about whether to allow/recommend HEAD requests when making the HTTP request to verify that a webmention source URL does in fact link to the target URL.

This is *not* about the HTTP request used to discover the webmention endpoint in the first place. There are definitely obvious benefits to doing a HEAD request first when discovering the endpoint, since the webmention endpoint may be advertised in the HTTP header, which means that the sender can avoid making a GET request at all.

When verifying the link back, the receiver is going to have to make a GET request eventually, in order to check the document body for the link. The question is whether we should recommend that a receiver first make a HEAD request to the source URL before making the GET request.

Portland, Oregon, USA

Fri, May 27, 2016 10:08am -07:00 #webmention
https://github.com/aaronpk/webmention/issues/40

It's true that not all webmention targets are HTML documents. Because of this, I think it's reasonable to clarify the text, changing

> The sender MUST fetch the target URL (and follow redirects [FETCH]) and check for an HTTP Link header [RFC5988] with a rel value of `webmention`, or an HTML `<link>` or `<a>` element with a rel value of `webmention`.

to

> The sender MUST fetch the target URL (and follow redirects [FETCH]) and check for an HTTP Link header [RFC5988] with a rel value of `webmention`, and if the content-type of the target URL is HTML, the sender MUST also check for an HTML `<link>` or `<a>` element with a rel value of `webmention`.

Requiring all senders to check for the HTTP `Link` header provides the largest opportunity for interop among implementations, since it's possible to publish a Link header regardless of content type.

If you have specific examples of wanting to advertise a webmention endpoint in a non-HTML document, please document them and suggest a (as you said) "standards-compliant way" of advertising the endpoint in the document.

Portland, Oregon, USA

Thu, May 26, 2016 1:06pm -07:00 #webmention #w3c
https://github.com/aaronpk/webmention/issues/39#issuecomment-221936420

I'm just going to point back to what @sandhawke said:

> Abandoning your early adopters before establishing a new user base means you have nobody.

The time to suggest a 100% breaking change to the spec has long passed. There is already a lot of written and deployed code that sends webmentions using form-encoded syntax. It's not a matter of simply making a "tiny" change to switch to JSON, since it will affect senders as well as receivers, some of which are using libraries on both sides, not to mention the fact that this software is deployed quite widely and in places where a single person can't even mandate that it be updated. Such is the situation when a spec gets widely implemented.

Portland, Oregon, USA

Thu, May 26, 2016 10:25am -07:00 #webmention