KGIII / pino-twitter

Automatically exported from code.google.com/p/pino-twitter
GNU Lesser General Public License v3.0
0 stars 0 forks source link

Pino 0.2.11 stopped working with twitter since august 31. #319

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Started failing connecting to twitter since yesterday morning.

Other Twitter clients, like Pidgin, gwibber or mitter, can't connect since 
yesterday too.

The reason is Twitter changed the authentication method for 3rd party connector 
clients.
http://www.smartphonegurus.com/forums/index.php?/topic/11487-some-twitter-client
s-including-twikini-to-stop-working-next-week/

Pino needs urgent update to new authentication protocol required for third 
party programs.

gdb pino
GNU gdb (GDB) Fedora (7.1-33.fc13)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/pino...Reading symbols from 
/usr/lib/debug/usr/bin/pino.debug...done.
done.
(gdb) run
Starting program: /usr/bin/pino 
[Thread debugging using libthread_db enabled]

** (pino:2873): WARNING **: Invalid GValue unboxing (wrong type or NULL)
[New Thread 0x7ffff0e01710 (LWP 2876)]
[New Thread 0x7ffff02e8710 (LWP 2877)]
[New Thread 0x7fffe4f33710 (LWP 2878)]
[Thread 0x7fffe4f33710 (LWP 2878) exited]
[New Thread 0x7fffe4f33710 (LWP 2879)]

Original issue reported on code.google.com by darksh...@gmail.com on 1 Sep 2010 at 3:10

GoogleCodeExporter commented 8 years ago
this will be fix when?
i can't login since yesterday

Original comment by jfca...@gmail.com on 1 Sep 2010 at 10:55

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Same as 229

Original comment by geob...@gmail.com on 2 Sep 2010 at 7:13

GoogleCodeExporter commented 8 years ago
i will provide patch and may be PPA in 4 days

Original comment by lost.chi...@gmail.com on 2 Sep 2010 at 1:57

GoogleCodeExporter commented 8 years ago
got working timeline, and broken non-twitter services (dunno if i will fix them)

Original comment by lost.chi...@gmail.com on 4 Sep 2010 at 2:58

Attachments:

GoogleCodeExporter commented 8 years ago
posting works too for latin-only characters: 
http://twitter.com/iiiii/status/22993396758 :3

Original comment by lost.chi...@gmail.com on 4 Sep 2010 at 5:54

GoogleCodeExporter commented 8 years ago
How do you build this new version? I've pulled the source from your updated 
clone of the repo and run "cmake ." (after getting all the -devel dependencies) 
followed by "make", but it bails with:

src/main_window.vala:26.7-26.11: error: The namespace name `OAuth' could not be 
found
using OAuth;
      ^^^^^
src/main_window.vala:87.16-87.21: error: The type name `Client' could not be 
found
    public static Client? client;
                  ^^^^^^
Compilation failed: 2 error(s), 0 warning(s)

My first guess would be that the cmake hasn't been updated to include the new 
code, but then I don't know how you managed to build and run it :)

Original comment by ibbo...@gmail.com on 4 Sep 2010 at 6:16

GoogleCodeExporter commented 8 years ago
it does not handle auth token request right, if u want to test it:
1. register app @ dev.twitter.com 
2. update MainWindow.vala with yours consumer_key/secret
string cons_key = "969YbgNJ2SYnvOZFLpO7fQ";
string cons_sec = "q8CX6pWJuabuLh5SolwCPO8O8CXgIJcDtFW4DuRpaY";
client.set_access_token(your_token, your_token_secret); // Twitter will tell 
you values for you account+your app for testing
3. ./waf configure && ./waf build && sudo ./waf install
4. Enjoy

PS> pushed update cmake build

Original comment by lost.chi...@gmail.com on 4 Sep 2010 at 6:25

GoogleCodeExporter commented 8 years ago
Nearly there - I can fetch messages, but sending gets rejected. I've probably 
not done something right, but it looks promising (and it is still the old v0.2 
GUI, which I prefer :) ) so I'll keep an eye on it. Thanks.

Original comment by ibbo...@gmail.com on 4 Sep 2010 at 6:52

GoogleCodeExporter commented 8 years ago
there are some issues with messages that has commas, can you tell which msg you 
try to post?

Original comment by lost.chi...@gmail.com on 5 Sep 2010 at 9:04

GoogleCodeExporter commented 8 years ago
Ah, yes, appears to be commas. Just tried a message with and a message without. 
Message without comma worked, message with comma failed. An encoding issue or 
something?

Original comment by ibbo...@gmail.com on 5 Sep 2010 at 6:11

