Conversation
Notices
-
!choqok "Could not authenticate with OAuth." <- did Twitter break something or is this an isolated issue.
about a year ago from Choqok-
@losinggeneration Twitter, a friend of mine seems to have the same issue with #Twirssi
-
@losinggeneration No, It still works here :D
-
@mtux http://ur1.ca/9kqcz there's the console output if that's any help. Otherwise I'd be willing to help debug some more if needed
-
@mtux I can still post, it's just the main timeline is failing to load (it looks like retweets, inbox, & outbox all work as well)
-
@mtux Err, home timeline, I just tried public and that seems to work as well
-
@losinggeneration wow! so funny :)) It should be Twitter problem :D Because there's no difference between timelines in authentication code
-
@losinggeneration Did you check your TL Options->Update Interval? It's it a delayed or nothing happens at all?
-
10 minutes & every 10 minutes it gives the error again for the home timeline (you can check the rest of this thread in context for details)
-
@losinggeneration Check you machine time clock is on the right Time Zone or region. Different Time Zone usually sends that error
-
@amon0thoth1 It was working > 18 hours and then stopped. I've also tried removing the account, re-adding, and some other things.
-
@losinggeneration I told that because Daylight Time Saving or Traveling Time Zones impact your Time Lines.
-
My clock/TZ is correct. Also, DST was >3 months ago. I would think if that was an issue, it would have been an issue much sooner
-
@losinggeneration After checking your log , Clock comments I have no clues about it. I made my bet to client-server time synchronization
-
yeah, it's really strange that it's home_timeline and mentions that fail & others seem to work fine (posting,inbox,outbox,reply)
-
@losinggeneration Just 1 thing to try...Go to Account->Timelines Configuration- and watch if checkboxes are checked
-
home is checked. Without home checked I don't get an error, but am still without a home timeline (and the error comes back reenabling home)
-
@losinggeneration Not sure at all. Maybe deleting the !Choqok user setup files and rebuilding it from scratch. Then setting up your accounts
-
Same error, it almost /has/ to be an issue on Twitter's side .
-
@losinggeneration Any chances to switch to another ISP for testing purposes?
-
I don't think it's my ISP. My quick perl test with Net::Twitter was able to get my home_timeline that I just wrote.
-
@mtux Well, the plot thickens. This script that I just threw together works while choqok still doesn't: http://ur1.ca/9krmu
-
@losinggeneration So. It was solved, does it?
-
@amon0thoth1 my script works via oauth to get the home timeline, but choqok is still failing for some unknown reason
-
@losinggeneration That's sad...I'm running out of ideas
mtux likes this. -
@losinggeneration Just to isolate would you tried KDE Microblog Widget? It's minimal client.
-
It does indeed work.
-
@losinggeneration Great! I'm thinking to rename !Choqok file to old Home/.kde4/share/apps/choqok and reboot Not sure it will solve it
-
@losinggeneration I have the same problem as of yesterday. No home, and no posting to Twitter. #Choqok 1.3 on #Debian. Identica fine tho.
-
@losinggeneration Oh wait, I too can post to Twitter. It just gives me an error message afterwards when it can't update. No home though.
-
@mtux Copy that. I'll wait a few days, keep trying, and report back.
-