Instead of asking for clarification or arguing with people who give vague criticism, I’m just going to unfollow/ignore them. #lifehacks
WeChat ID
aaronpk_tv
-
This is perhaps the first step in the fall of certificate authorities in favor of p2p root CA trust sharing. https://twitter.com/FiloSottile/status/735940720931012608 -
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. -
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. -
On tap: Stop Work Stout! #wework
-
This entire article is, essentially, saying that Twitter-the-concept is a great thing, but Twitter… (medium.com)"Let’s pretend that instead of building a single company, a group of engineers got together and built an ecosystem. Like email, but taking in the lessons we’ve learnt, the new communication modes we’ve stumbled across, in the past decades. Multiple servers and services compete and coordinate in equal measure, advancing the whole and being pushed to their limits. Some servers compete on individual privacy, others compete by exchanging privacy for enriched services. Maybe some services even have Moments, who knows. Space for everyone."
-
@rrmutt You can sign up for the weekly newsletter! https://indiewebcamp.com/this-week
-
Portland, Oregon • Wed, May 25, 2016 12:57pm -
Walk
0.61miDistance10:31DurationStartEnd
