Repeated Posts on Startup

[GoogleCodeExporter]

When Pidgin crashes (as seems to happen often to me - still trying to
figure out why) and I restart, I am always greeted with a message from
Twitter telling me the same posts I have already read.
Screenshot attached.

Original issue reported on code.google.com by nul...@gmail.com on 22 Aug 2008 at 9:27

Attachments:

• screenshot3.png

[GoogleCodeExporter]

yes, this is partly intentional (not the crash, of course). Because Pidgin will
automatically destroyed all instances of Mbpurple when it got disconnected. So 
all
the saved tweets are gone, so all the old tweets is coming back. 

I think the real problem is the crash. If possible, could u run it in debug 
mode?

pidgin -d > debug.log

Then send us the log when it crash? 

Original comment by somsaks on 23 Aug 2008 at 4:27

[GoogleCodeExporter]

These duplicate entries and popups quickly become annoying when you are using 
an 
intermittent Internet connection like roaming with wifi.  Not only that, but it 
results in many duplicate entries in the history logs, if you have that enabled.

If Mbpurple can save some 'state' information, possibly in the prefs.xml config 
file, then it can figure out which Tweets have already been displayed.  On 
Windows 
this is located at C:\Documents and Settings\<username>\Application 
Data\.purple\prefs.xml

I don't know if protocol plugins can save information in prefs.xml or another 
xml 
file, but a possible solution might be to split Mbpurple into two pieces, a 
protocol 
plugin and a Twitter protocol management plugin that would show up on the 
plugins 
window.  The management plugin could save settings to prefs.xml like any other 
plugin, and would enable the user to customize how Tweets are handled, e.g.:

1.) selector box: 'On Pidgin startup'
 a.) display all Tweets scraped from http://twitter.com/username
 b.) display only new Tweets scraped from http://twitter.com/username  (default)

2.) selector box: 'On reconnection'
 a.) display all Tweets scraped from http://twitter.com/username
 b.) display only new Tweets scraped from http://twitter.com/username  (default)

3.) selector box: Tweet grouping
 a.) Put all Tweets into a single shared IM window
 b.) Treat Tweets from the following people on your buddies list like instant 
messages, placing them into an IM window with that buddy (if this option is 
chosen, 
display a list of buddies with a checkbox next to each.  If checked, Tweets 
from 
that buddy will go into an IM window private to that buddy.)

Original comment by kaze0...@gmail.com on 28 Oct 2008 at 11:56

[GoogleCodeExporter]

It is possible to save anything, can even be our own file format. However, it 
will
require some amount of effort to implement this. I'll revisit this again after 
the
other things in my queue is cleared up.

I don't quite sure about your point on separated plug-in. I think it can be in 
the
same plug-in. 

Your idea on 3) is interesting, but I think of microblog-services is more like 
group
chat. It interested me to know if there are many people use it for one-on-one.

Original comment by somsaks on 29 Oct 2008 at 3:26

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by somsaks on 29 Oct 2008 at 3:27

[GoogleCodeExporter]

The idea behind a separated plugin was to give the user a GUI way to configure 
the
protocol plugin through the plugins window.  If that can be done all in one 
plugin,
great!

Twitter has higher latency than regular IM, and shares group chat 
characteristics as
well.  The thing is, though, that the list of Twitter friends someone has can be
small, and probably significantly overlaps the list of IM buddies.  I've come 
to find
that while Twitter posts sometimes have multiple people responding to 
one-another,
that's not always the case.  Instead, I find that they're more frequently status
updates or points of interest updates from friends.

To top it off, Twitter supports direct private messages and reply messages.  
Direct
private tweets are just like IMs, using a 'd' command.  These might make the 
most
sense to throw into a private IM window:
http://help.twitter.com/index.php?pg=kb.page&id=15

Replies to specific people are done using a '@':
http://help.twitter.com/index.php?pg=kb.page&id=70

Original comment by kaze0...@gmail.com on 4 Nov 2008 at 9:43

[GoogleCodeExporter]

IMO, direct message is a kind of urgent message sending to someone, since it 
will all
pop-up in their e-mails, mobile phone, etc... I seldom use it.

It is possible though to query just direct message and report it just like 
normal IM
message. I think this will be a separated enhancement.

Original comment by somsaks on 5 Nov 2008 at 1:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Fixed in SVN now. (For the part of saving received tweets permanently).

Original comment by somsaks on 16 Feb 2009 at 4:27

• Changed state: Fixed