Configurable tweeting style

[GoogleCodeExporter]

1. PM (IM) style
2. Chat style

Original issue reported on code.google.com by somsaks on 25 Jul 2008 at 10:49

[GoogleCodeExporter]

3. Mixed style (Direct messages come as IM, others as Chat)
4. Email notification style (similar to how Facebook Plugin handles Facebook
Notifications) - nice for those of us who have pop-up notifications set

Original comment by nul...@gmail.com on 2 Aug 2008 at 9:35

[GoogleCodeExporter]

Issue 56 has been merged into this issue.

Original comment by somsaks on 21 Jan 2009 at 4:33

[GoogleCodeExporter]

Original comment by somsaks on 14 Feb 2009 at 5:39

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Sorry, IMHO "tweeting style" is a shallow description for this issue which is 
by no mean an "enhancement", 
but plain old defect. This "IM style" approach is the main reason why it does 
not work, as the now extinct 
Twitter's Jabber interface didn't work. There is no way to pretend that each 
and every received "twit" is 
an "IM", the message that you should read this instant.

Think about "chat", "conference", or whatever you wanna call IRC these days, 
that's exactly the way a 
twitter (or whatever other micro-clone) interface should be implemented. :(

My apologies for ruffling any feathers, but I'm really annoyed thinking that 
some folks wasted a lot of 
their precious time following this still born approach. :(

Original comment by altblue on 21 Mar 2009 at 11:22

[GoogleCodeExporter]

If all you concern are the blinking notification of incoming message, what if 
we can
disable the blinking for IM windows?

In Linux, this can be done by configuring message notification plug-in. For 
example,
right now I configure it to just show number of unread message (tweet) in 
bracket
without blinking.

I think the similar configuration should be available in Windows, since there 
is an
option for Pidgin to disable blinking.

This setting might active globally, so it will also affect other IM services as 
well.
I will look for the way to disable this just for specific account.

Note that, the main idea of supporting chat is to support autocomplete, which 
is not
available in IM style.

Original comment by somsaks on 22 Mar 2009 at 1:22

[GoogleCodeExporter]

That's not a good idea -- one broken behavior covered by other one? Really,
microblogs shouldn't be IM at all.

Original comment by matej.c...@gmail.com on 22 Mar 2009 at 8:13

[GoogleCodeExporter]

Both IM and Chat style is just a way to control windows. I checked in Pidgin 
code and
found that it allow each plug-in to control the "urgent" flag in messaging 
windows
separately. What you see is just default

IM -> Blinked when message coming
Chat -> Not blinked

So there is a possibility to set this specifically for twitter in IM windows, 
and it
seems to be easy to implement since we already handle displaying message in 
Twitgin.

What I propose above is just a workaround to show you how it will become (as 
said "I
will look for the way to disable this just for specific account). Would like to 
know
if this make sense for you all.

My point is, once we change everything to chat style, I don't sure that the 
feature
to be implemented, such as Avatar, TwitPic preview support, channel tracking, 
will be
possible, or it would still possible but way harder to implement. (Have to check
Pidgin code again. All this are base on what I have seen from other protocols).

Back to my original idea for "supporinting chat-style", the idea is

- Normal IM windows, without blinking, for normal tweet. You get fancy stuff 
like
avatar, preview, tweet tracking, etc...
- User can switch to chat windows when they want to do "group chat"-like. For
example, when you are in a seminar/conference/camp and you want to quickly
communicate in a group. You got only text. You possibly got autocomplete 
capability
added.

Original comment by somsaks on 23 Mar 2009 at 3:42

[GoogleCodeExporter]

Just noticed that latest response was from master Matej :)

I am welcoming more point on supporting chat style in MB. It's not that I will 
not do
this, it's just not on top of my list, especially if disable-blinking is 
possible.

Original comment by somsaks on 23 Mar 2009 at 10:13

[GoogleCodeExporter]

comment 7 explains it all -- I retract all my opposition against doing it 
pidgin-way
in IM style.

Original comment by matej.c...@gmail.com on 23 Mar 2009 at 10:22

[GoogleCodeExporter]

Issue 97 has been merged into this issue.

Original comment by somsaks on 7 May 2009 at 9:04

[GoogleCodeExporter]

Issue 93 has been merged into this issue.

Original comment by somsaks on 7 May 2009 at 9:04

[GoogleCodeExporter]

if you go down the "chat" route, configurable alerts would be very useful; say 
I 
want to watch certain terms, or users, and get a notification when they appear 
(this 
would be very useful with the "IM without blinking" approach, too, btw)

Original comment by iac...@gmail.com on 26 Mar 2010 at 7:10

[GoogleCodeExporter]

@iacobs, that's not mbpurple's job; pidgin can already do that (assuming “the 
chat
route” is taken). Watching for your nick is built-in, and watching for other 
words
can be done by a plugin (the “hilight” plugin IIRC).

If you want it *more* configurable alerts, then you want guifications.

Original comment by lalo.martins on 27 Mar 2010 at 12:06