[Pidgin] #13265: Rewrite buzz errors to be protocol-specific when buzz is not supported

[Pidgin]

#13265: Rewrite buzz errors to be protocol-specific when buzz is not supported
----------------------------+-----------------------------------------------
 Reporter:  Sman789         |     Owner:  rekkanoryo
     Type:  enhancement     |    Status:  new       
Component:  unclassified    |   Version:  2.7.9     
 Keywords:  Facebook, buzz  |  
----------------------------+-----------------------------------------------
 When "buzzing" on Facebook - the error "Unable to buzz, because (''name'')
 does not support it or does not wish to receive buzzes now." is given.
 This is fair enough, as Facebook does not support buzzing, but I feel that
 this should be conveyed in the message so users don't go wasting time on
 futile attempts to enable it on Facebook. Something like "Unable to buzz
 as this feature is not yet supported by Facebook" might be more
 appropriate - as it includes the name of the service being used (so users
 know this only applies to certain services) and it also says that this
 feature is actually impossible at the present time (as far as they are
 concerned, as users and not FB developers).

 Of course, a similar message should be shown for other services which also
 do not support it. It's just to reduce confusion, really, and it avoids
 this general purpose (unspecific) error situation which can be very
 annoying.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/13265>
Pidgin <http://pidgin.im>
Pidgin