[Pidgin] #301: Make number of saved popular statuses configurable

[Pidgin]

#301: Make number of saved popular statuses configurable
---------------------------+------------------------------------------------
  Reporter:  gagern        |       Owner:  seanegan
      Type:  enhancement   |      Status:  new     
  Priority:  minor         |   Milestone:          
 Component:  pidgin (gtk)  |     Version:  2.0     
Resolution:                |    Keywords:          
---------------------------+------------------------------------------------
Comment (by gagern):

 We don't have the distribution of the last 100 status changes. We only
 have the abolute usage counts and the timestamps of creation and last
 usage. At least that's what I see here on my beta6. And collecting more
 seems excessive to me.

 Using the usage count instead of the timestamp would help avoid the cyclic
 usage problem described in my initial description. However it would also
 make the sorting slower to respond to changed behaviour.

 If you were to use usage_count / time_since_created as an estimate of
 usage frequency, you could then apply the scheme you outlined, and try
 tweak it until it seems satisfactory. An alternative would be to simply
 examine the possible cutoff positions and take the one with the largest
 difference in estimated usage frequency. Saves a lot of math, and is best
 for all scenarios I can think of right now.

 I'd rather have 9 ± 3 entries instead of 6 ± 3. :-)

-- 
Ticket URL: <http://developer.pidgin.im/ticket/301#comment:6>
Pidgin <http://pidgin.im>
Pidgin