search

google-code-export / microblog-purple

Automatically exported from code.google.com/p/microblog-purple
GNU General Public License v3.0
2 stars 0 forks source link

Retweet is cut off at 140 characters #202

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
1. Retweet a tweet the twitter way
2. mbpidgin adds "RT @personsname" to tweet
3. the tweet is cut off at 140 characters. This way a tweet is shortened, and 
you have to go to twitter.com to see the remaining of this tweet. 

What is the expected output? What do you see instead?
The entire tweet as shown at twitter.com

What version of the product are you using? On what operating system?
Windows 7, 0.3

Please provide any additional information below.
Tweet is fully available at twitter.com,  but cut of in pidgin.

Original issue reported on code.google.com by rene...@gmail.com on 15 Jul 2010 at 2:14

GoogleCodeExporter commented 9 years ago 
This is really annoying, esp when there are links on the end of the RT, the 
whole tweet is visible at twitter.com, the Twitter API docs imply the whole 
tweet is returned to the client so presumably it's mp-purple that is truncating 
it. If so it should be an easy fix.

Original comment by ely.pedd...@googlemail.com on 15 Dec 2010 at 12:14

GoogleCodeExporter commented 9 years ago 
@ely.peddler No, the problem is, each tweet entry returned by the Twitter API 
has the attribute "text" which is used by mbpidgin. For normal tweets this 
contains the full text of the tweet. But for retweets this contains the 
truncated text with prepended "RT @user: ". Instead, there is an additional 
attribute "retweeted_status.text" which contains the original text, not 
truncated nor with prepended "RT ....". mbpidgin now has to check for this 
additional attribute and use this if present.

Original comment by sumeru...@googlemail.com on 15 Dec 2010 at 1:30

GoogleCodeExporter commented 9 years ago 
here ya go: compiles and runs fine, no obvious leaks (not sure whether xml 
nodes need to be free'd or not, from the rest of the code it appears it 
suffices to free the top node); my netbook is too slow to run it in valgrind, 
please test :)

Original comment by iac...@gmail.com on 20 Dec 2010 at 9:11

Attachments:

GoogleCodeExporter commented 9 years ago 
I took the patch and modify it a bit. Now it's in SVN.

Original comment by somsaks on 20 Dec 2010 at 5:10

GoogleCodeExporter commented 9 years ago 
Would you be kind enough to compile the modified plugin and upload it here as 
beta?

Original comment by sumeru...@googlemail.com on 12 Jan 2011 at 3:44

GoogleCodeExporter commented 9 years ago 
I've made deb packages from the svn, and properly tested the ubuntu 64 bit 
version.

Here attach You the 2 binary deb and the 3 sources packages/file

Original comment by epi...@gmail.com on 14 Apr 2011 at 2:14

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks, but I do not know how to use this. :-/ Maybe I should mention that I am 
a windows (7, 32bit) user without any knowledge about compiling a pidgin plugin?

I think the i386.deb is for windows? But what to do with the .so files?

Original comment by sumeru...@googlemail.com on 18 Apr 2011 at 9:54

GoogleCodeExporter commented 9 years ago 
No, You cannot install them on Windows because these packages are ONLY for 
Debian/Ubuntu GNU/Linux.

Original comment by jordisa...@gmail.com on 20 Apr 2011 at 1:41

GoogleCodeExporter commented 9 years ago 
Issue 243 has been merged into this issue.

Original comment by andresen.nils@gmail.com on 13 Jun 2011 at 7:18

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 

Error: Dependency is not satisfiable: libpurple0 (>= 1:2.6.0)

Even though I have 2.7.11 I have no idea why it is says 1:version, but it's 
clearly doing something.

libpurple0
Installed Version 2.7.11-2

Original comment by 133794...@gmail.com on 14 Jun 2011 at 1:07

GoogleCodeExporter commented 9 years ago 
Hi 133794 (Author of comment#11),
Are you trying to install one of the packages from comment#6? Which one? On 
which distro are you?

Original comment by andresen.nils@gmail.com on 14 Jun 2011 at 6:49

GoogleCodeExporter commented 9 years ago 
I forgot to say, debian amd64.deb

It seems to be working just fine, though, after i changed it and repackaged it.

Original comment by 133794...@gmail.com on 14 Jun 2011 at 4:54

GoogleCodeExporter commented 9 years ago 
It would be gorgeous if somebody could compile a windows version... :-) I'd 
like to test the new fixes.

Original comment by sumeru...@googlemail.com on 14 Jun 2011 at 5:10

GoogleCodeExporter commented 9 years ago 
Hi 133794. What did You change? I created these sources and binaries.

Original comment by epi...@gmail.com on 14 Jun 2011 at 5:18

GoogleCodeExporter commented 9 years ago 
In the Depends section for libpurple0 ( >= 1:2.6.0)

I changed it to libpurple( >=2.6.0)

that's it. Nothing too complicated or well that interesting really. It was just 
not working for some reason.

Original comment by 133794...@gmail.com on 14 Jun 2011 at 5:23

GoogleCodeExporter commented 9 years ago 
Ok, the problem is the different version nomenclature between debian and 
ubuntu. This happen some times.
These packages were created for ubuntu. that's all

What do you mean with "It was just not working for some reason"? It's still not 
working?

Regards,

Original comment by epi...@gmail.com on 14 Jun 2011 at 5:45

GoogleCodeExporter commented 9 years ago 
The original version, and that is weird. I don't know why ubuntu would call it 
1:2.6.0. Maybe DEX will help fix such issues. Since calling it as they do makes 
no sense. Since the rest of the package's dependencies are using 'normal' 
version numbers.

Original comment by 133794...@gmail.com on 14 Jun 2011 at 5:53

GoogleCodeExporter commented 9 years ago 
sumeru, 
I have added the installer for the 0.3.0-svn384. I am not all too sure that 
everything worked fine, since compiling pidgin under windows is no fun. So use 
with care. 
Have Fun.

Original comment by andresen.nils@gmail.com on 14 Jun 2011 at 10:02

Attachments:

GoogleCodeExporter commented 9 years ago 
Yay, new features! Thanks! Seems to work fine, no crashes since yesterday, yet. 
Have not tested all features yet. I have not installed it with the installer, 
only unzipped and copied the .dll's for twitter and twitgin. Interestingly the 
new dlls have only 15% the size of the older ones.
Sadly the timestamps are still wrong (see Issue 189).

Good work anyway!

Original comment by sumeru...@googlemail.com on 15 Jun 2011 at 9:29