WeChat ID
aaronpk_tv
-
Portland, Oregon • Wed, April 25, 2018 11:17amSome crazy new colors going on here!
-
Just downloaded my @instagram dump and I'm pretty disappointed. 😔
• My comments include only the comment text, a timestamp, and the photo author. No way to know what I'm commenting on
• Same for photos I've liked
• There's no indication of likes or comments on my own photos -
In practice this is enforced by the PHP process itself. PHP has a setting for a maximum memory limit, at which point the process will be killed. I'm not really interested in trying to solve this for real using some sort of stream solution, since the vast majority of content this is used for is relatively small pages.
-
omg is that a cat cafe? 😻 -
151.5lbsWeight18.0%Body Fat -
AsleepAwake7h 00mSlept12mAwake for
-
Hello from @donutjs, packed house tonight! We're livestreaming tonight thanks to support from @oktadev! https://youtu.be/4czBvCbtiWw
-
Portland, Oregon • Tue, April 24, 2018 5:32pm#DonutJS setup
-
We are very happy to let you know that @oktadev is sponsoring our video recording and production!
Okta provides authentication, authorization, and user management to your web or mobile app. Learn more at http://developer.okta.com!
🔑🍩‿🍩🔒 -
Hello everybody, Donut.js is tonight! Tickets are still available! Join us at 6pm at @AlchemyCodeLab for superb talks from @ryrykubes and @sandyaaaas and @elnoelle. Come support http://portlandmeetportland.org! Come and eat donuts and chat and party! https://donutjs.club
-
nickvance
https://micro.blog/nickvance
•
Apr 24
@aaronpk I'm a big fan of plan 'ol RSS but this is neat. Seems weird that it shows up under a GoDaddy URL though?
Plain old RSS is fine for what it does -- one-way consumption of blog posts and podcasts -- but the web moved on from that kind of interaction ages ago. GoDaddy has been a big indieweb supporter for a while now too! https://indieweb.org/GoDaddy -
wow pretty cool! It looks like 1000ft is normal though: https://aviation.stackexchange.com/a/2813
-
Please Stop Using Local Storage (dev.to)
-
Adam Lewis
https://twitter.com/lewiada
•
Apr 24
and what about for storing the access token in the browser?
Sadly there isn't a satisfying answer to that. Anything that your JS can use to store any token is vulnerable to XSS. The only secure option is cookies, but that won't work with OAuth. https://stormpath.com/blog/where-to-store-your-jwts-cookies-vs-html5-web-storage -
@buffer Does this Facebook API announcement mean publishing to Facebook from Buffer will stop working? https://developers.facebook.com/blog/post/2018/04/24/new-facebook-platform-product-changes-policy-updates/
-
Aaron Parecki
https://aaronparecki.com/
•
Apr 24
BCP for public UA clients:
• use the authorization code flow
• omit client secret
• strict redirect URI validation
Some citations and more info: https://aaronparecki.com/oauth-2-simplified/#single-page-apps
I agree it would be nice to see this written up properly though. In the mean time, I'm adding a section to my book about this. -
Adam Lewis
https://twitter.com/lewiada
•
Apr 24
We do implement native apps per RFC8252 including code flow, custom tabs and PKCE, and we use OIDC for authentication to web apps. But doing ua-based-apps / SPAs right is ambiguous at best and I keep hoping for the @oauth_2 WG to begin work on an ua-based client BCP.
BCP for public UA clients:
• use the authorization code flow
• omit client secret
• strict redirect URI validation
Some citations and more info: https://aaronparecki.com/oauth-2-simplified/#single-page-apps -
We do implement native apps per RFC8252 including code flow, custom tabs and PKCE, and we use OIDC for authentication to web apps. But doing ua-based-apps / SPAs right is ambiguous at best and I keep hoping for the @oauth_2 WG to begin work on an ua-based client BCP.
-
