Pidgin Update Notifier

Mark Doliner mark at
Mon Nov 1 19:10:47 EDT 2010

On Mon, Nov 1, 2010 at 4:05 PM, Daniel Atallah <datallah at> wrote:
> On Mon, Nov 1, 2010 at 18:43, Francois Botha <igitur at> wrote:
>>> The other factor is: What should we do when we get a response that
>>> doesn't contain the magic token?
>>> Suppress any UI?
>>> Pop up an error message?
>>> I'm probably in favor of the latter (displaying a message about
>>> invalid content being received when checking for a new release).
>> I'm very much in favor of the former. Otherwise I'm going to get an
>> awful lot of popups. Keep in mind my Pidgin is open 24/7. Rather than
>> a popup, what about an "inline error message", like what is currently
>> used to indicate an update?
> Note that the update checking is only performed at most once a day.
> I suppose we could suppress the UI and only display information in the
> debug log.  The problem with this approach is that the user has no
> indication that the release notification is not working properly.
> Sorry, I didn't mean to show a popup, just to have a minidialog
> similar to the real release notification indicating that we were
> unable to check for updates with the same link to the website (which
> may or may not work in their browser, but at least if they click it,
> they'll see the message from their annoying firewall).

The ideal behavior in my mind is to disable the plugin, show a
minidialog with an error message (and a link to the website or
whatever) and a "re-enable plugin" button.


More information about the Support mailing list