Aaron Parecki

twitter.com/jack/status/20

It's a little known fact that QR codes are actually quite tolerant of errors and missing pixels, so much so that you can completely cover up a bunch of them with junk and the code still scans fine. This is the principle behind the site I made, vanity-qrcode.com, which allows people to create QR codes with text overlaid on them.

I have lived in IRC for about 7 years. What I mean by this is that IRC has been my primary hub for reading information online and interacting with people and systems. I don't use an RSS reader, I visit Twitter and Facebook only occasionally, and I try to limit my email usage to only business. Instead, I have created filters from various sources that send notifications to various IRC channels about things I am interested in.

aaronparecki.com/replies/2012/11/19/1/devsummit

Earlier this week, Eye-fi announced they are discontinuing the online services for the "Pro" cards in favor of the new cloud-connected "Mobi" ones. Since my primary use of the Eye-fi card is to upload my photos to Flickr, I have no interest in paying for their cloud service. Time to look for another card! Most of the other wifi SD cards on the market come with an iOS/Android app, and basically all they let you do is view the photos from the app if your phone is connected to the card's wifi. Then I discovered the Toshiba FlashAir card, which has a developer site and encourages people to build things on top of the card.

Since this took me a while to figure out, I figured I'd document it here in case it's useful to others later.

I'm writing this post in the newest version of my Quill editor, which I hacked together at IndieWebCamp Germany. I was inspired by Glenn Jones' nice editing UI for Transmat (now separated out as a separate component and published here), and wanted to create something myself that was more than just a Bootstrap form. 

In August 2012, I wrote a quick script to stream front-page Hackernews stories to an IRC channel on Freenode. It broke after 2.5 years, at which point I switched to their new JSON API. That one broke after 2 days. Here is how we can fix this.

Since all of my recent spam has been sent to non-expired endpoints, and since I don't get a high number of webmentions right now, I decided to remove the expiring endpoints from my site for the time being.

aaronparecki.com/notes/2015/03/03/4/

In the current world of silos dominating the social media space, people typically have to visit half a dozen websites or apps to see all the latest content from friends. At this point I'm sick of this "multiple inbox" model that I want to find an alternative as fast as possible.

This is a reply to fkooman's proposed changes to IndieAuth protocol.

Let's say you have a cluster of Postgres database servers and you want a way to easily monitor their CPU and memory usage. You could install any of the system monitoring daemons like Nagios, Collectd, Munin, etc, but that means opening up another port in your firewall, and maintaning another running process. If all you're after is basic info like CPU and memory usage, there's an easier way!

twitter.com/davewiner/status/565208821250162688

People often wonder why I am hesitant to bake JSON into specs I write such as IndieAuth and Micropub. Here is the short answer.

While OAuth 2.0 is a good framework for building an API, the spec itself leaves many things un-specified, and it's up to the implementer to make a decision based on their own security requirements. As such, most OAuth 2.0 implementations are not interoperable, which is often cited as a failure of OAuth 2.0. On the other hand, the current state of OAuth 2.0 implementations is that they are often similar enough that developers don't need to learn too many new concepts when dealing with them.

Today, ind.ie announced in a blog post (ind.ie/blog/focus/) that they will no longer be making a phone, and are dropping support for their Android and iOS social network clients, focusing instead only on the OS X version.

The core principle of the IndieWeb is to own your data by creating content on your own domain with permalinks you control, rather than creating content in silos.

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.