Aaron Parecki

@thursdayb Don't tempt me! I have a list!

@ProfessorDino No blog posts lately, but plenty of wiki activity! http://microformats.org/wiki/Special:RecentChanges Lots of use in #indiewebcamp too!

Thank you for describing the blockchain without using the words "decentralized" or "distributed." This makes me much more likely to be interested in your further thoughts and experiments with it! Looking forward to reading more from you about this in the future!

@aaronraimist oh wow. That's worse than I thought then. That means it isn't just sending them in batches.

@aaronraimist Thanks. Is it the very last one in the list?

@aaronraimist I got that too. Can you check if my name is the last one in the list you got?

@ungoldman @lyzidiamond is this a euphamism

@chrisbergr Thanks! The screenshots are generated by http://wkhtmltopdf.org wrapped into a small service here: https://github.com/aaronpk/Lithograph

@jeena @veganstraightedge When I launch a new teespring campaign I will make a parallel one that ships out of the EU and it should solve that. The shirts will likely be more than $20 USD though since I'll be doing a smaller minimum order size.

Not that it's your fault, but I think you're starting to confuse the two roles of indieauth.com. Role 1) indieauth.com is a service that developers can use to handle all the hard work of doing rel-me-auth with specific providers directly. In this case, the application developer has a trust relationship with indieauth.com and users should not be concerned that they're using indieauth.com, from their POV they are just signing in to the website. This is how the indiewebcamp.com wiki uses indieauth.com Role 2) indieauth.com is a service that users can delegate their domain to. To use indieauth.com this way, the user links to indieauth.com as their `authorization_endpoint` on their domain. In this case, the user has a trust relationship with indieauth.com, and an application discovers the user's auth endpoint by following the rel link on their website. Micropub apps like Quill work this way, where you will only ever see indieauth.com if you have delegated to it yourself. Does this help clear things up? In situation 2, you'll only ever see indieauth.com if you explicitly set it as your authorization endpoint. You could use indiecert.net or use your own auth server instead. In situation 1, where a developer has chosen to use indieauth.com instead of implementing authentication themselves, you're limited to the options that indieauth.com has implemented. However the idea is that indieauth.com implements a good number of options and in a secure way, making it a better option for developers than implementing PGP/SMS/GitHub/etc themselves. With that in mind, could you rephrase your request in that context?