71°F

Aaron Parecki

  • Articles
  • Notes
  • Photos
  • Andy Baio https://twitter.com/waxpancake   •   Jun 8
    EXCELLENT
    Aaron Parecki
    @waxpancake Totally not planned I swear 😂 @evanpro
    Portland, Oregon, USA
    1 reply
    Tue, Jun 7, 2016 5:46pm -07:00
  • Andy Baio https://twitter.com/waxpancake   •   Jun 8
    Nice t-shirt in the front row!
    Aaron Parecki
    @waxpancake @metaltoad It's hard to see but I'm wearing the grey on black version 😄
    Portland, Oregon, USA
    2 replies
    Tue, Jun 7, 2016 5:35pm -07:00
  • Kevin Yank https://twitter.com/sentience   •   Jun 5
    Don’t mean to nitpick, but @indiewebcamp’s nice new logo is fuzzy on my @2x Retina display.
    Aaron Parecki
    @sentience Replaced it with an SVG! Thanks! /cc @t @KevinMarks @indiewebcamp
    Portland, Oregon, USA
    1 like 1 reply
    Sun, Jun 5, 2016 5:09pm -07:00 #indiewebcamp
  • http://werd.io/2016/really-happy-to-be-here-at-indiewebsummit
    Aaron Parecki
    @benwerd I'm really happy you're here too!
    Portland, Oregon, USA
    1 reply
    Sat, Jun 4, 2016 10:33am -07:00
  • Jim Pick https://twitter.com/jimpick   •   Jun 2
    My wife couldn't get the time off from her nursing job at the hospital, so if you sell out, I'm not using that ticket. I'm coming.
    Aaron Parecki
    Thanks for letting me know! See you soon!
    Portland, Oregon
    Thu, Jun 2, 2016 4:00pm -07:00
  • https://kylewm.com/2016/06/there-are-a-handful-of-albums-that-i-listened-to
    Aaron Parecki
    The same thing happened to me when I left Eugene and moved back to Portland
    Portland, Oregon
    Wed, Jun 1, 2016 9:37pm -07:00
  • Donut.js 🍩 https://twitter.com/donutjs   •   Jun 1
    A big thank you to @aaronpk for running video, @obensource for taking care of all the audio stuff!
    Aaron Parecki
    @donutjs_pdx @obensource woo hoo! Maybe next time we can livestream the talks!
    Portland, Oregon, USA
    2 likes 1 reply
    Wed, Jun 1, 2016 7:26am -07:00 #donutjs
  • https://twitter.com/ubiquill/status/713035418707431424
    Aaron Parecki
    @ubiquill We're still using them, and working on some new protocols too! Come to IndieWeb Summit this weekend? http://2016.indieweb.org
    Portland, Oregon, USA
    2 likes
    Tue, May 31, 2016 8:26am -07:00 #indiewebcamp
  • https://kylewm.com/2016/05/bridging-the-indieweb-generation-gap
    Aaron Parecki
    @kylewm There's so much I want to reply to, but I only have time for a short reply right now. Short version:

    Agreed that we need to better define our "inessential weirdnesses". I suspect they are actually things that developed organically and can be replaced by other less weird things that have the same effect and accomplish the same goal

    Homebrew Website Club was originally created to be a less technical-focused place to discuss indieweb things.

    An alternate IRC channel isn't a bad idea. Slack does a great job of encouraging splitting different discussion topics into channels and we could do the same. That said, I think rather than splitting off the newcomers into a separate channel, we should split off the jargon/plumbing/implementation discussion into a separate channel.

    I think we're at an interesting time for the community right now. It's super important to have these discussions, so thanks for the writeup.
    Portland, Oregon, USA
    1 like 1 mention
    Tue, May 31, 2016 7:53am -07:00 #indiewebcamp #weirdness
  • Ben Michel📍Bend, Oregon https://twitter.com/obensource   •   May 30
    going to be there no later than 5:30 to set ups sound, etc. Going to try for 5. :)
    Aaron Parecki
    @obensource Cool, I will shoot for 5pm then! I need either a 1/4" or RCA output of the audio.
    Portland, Oregon, USA
    1 reply
    Mon, May 30, 2016 11:43am -07:00
  • Ben Michel📍Bend, Oregon https://twitter.com/obensource   •   May 24
    rad! So stoked you’re jumping in! 🙌

    I’m doing audio, we’ll be in touch soon. :D
    Aaron Parecki
    @obensource What's the plan for tomorrow? I need some time to set up, what time are you getting there?
    Portland, Oregon, USA
    1 like 3 replies
    Mon, May 30, 2016 11:06am -07:00
  • Calum Ryan https://twitter.com/calum_ryan   •   May 28
    made them myself
    Aaron Parecki
    @calum_ryan Oh that's awesome! They look great!
    Portland, Oregon
    Sat, May 28, 2016 1:04pm -07:00
  • Calum Ryan https://twitter.com/calum_ryan   •   May 28
    it's up and working now, uses forecast.io for weather API as it's served over https
    Aaron Parecki
    @calum_ryan That looks great! Where'd you get the weather icons from?
    Portland, Oregon, USA
    2 replies
    Sat, May 28, 2016 1:00pm -07:00
  • https://github.com/snarfed/granary/issues
    Aaron Parecki
    It would be amazing if Granary supported PuSH. That would allow Granary to be smart about how it polls the underlying data sources (since each may have their own varying rate limits) instead of relying on the Granary consumer to implement smart polling. Ideally a Granary consumer could subscribe to updates at the PuSH hub and be notified when a feed has new content.
    Portland, Oregon, USA
    Sat, May 28, 2016 11:45am -07:00 #granary
  • https://github.com/aaronpk/webmention/issues/46
    Aaron Parecki
    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
    Aaron Parecki
    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
    Aaron Parecki
    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
  • https://twitter.com/rrmutt/status/735584264821964800
    Aaron Parecki
    @rrmutt You can sign up for the weekly newsletter! https://indiewebcamp.com/this-week
    Portland, Oregon, USA
    Wed, May 25, 2016 2:33pm -07:00
  • Ben Michel📍Bend, Oregon https://twitter.com/obensource   •   May 24
    rad! So stoked you’re jumping in! 🙌

    I’m doing audio, we’ll be in touch soon. :D
    Aaron Parecki
    @obensource Speaking of audio, are you free tonight? It'd be great to see you at this! https://www.eventbrite.com/e/xoxo-podcast-studio-visioning-workshop-tickets-25070419299
    Portland, Oregon, USA
    1 like 1 reply
    Tue, May 24, 2016 11:18am -07:00 #xoxo
  • Ben Michel📍Bend, Oregon https://twitter.com/obensource   •   May 24
    rad! So stoked you’re jumping in! 🙌

    I’m doing audio, we’ll be in touch soon. :D
    Aaron Parecki
    @obensource @denormalize Perfect! This will be a good chance to test out my new bike-sized recording rig!
    Portland, Oregon, USA
    1 reply
    Tue, May 24, 2016 11:12am -07:00 #donutjs
older

Hi, I'm Aaron Parecki, Director of Identity Standards at Okta, and co-founder of IndieWebCamp. I maintain oauth.net, write and consult about OAuth, and participate in the OAuth Working Group at the IETF. I also help people learn about video production and livestreaming. (detailed bio)

I've been tracking my location since 2008 and I wrote 100 songs in 100 days. I've spoken at conferences around the world about owning your data, OAuth, quantified self, and explained why R is a vowel. Read more.

  • Director of Identity Standards at Okta
  • IndieWebCamp Founder
  • OAuth WG Editor
  • OpenID Board Member

  • 🎥 YouTube Tutorials and Reviews
  • 🏠 We're building a triplex!
  • ⭐️ Life Stack
  • ⚙️ Home Automation
  • All
  • Articles
  • Bookmarks
  • Notes
  • Photos
  • Replies
  • Reviews
  • Trips
  • Videos
  • Contact
© 1999-2025 by Aaron Parecki. Powered by p3k. This site supports Webmention.
Except where otherwise noted, text content on this site is licensed under a Creative Commons Attribution 3.0 License.
IndieWebCamp Microformats Webmention W3C HTML5 Creative Commons
WeChat ID
aaronpk_tv