GoogleCodeExporter commented 8 years ago
dunno, there are `Invalid signature` answer if i left then unencoded (they are 
reserved http://www.blooberry.com/indexdot/html/topics/urlencoding.htm, so 
libsoup.URI does not encodes them by default), and `500 error` if i encode them 
:)
Will sniff gwibber traffic tonight to see what i`ve done wrong

Original comment by lost.chi...@gmail.com on 6 Sep 2010 at 9:05

GoogleCodeExporter commented 8 years ago
lost.childZ, thank you for your efforts.

Original comment by tro...@gmail.com on 6 Sep 2010 at 6:28

GoogleCodeExporter commented 8 years ago
pushed comma fix

Original comment by lost.chi...@gmail.com on 6 Sep 2010 at 9:20

GoogleCodeExporter commented 8 years ago
i can't use pino....this is from 2 weeks...when the ubuntu package fixed?

Original comment by jfca...@gmail.com on 8 Sep 2010 at 11:06

GoogleCodeExporter commented 8 years ago
pushed pin request, almost usable now :) but twitter oauth service fails often 
and needs better errors handling

Original comment by lost.chi...@gmail.com on 11 Sep 2010 at 10:39

GoogleCodeExporter commented 8 years ago
I've still not got this working reliably. The errors almost look like it isn't 
sending the right OAuth data and it only seems to happen with longer tweets, 
which probably have odd characters in them, so I still suspect the URL 
encoding. Based on an article about creating a command-line Twitter client in 
the latest LinuxFormat mag then it looks like almost everything should be 
encoded, because they use:

perl -p -e ‘s/([^A-Za-z0-9-._~])/sprintf(“%%%02X”, ord($1))/seg’

I tried writing my own method using Regex.replace_eval() and replacing all 
calls to URI.encode with my method, but it obviously did too much because it 
wouldn't even pull down my feed :(

I've tried Pino 0.3 as well, even though I don't like the sample UI screenshots 
(0.2 is nice and compact when I have one account), but the latest source won't 
build on my openSUSE box because of some undefined references :\

Original comment by ibbo...@gmail.com on 22 Sep 2010 at 7:51

GoogleCodeExporter commented 8 years ago
Hi!

can you provide sample fail-to-send tweets ?

Original comment by lost.chi...@gmail.com on 24 Sep 2010 at 6:27

GoogleCodeExporter commented 8 years ago
The first one I tried tonight gave me "401 Unauth: request requires user 
authentication":

"Cool Venn diagram of mythical creatures. Not sure I heard of all the Bull 
ones! http://www.flickr.com/photos/preshaa/3847027500/"

but

"PinoIBB test" 

worked fine straight after it.

Original comment by ibbo...@gmail.com on 24 Sep 2010 at 6:18

GoogleCodeExporter commented 8 years ago
Just found another one - "'" in a message fails, as does "!" and both are 
unencoded. I think the fuller encoding should work, if only it didn't encode 
too much somewhere along the line.

Original comment by ibbo...@gmail.com on 24 Sep 2010 at 8:00

GoogleCodeExporter commented 8 years ago
Okay, I've fixed it for ASCII and pushed it to a GoogleCode clone [1]. The main 
fix is rev 81d8f99557 [2] and then rev 5dd79f5fa3 [3] makes use of it 
everywhere. I've tested it with some Russian text and it fails, so I think my 
encode relies on a bad assumption that works for ASCII but not other character 
sets. Unfortunately the Vala documentation is lacking to say the least, and 
Valide won't even work properly for me, so it has been a bit of a fight to get 
it that far! I'll see what I can do about proper multi-lingual support, though.

[1] http://code.google.com/r/ibboard-pino/source/checkout
[2] 
http://code.google.com/r/ibboard-pino/source/detail?r=81d8f99557893ee87f4fe946d8
d2e682dec7b5cb
[3] 
http://code.google.com/r/ibboard-pino/source/detail?r=5dd79f5fa3cc6a6d30f0b50c0c
2079d790cf9df4

Original comment by ibbo...@gmail.com on 25 Sep 2010 at 9:32

GoogleCodeExporter commented 8 years ago
There we go, not a terribly difficult fix in the end :) Revision 284731615f 
fixes up non-ASCII messages (I tested with a sample bit of Russian)

[1] 
http://code.google.com/r/ibboard-pino/source/detail?r=284731615fba3d41dac53ae1e5
8bbec31dc31e80

Original comment by ibbo...@gmail.com on 25 Sep 2010 at 9:43

GoogleCodeExporter commented 8 years ago
pushed temporary fix, some special chars still does not work.

Original comment by lost.chi...@gmail.com on 25 Sep 2010 at 10:28

GoogleCodeExporter commented 8 years ago
plz check '~$*' in your version, will give it a try a bit later today

Original comment by lost.chi...@gmail.com on 25 Sep 2010 at 10:57

GoogleCodeExporter commented 8 years ago
Works fine, as do other char sets. Here's a test message send with PinoIBB: 
http://twitter.com/IBBoard/status/25489157352 (Google translates of "Test 
message" into Russian, Arabic and Greek, plus the characters you just added in 
the last revision)

Original comment by ibbo...@gmail.com on 25 Sep 2010 at 11:02