I just read Graham Lee’s blog post A brief history of talking on the interwebs (or: why I’m not on and it got me thinking. Instead of creating another centralized Twitter-like service like, why not do microblogging like the Web does “regular” blogging? You know, servers and protocols, like the old days? That would fix the problem of Twitter Inc’s goals not aligning with its users’ goals and third-party developers’ goals.

Beep, a proposed new microblogging system

Beep isn’t a centralized service. It’s an app, a set of protocols, and an ecosystem of Beep servers.

Here’s how it works:

  • You choose a Beep client app (or several).
  • You set up your own Beep server.
  • You subscribe to other Beep servers.

Beep Server

To set up your Beep server, get a quality Beep app and use its 1-click “Make My Server” feature. The Make My Server feature

  • creates a Beep server in your AWS account (provisions you for AWS if you don’t have this)
  • creates your DNS domain (or uses an existing one if you have it)
  • creates a “beep.<your domain>” record in your DNS
You don’t have to be a technical person to do this, because the Beep app makes it super simple and easy.

Reading Beeps

Use your Beep app to post Beeps, to “follow” whichever Beep servers you’re interested in, and to read their Beep streams.

Use Google to search Beeps. If it takes off, Google will probably get better at presenting Beeps in the search results. Maybe Google would provide the #trending feature too?

Like the Web, but Micro

In other words, Beep is the same as the World Wide Web, plus real-time new-post-notification, plus easy self-hosting (via the magic of a quality app) on a little piece of the cloud that you control.

Ownership and Control

Nothing lasts forever. Service providers come and go. Their goals may be aligned with yours now, but that can change. If you’re putting your content in their system, you don’t really have control over it.

With this system, your own your Beep account and you have full control over your “beeps.” 

Problems With This Approach

A few problems come to mind:

  • It’s not free. This would probably keep a lot of users away. But then, isn’t free and it’s getting traction.
  • If you have a lot of followers, hosting costs could be prohibitive. But maybe there are clever solutions for this problem.

EDIT: 5 seconds after I posted this, I saw a tweet about, “a protocol for open, decentralized social networking”, which sounds a lot like this idea. I hope it takes off!


I wanted an NSBrowser with checkboxes for Arq to replace its ugly file-selection mechanism. Some type of file tree with checkboxes UI (like Dropbox and Crashplan use) seemed like a good fit, and I prefer NSBrowser to a (potentially gigantic) NSOutlineView. But I was stumped as to how to get checkboxes in an NSBrowser.

Searching the net gave me some clues, like I should subclass the cell that the NSBrowser uses and call [NSBrowser setCellClass:], but searching also led me down some fruitless paths. Contrary to what you may have read, don’t subclass NSBrowserCell — it’s unsubclassable.

Finally I stumbled on Apple’s ComplexBrowser sample code. It uses a subclass of NSTextFieldCell. And it gives some clues on how to capture the checkbox click.

The Code

When I began my search, I was hoping to find someone’s sample project that did just what I wanted, but no luck. So I’m publishing my sample project for the next person who goes looking for such a thing:


- Stefan


As part of my process for releasing a new version of Arq, I needed a way for my script to get the version of an app bundle.

So, I wrote a simple utility called appversion which prints the value for the CFBundleVersion key in an app’s Info.plist.

For example:

	appversion /Applications/



Download the 32/64-bit Universal binary (in a zip file) here:


Unlike web apps, desktop apps crash without the app’s developer knowing about it, unless the user sends a crash report to the developer. Whenever an app crashes, OS X puts up a dialog for the user to submit a crash report to Apple. Unfortunately for non-Apple apps that crash report never gets to the developer!

So, Arq needs its own “crash reporter”. After reading Daniel Jalkut’s nice roundup of crash reporters, I chose Breakpad because it seems the most similar to Apple’s built-in crash reporter.

Adding Breakpad to your Mac OS X app is easy since the Breakpad team created a Framework around it.

Building Breakpad

Just download the source, open the XCode project under src/client/mac and compile the target “All”.

If you’re on 10.6 though, you’ll need to set the compiler for all the targets and sub-projects to “GCC 4.0″, or else you’ll get an error “GCC 4.2 is not compatible with the Mac OS X 10.4 SDK”.

The default settings for the project (at least as of svn revision 394) create a “32-bit Universal” build. 64-bit isn’t supported yet. See the Breakpad issues list for more details.

Adding Breakpad to Your App

Once you’ve built Breakpad, drag Breakpad.framework into the Linked Frameworks folder of your XCode project. Be sure to check the “copy items into the destination group’s folder” box in the sheet that appears. Also check the target you want to add Breakpad to.

Next, create a “Copy Files” build phase in your target with a destination of “Frameworks”, and drag Breakpad.framework into that.

Next, add a bunch of variables to your app’s Info.plist, including:


See the comments in Breakpad.h for how to set those variables. One tricky bit: BreakpadRequestComments should be a <string> with a value of "TRUE" in your Info.plist, not a <true>.

As an example, here’s how I set my plist variables for Arq:

    <string>Haystack Software</string>

Finally, create a Breakpad object in your app:

    BreakpadRef bp = BreakpadCreate([[NSBundle mainBundle] infoDictionary]);
    if (bp == NULL) {
        NSLog(@"failed to create Breakpad");

That’s it! Now crash your app to try it out :)

On the server side, you’ll need something to process the report. I’ll post my server-side code soon. Tweet me @reitshamer if you need it right now.

UPDATE: I put the server-side code at

© 2012 Philomathy Suffusion theme by Sayontan Sinha