Comment 22 for bug 327172

an elegant form of notification is definitely an improvement to the current state.
the optimum is:
i flip a switch and its visual representation actually shows as flipped

what happens instead:
i flip a switch and the whole room turns dark so i can't see the switch i flipped

there is no problem with sending the current behaviour into the menus or preferences as an option.
the way gwibber is currently behaving though is not in line with the principles of usability described in the current hig-book.

the user is being surprised, his input is overinterpreted in a confusing manner, instead of implemented on the spot.

related issues are:
*there is no visual representation of whether or not i like a broadcast
*there is no visible button or [+] or tree symbol that would instantly expand a comment thread beneath a broadcast message
*comments are not threaded to the message at hand and displayed in context when posted
*the text input field does not visually change to indicate that i'm commenting, when i'm commenting and not writing a new broadcast message
*the status messages entered above the availability settings for IM automatically get sent to all active Microblogging accounts instead of IM accounts

where do i discuss a whole set of usability issues?
the gwibber ML is team only.. :S