coneybeare's dashboard

coneybeare marked one of Chris Leydon's replies in TinyGrab as useful. Chris Leydon replied to the question "Go away status-bar icon!". coneybeare and 2 other people think it's one of the best replies.

coneybeare replied on September 02, 2009 20:48 to the question "Go away status-bar icon!" in TinyGrab:

I have never looked at the status bar to tell if it was uploaded. Almost anybody who is savvy enough to take a screenshot also has growl support. This is how I know. If I didnt have growl, it would be obvious that when I pasted, and it wasnt a TinyGrab link, that I would have to wait a tiny bit longer. You could also still have the audible ding on successful upload.

As for the history and other uploading, I have never used them and would rather have them tucked away somewhere. Do you guys do any analytics on how the app is used? I don't think I stray too far from the average user.

Either way, you could do it like your competition (GrabUp) does it and give the user a choice of whether or not they wanted the menu-bar icon. Put the choice in the hand of the user man!

coneybeare replied on September 02, 2009 19:47 to the question "Go away status-bar icon!" in TinyGrab:

I dont think that a common use-case is to quit the app. It is not that it is too simple, it is that many users wish to keep that area clutter free. I am an app-designer myself, and you have to ask yourself, what value does this icon serve? One of the biggest features you tout is that upload is automatic and url is pasted to your clipboard. This means that the most-used feature does not require the menu-icon at all! You can stick the app in the system-preferences easily, and this way, users can still access settings, without having to clutter up the dock and/or the menu-bar with unfruitful icons.

coneybeare asked a question in TinyGrab on September 02, 2009 16:58:

Go away status-bar icon!

Please make the status-bar icon go away. I want this completely in the background only

coneybeare started following the question "Do you have a Snow Leopard compatible version in the work?" in grabUp.

coneybeare marked one of Bill Kayser's replies in New Relic as useful. Bill Kayser replied to the problem "getting a cap error on after after_update".

coneybeare replied on February 01, 2009 08:13 to the problem "getting a cap error on after after_update" in New Relic:

** unable to notify New Relic of the deployment (Unexpected response from server: 403: Forbidden)... skipping

Sorry, looks like I didnt cut/paste the entire message

coneybeare reported a problem in New Relic on February 01, 2009 03:19:

getting a cap error on after after_update

I made sure to turn on the api in the control panel.

triggering after callbacks for `deploy:update'
* executing `newrelic:notice_deployment'
* Getting log of changes for New Relic Deployment details
* executing "xxxxxxxxxxxxxxxxxxxxx"
servers: ["xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"]
[xxxxxxxxxxxxxxxxxxxxxx] executing command
command finished
* Uploading deployment to New Relic

coneybeare replied on January 31, 2009 06:18 to the question "Is it possible to have charts auto-refresh?" in New Relic:

Does this happen even in the lite package?

coneybeare asked a question in New Relic on January 31, 2009 06:08:

Is it possible to have charts auto-refresh?

I would love to just leave the screen up and get refreshed stats at a glance without having to do anything.

coneybeare started following the idea "Real time RSS or XML feed of page requests" in New Relic.

coneybeare started following the question "Twitter on my journal! And it's not me! How do I make it stop!" in Twitter.