It'd be nice to put the date/time on error messages in the desktop app. Sometimes, when I return to it after a while, I see an exception, but I don't know how recently it was.

"0min" would look better displayed as "now"

If you do not have a ~/.trimetid file, the thread crashes with an unhelpful error

[briane@briane-linux desktop_service]$ ./trimetter_test.rb
./trimetter.rb:111:in fetch_update': undefined methodempty?' for nil:NilClass (NoMethodError)
from ./trimetter_test.rb:30

Instead of a 20-character max per line, bump that up and let the line scroll.

Split Trimetter to a gem

The blue fade is such a light shade of blue it's hard to distinguish from white, under certain lighting conditions. It should either be a darker shade of blue or a more drastic color swing.

Use introspection or somesuch so that you can just point the desktop app to a folder of plugins and have it automatically detect and launch them without having to hand-add each into the main Ruby script.

A temporary error in the Trac plugin (or, probably, ANY plugin) such as connectivity or temporary server issues causes the errored() function to be called and terminates the thread. There are no retries. The thread never again resumes until you restart the complete service.

Implement IP-based security. This means either forking or monkeypatching the Arduino code and the Webduino library, then sending pull requests back to those projects to get the features implemented in the mainline.

RegEx for matches goes against the plural form of the word, barfs on singular.

Finish initial release

If a thread (on the desktop application) dies some time after launch, there is no great visual notification. Stale data for just that thread could be displayed on-screen. There actual error message and stack trace could have scrolled off-screen in the desktop app's window (if running windowed and not headless). A couple of different possible ways to handle this:

• Have some kind of clear() or error() function that gets called within the thread's rescue or just after that clears its relevant parts of TextBuffer
• Check the Thread object for running or not if the count of should-be-running versus actually-running, print persistent error and/or do something on the hardware display (flash, print text, etc.)

The conflict resolution code is placeholder/nonexistent.

The ability to insert characters into the TextBuffer rather than complete lines.