Same for us, please let us know if there is anything we can provide /
do to restore oAuth access to our app. Some other comp. web-based apps
work 100%, so this is kind of embarrassing...
Many thanks in advance.
On 16 août, 17:41, Sean Callahan wrote:
> Yeah, no one can login tohttp://TweetPhoto
Can't agree more with 2.
Please guys, you need to convey a consistant and *visible* message to
your users.
On 16 août, 05:21, Jonathan George wrote:
> 1. It's been roughly 10 hours. How about an update?
>
> 2. It'd be great if you would post this to status.twitter.com, in
> addition to the dev
Hi Ryan,
Many thanks for the update.
On twitscoop, we have issues with the search api, which apparently
returns erroneous or ill-formed timestamps.
eg. http://www.twitscoop.com/search?twitter you'll see the latest
tweet will be dated "14465 days ago" :))
Cheers
On Aug 9, 7:34
Hi Alex,
Same thing happening to twitscoop. Our production IP is being blocked
for all streaming apis, oAuth api etc.
Do we need to send an email to the usual api address or have you
identified the third-parties being affected ?
Please let us know if there is anything we can do to help.
Many
Glad you stepped in, Chad, because I felt really stupid for a second.
And like I said, it's less harmful to have your oAuth session stolen
(you can just unauthorize the application) than to have your plain
twitter credentials exposed.
Anyway this is not the subject of this thread, I'm just glad w
Hi guys, is there an ETA for it to be restored ? It seems Oauth's
recommended approach is to simply add a warning notice on
authorization until this is fixed (this is what Google did). Anyways,
even with this security flow, oauth is safer than providing twitter
credentials to third parties...
Tha
