[twitter-dev] edit application - time estimation until changes committed

2011-06-13 Thread ds
I've edited my twitter app several times(change app name,
description,icon) and each change took a very long time until i was
able to actually see it.

How long does it take until changes on twitter app take effect?


Thanks

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk


[twitter-dev] Re: Incorrect search results

2010-09-23 Thread DS
Just a note, we fixed the problem. The ID that was not working was
created a while ago an never used until now.
We just set the tweets to be private, saved, logged out, then logged
in, set tweets to public, saved.

After that refresh of the parameters things are working. Seems it just
needed some sort of database refresh since
it was an old, inactive id.

On Sep 22, 7:35 pm, DS goonlin...@gmail.com wrote:
 I would like to understand which users and posts end up searchable
 with the search api and the Twitter search web page.

 I have examples of a user who has posted but his results are not
 viewable by either search api or web page.
 The tweets are visible in the users timeline and those that follow the
 user, but not in search. The user settings
 allow his tweets to be public.

 Another user works fine and has posts immediately available in all
 searches and followers.

 The settings for these two users appear to be the same.

 Any advice on how to debug and what the rules for the search
 availability of tweets.

 Thanks.
 ...Dave

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: oAuth and Direct Message

2010-06-21 Thread ds
I solved the problem.

I did not have an  between my two parameters in the POST body.

Adding  between the text and user parameter fixed it.

Thanks Matt.

On Jun 21, 1:10 pm, themattharris thematthar...@twitter.com wrote:
 Hey Dave,

 Looking through your signature base string just a couple of things
 which jump out and would be worth checking:
 * There are some spaces in the nonce and timestamp where there
 shouldn't be. In all honesty this is most likely email formatting
 problems but I wanted to point it out just in case.
 * Your text is encoded three times which isn't good and could be the
 source of the problem depending on what else you are doing when you
 send your request. I want to rule it out as a symptom so can you take
 a look at that, and why it is encoded one extra time. When I run tests
 I see my text string similar to text%3Djust%2520a%2520simple
 %2520message%2520test. yours, in it's current encoding, would read as
 just%252520a%252520simple%252520message%252520test.

 Matt

 On Jun 18, 9:54 am, Acme Dave acmedav...@gmail.com wrote:



  Thanks Matt,

  I am still having problems. Here is the output of my test app.
  I am able to update status. So I know my POST logic is working correctly.

  Info sigBase: POSThttp%3A%2F%2Fapi.twitter.com
  %2F1%2Fdirect_messages%2Fnew.xmloauth_consumer_key%3DCKEY%26oauth_nonce%3D 
  5855976111049200858%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp% 
  3D1276879684%26oauth_token%3DATOKEN%26oauth_version%3D1.0%26text%3Dyes%2525 
  20very%252520good%252520message%26user%3DTOUSER

  Info url:http://api.twitter.com/1/direct_messages/new.xml

  ERROR during token access exchange: java.io.IOException: Server returned
  HTTP response code: 401 for 
  URL:http://api.twitter.com/1/direct_messages/new.xml

  Extended error response: ?xml version=1.0 encoding=UTF-8?hash
  request/1/direct_messages/new.xml/request  errorIncorrect
  signature/error/hash

  On Fri, Jun 18, 2010 at 9:21 AM, themattharris 
  thematthar...@twitter.comwrote:

   Hi Dave,

   I seemed to have missed your message originally. Are you still
   experiencing problems with this?

   In answer to your question there isn't anything special required for
   signing requests to send direct messages. If you are still having
   problems can you provide us with your signature base string (without
   any tokens/keys).

   Matt

   On Jun 11, 9:32 am, ds acmedav...@gmail.com wrote:
I am having trouble sending a direct message with:
  http://api.twitter.com/1/direct_messages/new.xml

I have been able to successfully post status updates with my code
using oAuth.
I have a java based custom application that is working fine for these
updates.

When trying to post a direct message I get 402 errors with incorrect
signature.

