Feature: don't autosave blist.xml upon "last_seen" changes

Peter Lawler bleeter at gmail.com
Sat Mar 30 07:08:40 EDT 2013

On 30/03/13 21:24, immerrr again wrote:
> The problem is that a buddy going offline alters
> "last_seen" node attribute

What you'd probably want to do is modify the blist so that plugins can 
have a preference to not write blist updates to disk immediately (you 
could have it set a timer for X minutes, or account logoff, or pidgin 

That's to say, hardcoding looking for the last_seen node would probably 
not get accepted but working out a way for plugins to tell blist not to 
autosave if this, that or someother node gets changed but to save if 
one, another or yetmore nodes get changed is likely to be more 
acceptable to the devs.

This is to say, to get 'last_seen' to not write as much to disk, blist 
probably needs changing then the last_seen plugin needs changing to meet 
the new blist foo.


More information about the Devel mailing list