While we have a lot of development going on here behind the scenes with regard to our time tracking system Tempo, we’re always looking for more feedback from our customers. Ever since we launched the system we’ve gotten some incredibly thoughtful criticism and suggestions that have driven where we’ve taken the app and will continue to do so.

Last night I pushed out some minor adjustments to the interface and we’re planning to do a slew of such adjustments in the upcoming month. With that in mind, we’d like to hear from you about any tweaks you’d like to see. We all tend to notice things that bother us when we are using the site the most, which is generally right around now, at the end of the month. In particular, I’m interested in hammering down any nails that might be sticking up from the floorboards. If you have the time, please hit us up with any changes you’d like to see, major or minor, by writing us at support@zetetic.net.

Thanks again for your support!

We made a couple of small but necessary adjustments to Tempo’s user interface this evening. The date range selector at the top of the screen had been causing some confusion and from there some unexpected exceptional situations [also known as “bugs”]. As you can see here, there’s a date range selector, and a pair for date fields that allow you to select your own date range manually:

Previously, if you typed dates into those boxes or used the calendar pop-up to change their values, the date range would become immediately unselected. This is because the date range took precedence over what was present in the start_date and end_date fields. If you selected a new date range, the start_date and end_date fields would not change until you clicked “Run Report”, and then you’d see that the range took precedence in the report, and their values would be updated to match the range.

That’s a little bit confusing! Some users thought this was a bug and so would clear out the start_date and end_date fields, and then set a range, hit “Run Report”, and nothing would happen because the server wouldn’t process the report without the missing values – even though they would be ignored. Bug on my part.

So, not only has that been fixed, but the start and end date fields are now updated instantly to the correct dates when you select one of the ranges, so that you get the appropriate visual feedback and can see what it is you’re asking for when you run the report. Apologies for the confusion!

As always, if you see anything weird, please send us a message at support@zetetic.net.

Sometimes you come across a webpage that is just so bizarre and absurb, you just don’t know how to introduce it to other people. But you still do it anyway. (h/t to Chip Z)

It only gets better from there (safe for work).

In other news we’re still hammering away at STRIP for the iPhone. We take breaks for food and small diversions, but we’re still plugging away.

Update: it would appear that not long after we posted this, the website in question took the page down.

Warren Ellis writes:

So, are people rolling their own private microblogging networks yet? And knocking together mobile pages and writing/hacking desktop apps to work with their private microblogging networks yet? It would seem to me to be the obvious outgrowth of the Twitter phenomenon: ambient communication for secret societies.

(Which you can take to mean “gated communities,” “dev teams” “people who like their privacy” or “bomb-throwing anarchists.”) …

I’d happily run two microblogging desktop apps: one for Twitter, and one for My Spooky Friends Net. And, after a while, I’d probably stop using the Twitter app, I’d imagine.

I’d be willing to work on My Spooky Friends Net.

Update: There are a ton of apps that work with Laconica / identi.ca already!

I need an HTCPCP daemon.

Or an intern.

There is coffee all over the world. Increasingly, in a world in which computing is ubiquitous, the computists want to make coffee. Coffee brewing is an art, but the distributed intelligence of the web-connected world transcends art…

I’m gonna go make some coffee. Blog post on really simple ruby daemonizing coming soon. Stay tuned.