Monthly Archives: March 2011

Many bug fixes and productivity enhancements

Here comes an update of Postler with a focus on solving problems and small productivity enhancements. DockManager API is now supported, so Docky and the latest AWN show a badge for unread mail.

You can also use Blind Copy when composing messages now. And you can specify which port should be used for sending, including secure SMTP support via port 465. Otherwise STARTTLS is used.

Keyboard users rejoice, there is actually an overview of keyboard shortcuts now. Including Alt+Up/ Down to jump to the next or previous unread message.

And you can delete messages from saved searches, which means a lot if you use them in place of inboxes such as “work” or “bugs”. For further changes see the change log.

So [http://archive.xfce.org/src/apps/postler/0.1/postler-0.1.1.tar.bz2#!sha1!f5c73c0219844d4092860eb4d8aa36223027b298 download Postler v0.1.1] (245 kB) now and have some fun reading mail, not setting it up.

For Ubuntu and derivatives, there are two PPA’s available, ppa:postler-dev/ppa and ppa:postler-dev/devel for stable and daily builds respectively.

An icon theme such as Elementary, Faenza or Buuf is recommended, at least as a fallback. And [https://launchpad.net/dexter-rolodex addess book Dexter] for contact auto completion.

Fingerprints, Frequent questions and fidelity

One thing history shows is, nobody wants to write documentation. Even though a number of people actually offered to do so, it never happened. And then you notice, hey, there is the FAQ in the wiki, and it is full of tips and tricks, and attracts users to suggest improvements. So why not use that as the documentation? So that’s what we do now. A side effect is that it will always be shipped because no longer is docutils needed. Which bears another lesson: if you make it too easy to disable something people may start to think it is not useful at all.

A sudden enlightenment as it sometimes happens and luck while typing key words into DuckDuckGo brought me to: Link Fingerprints. I have been very well aware of the utility of checksums for years. And yet, I will admit, I often enough ignore downloads which offer me an SHA1 or MD5 sum to verify my files. Why? Because it is different for every single site and because I have to fire up a console to switch to the right folder and compute the checksum, depending on which one is provided. That is simply annoying.
So I thought there must be a way to handle that automatically. And within minutes I found a Firefox extension that reads “fingerprints” embedded in hyperlinks. From this version on Midori will show such a checksum and display a warning if it doesn’t match. I use this for new releases of Midori from now on.

See http://mdhashtool.mozdev.org/lfinfo.html for the details.

As always, see the ChangeLog for all the other nice improvements.

So [http://archive.xfce.org/src/apps/midori/0.3/midori-0.3.3.tar.bz2#!sha1!01baf6243f7b00af5e5b4eb6ac5d3233e60bc993 download midori v0.3.3] (828 kB) ([http://archive.xfce.org/src/apps/midori/0.3/midori-0.3.3.tar.bz2.md5 MD5]) ([http://git.xfce.org/apps/midori/tree/ChangeLog ChangeLog]) already!

[http://www.twotoasts.de/media/midori-0.3.3.7z#!sha1!49904752d36861a19eb6b1a90baf070b35566fef Midori Win32 Archive v0.3.3] (11 MB)