I've just posted a new build of 0.5.1 at the same URL as above. It
fixes a couple of bugs I've found, but most notably I added a
workaround for Twitter's SSL issue. Since I don't know when it will
be completely fixed -- or whether it will happen again in the future
-- I've made it so that if Trowl encounters an SSL error, it will fall
back to using a regular, unsecure connection. I added special error
text -- "Could not establish secure connection" -- so you'll know when
it has switched. It will try SSL again next time the app restarts.
(I might change it so that it re-tries SSL more frequently in the
final build.)
If anyone has comments, feedback or bugs that they've found, feel free
to let me know! Thanks!