WeChat ID
aaronpk_tv
-
Buxton, Oregon • Wed, November 26, 2014 7:03pm -
Banks, Oregon • Wed, November 26, 2014 4:47pmStocking up -
Hillsboro, Oregon • Wed, November 26, 2014 3:30pmIt's gonna be dark...
-
Portland, Oregon • Wed, November 26, 2014 2:07pm
-
Portland, Oregon • Tue, November 25, 2014 4:24pm🚲 tuneup
-
Portland, Oregon • Mon, November 24, 2014 5:51pm -
@heyflock Hey guys, this looks really nice! Glad to see you developed it by scratching your own itch too. We've got a similar home-grown tool we use, but never got around to opening it to the public. http://donereports.com and some more details here: http://aaronparecki.com/presentations/2013/09/25/1/done-reports
-
So *that's* what @indiewebcat does while I'm out of the house.
-
A Little Twitter Developer History
Back in the early days of Twitter, I noticed that several tweets I was seeing showed "via _____" next to the date, which linked to the application that was used to post the tweet. I thought "hey that's a clever way to give credit to applications" and thought it would be a good way to get people to discover the Twitter app I was creating at the time.continue reading... -
Continuing last weekend's documentation of all the un-specified parts of OAuth 2.0, things were going pretty well until I hit the "Security Considerations" section, which basically recommends but doesn't require a whole bunch of things. Basically this means an API can be fully OAuth 2.0 compliant and also completely insecure.
If you want to know more, keep an eye out for this blog post. Or hire me as an independent OAuth consultant and I'd gladly spend a day with you. -
Spiced apple cider with brandy, candlelight, and OAuth specs. #saturdaynight #party
-
Portland, Oregon • Wed, November 19, 2014 5:24pm
-
Portland, Oregon • Wed, November 19, 2014 2:47pm
-
Sitting by the fire #esripdx
-
Portland, Oregon • Mon, November 17, 2014 6:58pm
-
Portland, Oregon • Fri, November 14, 2014 11:28pm
-
Currently documenting all the ways the OAuth 2.0 framework leaves choices up to the implementor. The list is long. #oauth2
-
"We could charge the credit card on file, but we would need the first 12 digits and the CVC code" #facepalm
