Drop Gwibber from default install

[Bedwell, Jordon]

On Sun, Mar 11, 2012 at 12:31 PM, Rodney Dawes
<rodney.dawes at canonical.com> wrote:
> I don't think a couple of people expressing a little frustration with
> a couple of missing or removed features, is a good reason to remove
> something from the default install.

Why? You guys think a few people constitutes a reason to make bad UI
choices.  Yes this is a shot at your supposed study about usability
which was far from a study, far from unbiased and not even a real
study.  Such a small sample group it was more like actually it was
nothing.  What is different about this situation other then it's the
opposite of what you guys think, and actually right and true.

> Even if I use the Twitter web site to interact with it, and gwibber is
> "slow" to update, it is useful to see the notifications which pop up
> due to gwibber running on my system (though I have a bug with where
> the notifications are popping up, in notify-osd).

Because you can't use Chrome and a small little addon to send updates
from twitter.com to notify, or hell, better, just use built-in desktop
notifications in Chrome.  I'm sure you could even build an addon that
does that for Firefox if one doesn't exist.  So your point is moot.

> If you haven't got a reasonable replacement, then your only goal is
> to punish others by removing something they might use, because you
> have some frustrations with it yourself.

Or is their goal to save them the agony?