Therefore also in the tab (on Firefox), even it the tab is pinned.
Cool. Nice.
Not sure if it is entirely useful, but I like it.
Wednesday, April 27, 2011
Google Calendar Goodie
Have you ever noticed that Google Calender shows the current day (of the month) as the favicon.
Therefore also in the tab (on Firefox), even it the tab is pinned.
Cool. Nice.
Not sure if it is entirely useful, but I like it.
Therefore also in the tab (on Firefox), even it the tab is pinned.
Cool. Nice.
Not sure if it is entirely useful, but I like it.
Saturday, April 23, 2011
The end of Flock
Flock Official End of Support Notice
Support for Flock browsers will be discontinued as of April 26th, 2011. We would like to thank our loyal users around the world for their support, and we encourage the Flock community to migrate in the coming weeks to one of the recommended web browsers listed below.
Our Recommendations
Since no further security updates will be provided to keep you safe on the web, we encourage all Flock users to upgrade to either Chrome or Firefox. Both are based on the same reliable technologies as Flock, and both are being actively maintained and improved. Also, each of these browsers has a broad selection of add-ons and extensions to customize and extend their capabilities.
For more information (including notes on how to migrate to other browsers), please see our FAQ.
Thanks,
The Flock Team
I de-installed it months ago anyway :(
Saturday, April 16, 2011
Thunderbird hack: Domain Specific Move
One of the most frequent actions in Thunderbird is to move a message that I received from a business partner or customer to a message folder for exactly this partner/customer. Same for messages I sent to them.
However, as you communicate with more customers and partners, the folder hierarchy will become more complex and I already need about 6 clicks to select the specific folder.
Sometimes I'm lucky and it is the most recently used folder, then I can do it with the "move again" function directly in the context menu; sometimes, it is at least in the recent folder menu, still 3 clicks.
WIBNI if TB could just remember that I always move messages from domain A to the folder X, lets say from "ibm.com" to folder "/Vendors/IBM" or something like that, and then present me with a one-click option on the menu.
So I wrote an add-on for this and called it "Domain Specific Move".
It does exactly what I described.
I find the most frequently used domain in the email (counting all from sender, recipient, cc-list).
If I already find a setting for this, I create an additional menu item in the move message menu for a move to this folder.
If not, I present a "learn" menu item, that lets you train the extension on where to put mails for this extension (i.e. register a folder for this domain). You pick the destination folder yourself. No magic included there.
Once I thus learned and stored the folder for this domain, I can - next time this domain appears - present the "Move to " menu item as above.
Configuration is stored in the preferences under "extensions.domainmove.".
Currently I have no options page for this, so if you want to change or remove an entry, you have to go to the prefs.js file or the about: dialog.
Yes, I know, filters can do the same; but when I select to manually run the filter, it will not tell me what exactly it is up to... The beauty of my approach (IMHO) is, that I see it on the menu and can decide otherwise, because not always does the folder registered for this domain really match.
In essence this is only a short cut with an educated suggestion. No behind-the-scenes magic.
Todos:
I will polish the code and implement some of the above todos, then I will post the first beta.
--
[1] well for me as an former Sun and now Oracle employee, all emails contain either an oracle.com or sun.com address and this domain contains no information on where to archive the email.
However, as you communicate with more customers and partners, the folder hierarchy will become more complex and I already need about 6 clicks to select the specific folder.
Sometimes I'm lucky and it is the most recently used folder, then I can do it with the "move again" function directly in the context menu; sometimes, it is at least in the recent folder menu, still 3 clicks.
WIBNI if TB could just remember that I always move messages from domain A to the folder X, lets say from "ibm.com" to folder "/Vendors/IBM" or something like that, and then present me with a one-click option on the menu.
So I wrote an add-on for this and called it "Domain Specific Move".
It does exactly what I described.
I find the most frequently used domain in the email (counting all from sender, recipient, cc-list).
If I already find a setting for this, I create an additional menu item in the move message menu for a move to this folder.
If not, I present a "learn" menu item, that lets you train the extension on where to put mails for this extension (i.e. register a folder for this domain). You pick the destination folder yourself. No magic included there.
Once I thus learned and stored the folder for this domain, I can - next time this domain appears - present the "Move to " menu item as above.
Configuration is stored in the preferences under "extensions.domainmove.
Currently I have no options page for this, so if you want to change or remove an entry, you have to go to the prefs.js file or the about: dialog.
Yes, I know, filters can do the same; but when I select to manually run the filter, it will not tell me what exactly it is up to... The beauty of my approach (IMHO) is, that I see it on the menu and can decide otherwise, because not always does the folder registered for this domain really match.
In essence this is only a short cut with an educated suggestion. No behind-the-scenes magic.
Todos:
- more flexibility with domains with more than 2 parts (e.g. at.ibm.com should map to ibm.com if there is no at.ibm.com)
- unlearn domains (without going to the about: dialog)
- option for domains-to-ignore; currently I ignore non-specific domains as gmail.com, a1.net, gmx.at, sun.com, oracle.com [1].
- ignore "my" domain (see comment re oracle.com)
I will polish the code and implement some of the above todos, then I will post the first beta.
--
[1] well for me as an former Sun and now Oracle employee, all emails contain either an oracle.com or sun.com address and this domain contains no information on where to archive the email.
Saturday, April 02, 2011
On podcasts - Not Print
Not only is a podcast not radio, it is also (not too surprisingly) NOT PRINT.
In a newspaper or journal you usually have the so called standfirst right after/below the headline summing the article to follow. Sort of an abstract, if you will.
This is quite convenient, because it allows you to learn what the article is about (not always that obvious from the headline alone), and maybe skip the article itself entirely.
Sometimes - if I know I am interested in the article - I will skip the standfirst... knowing that there is no additional information in it.
Either way, there are options to avoid the repetition.
Not so in a podcast.
In audio it is less easy to skip things.
If you provide a quick intro to a podcast, be very very brief. Only give the topic. Don't summarize the podcast. Especially not if the podcast is short (5-10 minutes). Do not repeat everything from the podcast in the abstract/standfirst.
Just don't.
It's annoying.
In a newspaper or journal you usually have the so called standfirst right after/below the headline summing the article to follow. Sort of an abstract, if you will.
This is quite convenient, because it allows you to learn what the article is about (not always that obvious from the headline alone), and maybe skip the article itself entirely.
Sometimes - if I know I am interested in the article - I will skip the standfirst... knowing that there is no additional information in it.
Either way, there are options to avoid the repetition.
Not so in a podcast.
In audio it is less easy to skip things.
If you provide a quick intro to a podcast, be very very brief. Only give the topic. Don't summarize the podcast. Especially not if the podcast is short (5-10 minutes). Do not repeat everything from the podcast in the abstract/standfirst.
Just don't.
It's annoying.
Subscribe to:
Posts (Atom)
Subscribe