Basically I am using the same signature generation as update except I
replace
status with text and add user at the bottom of signature generation.
Just like
the oAuth example page on twitter.

Then I pass the two parameters in the request body.

I also tried moving everything to url parameters but got the same
error.

Is there anything special about parameters for direct message when
using
oAuth?

Does it sound like I am doing this correctly with my post/body method?

Thanks,
...Dave


[twitter-dev] 401 Invalid / used nonce

2010-06-18 Thread ds
I have a small sample application I use for testing. This uses a saved
token and key.
The application works fine. I am able to get timelines, post status
updates, etc.

When moving this application to another system I now get the
invalid / used nonce on calls to the twitter api from this
application when using it on the new system.

I have three systems I have tried, two work and one does not. The
error invalid /used nonce does not tell me what is wrong. All the
systems have the same version of java and are running the exact same
application code.

Below is some trace information. Does anyone see something wrong with
my signature in the failing system vs the working systems.

Computer A (SUCCESS):
Info sigBase: GEThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
%2Fhome_timeline.xmloauth_consumer_key%3DCKEY%26oauth_nonce
%3D2887595401430130447%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1276825592%26oauth_token%3DATOKEN
%26oauth_version%3D1.0
Info url: http://api.twitter.com/1/statuses/home_timeline.xml
Info return: resp:?xml version=1.0 encoding=UTF-8?statuses
type=arraystatus  created_atFri Jun 11 16:57:45 + 2010/
created_at……./statuses

Computer B (SUCCESS):
Info sigBase: GEThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
%2Fhome_timeline.xmloauth_consumer_key%3DCKEY%26oauth_nonce
%3D6453132097719094794%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1276825993%26oauth_token%3DATOKEN
%26oauth_version%3D1.0
Info url: http://api.twitter.com/1/statuses/home_timeline.xml
Info return: resp:?xml version=1.0 encoding=UTF-8?statuses
type=arraystatus  created_atFri Jun 11 16:57:45 + 2010/
created_at……../statuses

Computer C (FAIL):
Info sigBase: GEThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
%2Fhome_timeline.xmloauth_consumer_key%3DCKEY%26oauth_nonce
%3D4424748944999180113%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1276818453%26oauth_token%3DATOKEN
%26oauth_version%3D1.0
Info url: http://api.twitter.com/1/statuses/home_timeline.xml

ERROR during token access exchange: java.io.IOException: Server
returned HTTP response code: 401 for URL: 
http://api.twitter.com/1/statuses/home_timeline.xml

Extended error response: ?xml version=1.0 encoding=UTF-8?hash
request/1/statuses/home_timeline.xml/request  errorInvalid /
used nonce/error/hash



[twitter-dev] oAuth and Direct Message

2010-06-11 Thread ds
I am having trouble sending a direct message with:
http://api.twitter.com/1/direct_messages/new.xml

I have been able to successfully post status updates with my code
using oAuth.
I have a java based custom application that is working fine for these
updates.

When trying to post a direct message I get 402 errors with incorrect
signature.

Basically I am using the same signature generation as update except I
replace
status with text and add user at the bottom of signature generation.
Just like
the oAuth example page on twitter.

Then I pass the two parameters in the request body.

I also tried moving everything to url parameters but got the same
error.

Is there anything special about parameters for direct message when
using
oAuth?

Does it sound like I am doing this correctly with my post/body method?

Thanks,
...Dave


[twitter-dev] Widget Profile - Tweet Background floating above lightbox

2010-01-12 Thread ds
I have added a Twitter Profile Widget to a website I am developing. It
works well and looks good but I have a slight problem in that same web
page invokes a lightbox using mootools and the 'tweet background', not
the whole widget, floats above my lightbox when displayed. It could be
a 'z-index' modification but all the same it is strange that the whole
widget isn't consistently floating above the lightbox.

How can I change this please so that it doesn't do this?

Thank you

DS