Skip to main content

Communication manifesto

Draft! Not yet implemented.

Please leave comments with your feedback.

Historically my responses to inquiries has ebbed and flowed. Sometimes my inbox would pileup for a month before many people would get responses. This manifesto is my contract to the world to improve my communication response time. Before contacting me I suggest you read this manifesto and a couple of essays about email.

Here is my commitment to response time going forward:

Short form:
- @Twitter*, SMS, @GitHub, IM, etc.
- Response within 24 hours.
- Must be less then 250 characters.
- Preferred method of contact.

Long form:
- Email, @Facebook, snail mail etc.
- Response within 48 hours.
- Generally longer then 250 characters.
- Keep it short and to the point.

Voice:
- Phone calls, voicemail, @skype voice, etc
- Callback within 24 hours.
- You must leave a voicemail.
- I don't like phones so you should consider the above options first.

What if I miss my deadline? If it is important ping me immediately after the time lapses else restart the clock and wait one more cycle before pinging me. Maintain the same method of contact so important information stays organized and does not get misplaced. Feel free to also remind me of this communication commitment to you.

And finally ... my contact information page. :)

*Twitter is my preferred form of communication because of it's brevity and easy access.

Comments

  1. I think the long-form response time should actually be longer. It would encourage people to use the short-form.

    And what category does this comment or google group messages fall under?

    ReplyDelete
  2. @Greg: Good point. I should increase long form some.

    Blog comments are short form and Google Group messages are almost always emails for me so long form.

    ReplyDelete

Post a Comment

Popular posts from this blog

CloudSense: the Future of Advertising

With the whole cloud taking off and more and more services switching to a push it into the cloud, leave it there until you need it, and pull it out model. I can only imagine what will be switching to this model soon. Oh wait. I can imagine.



Advertising!


Reading an article about how Avril Lavigne is supposed to have a $2 million check "appear" in her mailbox because of the absurd number of streams her videos get from YouTube got me thinking about creator compensation. The problem Avril is having is, a) Google wants to keep the money, and b) Google is having trouble figuring out how to monetize video streams. But on a grander scale it is whoever puts the ads on the page that gets the money not the content creator.

Little known @Twitter and @TwitterAPI tips and tricks

Be sure to comeback as new tips and tricks get added. If you know of anything I missed be sure to let me know.

Static URL for profile images based on screen_name:

https://api.twitter.com/1/users/profile_image/abraham

* This performs a http redirect to the actual profile image URL. Currently https redirects to http. You can also add "?size={mini | bigger | normal}" to get specific sizes.

Redirect to profile based on user_id:

https://twitter.com/account/redirect_by_id?id=9436992

In_reply_to_status_id mentions:

https://api.twitter.com/1/statuses/update.json?status=reply+to+@abraham&in_reply_to_status_id=12410413197

* In the web interface new mentions are only replies if they start with @screen_name. By pushing @screen_name further along in the string your followers who do not follow @screen_name will still see the status.

Profile image sizes:

http://a3.twimg.com/profile_images/54160223/chart-black-small.png

* By default you get the original image size you can add _mini, _normal, and …

Installing Storytlr the lifestreaming platform

"Storytlr is an open source lifestreaming and micro blogging platform. You can use it for a single user or it can act as a host for many people all from the same installation."

I've been looking for something like Storytlr for a few months now or at least trying to do it with Drupal. While I love Drupal and FeedAPI I did not want to spend all that time building a lifestream website. So I've been playing around with Storytlr instead and found it very easy. Here is how I got it up and running on a Ubuntu EC2 server. You can also check out the official Storytlr install instructions.

Assumptions:
LAMP stack installed and running.Domain setup for a directory.MySQL database and user ready to go.Lets get started!
Get the code: wget http://storytlr.googlecode.com/files/storytlr-0.9.2.tgz tar -xvzf storytlr-0.9.2.tgzYou can find out the latest stable release on Storytlr's downloads page.

Import the database:
Within protected/install is database.sql. Import this into your empt…