Aaron Parecki

Thursday, May 26, 2016

• 
• 

  9:43pm

  Asleep

  6:48am

  Awake

  8h 50m

  Slept

  34m

  Awake for

  

  Portland, Oregon, USA

  Thu, May 26, 2016 6:48am -07:00
• Ride

  2.17mi

  Distance

  11:41

  Duration

  7:37am

  Start

  7:49am

  End

  

  Portland, Oregon

  Thu, May 26, 2016 7:49am -07:00
• 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
• Walk

  0.73mi

  Distance

  13:32

  Duration

  11:36am

  Start

  11:50am

  End

  

  Portland, Oregon

  Thu, May 26, 2016 11:50am -07:00
• Walk

  0.57mi

  Distance

  11:15

  Duration

  12:10pm

  Start

  12:21pm

  End

  

  Portland, Oregon

  Thu, May 26, 2016 12:21pm -07:00
• 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
• Kyle Mahan https://kylewm.com

  It is SUPER confusing that there is a guy at work named Travis who manages some of the build/testing infrastructure

  Portland, Oregon

  Thu, May 26, 2016 2:27pm -07:00 (liked on Thu, May 26, 2016 2:30pm -07:00)
• Untrusting an intermediate CA on OS X (blog.filippo.io)

  

  Thu, May 26, 2016 3:18pm -07:00 #security #bluecoat #osx #ssl
• 

  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

  Portland, Oregon, USA

  1 like 1 repost 2 mentions

  Thu, May 26, 2016 3:19pm -07:00 #security #ssl #https #bluecoat
• Ride

  2.06mi

  Distance

  12:40

  Duration

  4:31pm

  Start

  4:44pm

  End

  

  Portland, Oregon

  Thu, May 26, 2016 4:44pm -07:00
• Kyle Mahan https://kylewm.com

  Instead of asking for clarification or arguing with people who give vague criticism, I’m just going to unfollow/ignore them. #lifehacks

  Portland, Oregon

  Sun, May 22, 2016 2:00pm -07:00 (liked on Thu, May 26, 2016 7:44pm -07:00) #lifehacks