Closed GoogleCodeExporter closed 8 years ago
Check this
http://blog.programmableweb.com/2011/06/28/twitter-direct-message-enforcement-de
adline-this-week/
Seems like you need to regrant authorization to the application. I revoked
access and after that re-authorized and now it works again :)
Original comment by anwarpi...@gmail.com
on 2 Jul 2011 at 5:42
Good thought, I'll try and report back.
Original comment by schet...@gmail.com
on 2 Jul 2011 at 5:44
Sure enough, that did it. Thanks-
Original comment by schet...@gmail.com
on 2 Jul 2011 at 5:51
Original comment by xnrefor...@gmail.com
on 3 Jul 2011 at 7:25
Issue 407 has been merged into this issue.
Original comment by xnrefor...@gmail.com
on 3 Jul 2011 at 1:51
Issue 411 has been merged into this issue.
Original comment by xnrefor...@gmail.com
on 5 Jul 2011 at 9:50
Issue 413 has been merged into this issue.
Original comment by xnrefor...@gmail.com
on 9 Jul 2011 at 7:36
I filled a feature request that might stop these bug reports from comming in:
http://code.google.com/p/hotot/issues/detail?id=410
Original comment by prop...@gmail.com
on 9 Jul 2011 at 8:14
Issue 421 has been merged into this issue.
Original comment by xnrefor...@gmail.com
on 28 Jul 2011 at 6:50
I have the same error, only the new authorisation doesn't fix it. I'm on Mint
11.
Original comment by newtons....@gmail.com
on 22 Aug 2011 at 8:45
Autorization do not fix anything. Same error.
Original comment by tipsgnul...@gmail.com
on 23 Aug 2011 at 6:11
Same here. Even after reauthorize the app in twitter the error still present
Original comment by mariano....@gmail.com
on 24 Aug 2011 at 3:29
Here another one with the same error.
Original comment by tiagojpa...@gmail.com
on 24 Aug 2011 at 2:03
Same here. Even after reauthorize the app in twitter the error still present
Original comment by thwest1...@gmail.com
on 24 Aug 2011 at 3:29
Same for me even after reauthorize hotot in twitter :|
Original comment by the.sond...@gmail.com
on 27 Aug 2011 at 12:12
Having the same error on hotot for chrome, i've already reauthorized
Original comment by eSt...@gmail.com
on 28 Aug 2011 at 4:39
Original issue reported on code.google.com by
schet...@gmail.com
on 2 Jul 2011 at 4:16