Aaron Parecki

I was sitting at the back of the API discussion at the Quantified Self Conference this Friday in San Francisco, and realized that there is something wrong with the current way these quantified self devices are built and marketed. I don't want to buy a device and be trapped in the company's ecosystem of apps and be stuck in yet another social network. I want to use these physical devices as inputs to my own data store, and have a completely separate set of companies handle the social and aggregation of data from the data that I own.

Now that I've been creating a list of events on my site using p3k, it would be great if I could get a more calendar-like view of that list.

You can now use <a href="https://indieauth.com">IndieAuth.com</a> as an OpenID delegate! This makes it super easy to move off of myopenid.com since it will be shutting down in a few months.

New problem: My notes do not have a "u-syndication" link to the app.net version like they do for the Twitter versions, because my code has no idea that app.net syndicated my post automatically using PourOver.

IndieAuth is a way to use your own domain name to sign in to websites. To sign in, you enter your domain name, and IndieAuth looks for a supported authentication provider on your site and uses that to sign you in.

As part of expanding the functionality of the software my site runs on, I thought it was about time to start showing inline content when I post links in notes.

After I posted my article, An Open Challenge to App.net, @po shared it on App.net. You can see the full thread here.

I am no longer publishing content to my App.net account until I can syndicate my content to their service without writing a single line of code.

The Indie Web

@tantek has been using his Falcon project to create short-form and long-form content on his site, and syndicate it out to Twitter. Falcon is a personal publishing (tweeting, blogging, realtime syndicating) web application created in the true spirit of the Indie Web.