Over 1,5 years ago the question was raised about why the
crossdomain.xml doesn't allow public access.
https://groups.google.com/group/twitter-development-talk/browse_thread/thread/e35a708400b529b3/2a8e40506a039072
https://groups.google.com/group/twitter-development-talk/browse_thread/thread/28232
a central server using a shared
account so the request numbers may be quite high
Martin
--
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
C
backend component and thus
wont be able to receive the callbacks?
Martin
On Feb 14, 7:14 pm, Carlos Hugo Gonzalez Castell
wrote:
> are usign oauth api?
>
> in this api your manage the callbacks twitter
>
> On 13 feb, 07:51, Martin Cronjé wrote:
>
>
>
> > Hi the
a central server using a shared
account so the request numbers may be quite high
Martin
--
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
C
://www.coresoft.com.au/coreforum/index.php?topic=38.0
On Nov 2, 9:40 am, Taylor Singletary
wrote:
> Hi Martin,
>
> Thanks for your patience in working through xAuth with the issues you're
> facing. Given the information you've provided, it's difficult to determine
> ex
=87aaa10a26a77fb99837fe711ecbaaa5;topic=38.msg43
On Nov 2, 11:22 pm, Martin Hannah wrote:
> Hi Taylor,
> Now I have the Access Token and I use the explanations
> inhttp://dev.twitter.com/pages/authto make a request on users behalf, I
> get a response from twitter:
>
> Twitter
th_signature_method="HMAC-SHA1",
oauth_timestamp="1288703533",
oauth_token="46989789-6NoccKZ1NVN3wdtlRGyhQrUG3b9RcU9Tkn372uIg3",
oauth_version="1.0", status="PostingthroughMicrosoftXMLHTTP"
Any suggestions ?
Martin Hannah wrote:
> Hi Taylor,
>
> Success, the missing
1st time, it wasnt obvious then.
So the find part of the send is:
objHTTP:send("x_auth_username=oauth_test_exec&x_auth_password=twitter-
xauth&x_auth_mode=client_auth").
So my last question is, should this be url encoded, because when we
URL encoded (as the doco suggests) it did
random number and
we borrowed and adapted some code to generate this number each time..
Please confirm that this is correct.
We are now performing another test based on your suggestions and
results of todays investigations/tests and will post results as soon
as complete.
Taylor Singletary wrote
act we used the syntax for
objHTTP:open and setRequestHeader("Authorization" that you see above,
in the same way as it is used in the googe examples in
http://oauth.googlecode.com/svn/code/javascript/example/AJAX.html
(open this Google example page and view HTML source from lines 32 to
53..)
We are c
We had an application successfully talking to twitter for a few years
prior to oAuth, and now converting this application to xAuth and cant
get past the first step.
The application gets a 401 "Unauthorized" response when attempting to
get the access token.
Have confirmed our program when provided
, Martin Hannah wrote:
> Hi Matt,
>
> Thanks for the response, I went back and looked closely at the
> possible trouble spots you suggested (the epoch time, the consumer
> key, the parameters not repeated) and its all fine.
>
> I used the program to produce epoc time and com
witter.com/pages/xauth .?
Can anyone help ..?
On Oct 24, 9:55 am, Martin Hannah wrote:
> Hi Matt,
>
> Thanks for the response, I went back and looked closely at the
> possible trouble spots you suggested (the epoch time, the consumer
> key, the parameters not repeated) and its all fin
" objHTTP .
objHTTP:open("POST",api-atokin, false, api-username, api-
password).
objHTTP:setRequestHeader('Authorization', v-params).
objHTTP:send("").
v-response = objHTTP:responseText .
I am stumped, and would appreciate any suggestions as to where
We are converting our Twitter interfaces to oAuth and from the advise
on http://twittervb.codeplex.com/wikipage?title=XAuth we are heading
down the path of xAuth for our desk top applications that use Twitter.
We opted not to use TwitterVB.dll for backward compatibility of older
sites, so we are f
rawurlencode() isn't the proper function for URL encoding, but I
> can't give you a better one right now.
I believe it is if you are on PHP 5.3 or later. Before that, this
should do it:
function oauth_encode ($str) {
return str_replace ('%E7', '~', rawurlenco
lose($ch);
curl defaults to GET, so you're signing a POST for the auth, but
doing a GET. Also, you're not sending the actual status you want to
update, just signing it.
--
Martin Dapas
@mahrteen
Its very good to hear, I hope he will be able to adress that soon.
yours
Martin
On 12 Apr., 18:29, Raffi Krikorian wrote:
> yup - totally :P just giving you an update that its been low on our
> priority list :P
>
> twitter now has a dedicated security manager, so i have just elevat
ight reduce the
responsetime and the quality of their applications).
And for what? To avoid or some temporary load difficulties? This API
is online/live for more
than a year now. I hope you reconcider opening it soon.
yours
Martin.
On Mar 19, 8:53 pm, "Orian Marx (@orian)" wrote:
> John, t
I think it's a API bug, even in the twitter page the paginator doesn't work
as expected, sometimes
appears, sometines not, and when appears it makes in a random manner.
i'm getting cursor 0 from API, using int or string representation, the bug
is in the API that sends
the cursor 0 randomly.
regar
of the twitter hype like this
wouldn't be possible anymore.
I think it would be great if you could provide some other means to
track the volume of tweets before the change of the status_id take
place.
When is this change supposed to happen?
Thx
martin
To unsubscribe from this group, send ema
Good morning,
just discovered the change of the rate limit and also the possibility
to lookup 100 users with one call.
Thank you so much to respond in such a generous way to our requests
here. Highly appreciated
Greets
martin
To unsubscribe from this group, send email to
twitter-development
+1 for asking for keeping the default as it is right now (should be
clear really strange to even discuss this)
To unsubscribe from this group, send email to
twitter-development-talk+unsubscribegooglegroups.com or reply to this email
with the words "REMOVE ME" as the subject.
just saw the API doc is already clear now
> Users can, at most, look up 1000 users in an hour.
thx
consider increasing the call limitations for at
least api white_listed applications.
Greets and happy weekend
martin
hi. I'm doing a server context, which make calls to API methods and I
would love to know how can I know user ID in general, without any
prior id, or how to generate valid user id. I would serve very
helpful, thanks
Hi.
I couldn´t find this on twitter api wiki.
Is it possible to search for tweets which contain a link to a
specified url? (For example to a blogpost.)
Thanks
Martin
add to the bug report!
/Martin
On Dec 6, 2:47 pm, Damon Clinkscales wrote:
> On Sun, Dec 6, 2009 at 3:24 PM, Martin Omander wrote:
>
> > I noticed the same behavior in my app: when I include since_id in the
> > search API call, I often don't get all the tweets I shoul
meter is a very useful
feature of the API. It would reduce system load and bandwidth
considerably for everyone if it worked right.
/Martin
On Nov 23, 6:14 pm, Hayes Davis wrote:
> +1 on this. I'm frequently getting 0 results from the search API (not an
> error, just 0 results) wh
I'm getting 404 today as well on "favorites/destroy" for well-formed
requests.
And this on recent favorited tweets using the API.
Any official response if this is a bug or not ?
Thanks - Martin
On Oct 15, 12:49 pm, Josh Roesslein wrote:
> Just ran my unit tests and they all
app is also affected.
L8er - Martin
www.wherecloud.com
On Oct 15, 6:49 pm, Marcel Molina wrote:
> Having retweets in the user_timeline isn't intentional. I'll be
> ensuring they don't appear there in the next few days. The only place
> they should be appearing (once pu
I have no problem with this new API call. But why is it also included
in the user_timeline payload ?
Is this inclusion official on the Twitter side...
Martin
On Oct 15, 9:46 am, ryan alford wrote:
> http://apiwiki.twitter.com/Twitter-REST-API-Method:-statuses-home_tim...
>
Thanks for the clarification.
That explains the inconsistent behavior we are seeing when trying to
load specific user timelines.
Do we have an updated api wiki that defines the semantics of the
fragment ?
Martin
www.wherecloud.com
On Oct 14, 10:59 pm, Josh Roesslein wrote:
> I think
I'm retrieving the timeline for a specific user:
curl http://www.twitter.com/statuses/user_timeline/ev.xml
Within that timeline, I see retweeted_status fragment.
Is this normal behavior ?
Thanks - Martin
n the book.
Best of luck!
/Martin
On Oct 10, 8:58 am, Dewald Pretorius wrote:
> I tried to check in Archive.org, but at some point in 2007 Twitter
> excluded /api with robots.txt.
>
> Besides, it was so interesting to see how the Twitter home page
> evolved over time that I got c
Same here; my app runs on Google App Engine and 40% of the requests to
the Twitter Search API get the 503 error message indicating rate
limiting.
Is there anything we as app authors can do on our side to alleviate
the problem?
/Martin
On Oct 5, 1:53 pm, Paul Kinlan wrote:
> I am pretty s
just curious ...
On Oct 2, 9:55 am, Nick Arnett wrote:
> On Thu, Oct 1, 2009 at 8:20 AM, Martin Dudek wrote:
>
>
>
> > Good morning
>
> > wonder if somebody knows how twitter determines the ten trends it
> > declares every five minutes? Is this a pure word/phras
Good morning
wonder if somebody knows how twitter determines the ten trends it
declares every five minutes? Is this a pure word/phrase frequency
algorithm or some more complexity behind.
Thanks
martin
lar a bit more spam free
so by posting this here I also hope to hear what means other twitter
API users
have developed to get rid of spam tweets they collect through the
twitter search API.
Greets
martin
Chad,
Very nice service that will accelerate development for app developers
who search Twitter. Best of luck!
/Martin
On Sep 29, 7:18 pm, Chad Etzel wrote:
> @Jesse, TweetHook is leveraging the Search API for now. The Streaming
> API has a totally different EULA and other subtle diffe
I'm seeing retweet_details information appearing in the payload of the
statuses/show call. Is this normal behavior?
Try this curl http://twitter.com/statuses/show/4297637412.xml
Thanks - Martin
On Sep 18, 4:57 pm, Marcel Molina wrote:
> The Retweet API launch is close at hand. You mi
Ryan: Is this still scheduled for today or tomorrow ?
Thanks
Martin Dufort
www.wherecloud.com
On Sep 11, 3:00 pm, Ryan Sarver wrote:
> Hwee-Boon,
>
> That is definitely part of the plan and hence why we are aiming for
> that Monday / Tuesday. We know what a strain it can be to push
Hello,
Under Twitter / Settings I've tried to enter my full name, Martin
Klein Schaarsberg, but I can only enter Martin Klein Schaars.
Is there a possibility to enter my full name or can the problem be
fixed? The character limit is quite low in my opinion. There are quite
a lot of people
On Aug 26, 2009, at 8:14 PM, Chad Etzel wrote:
Hi Jason,
The API endpoint and all other parameters sent with the request would
be helpful.
Thanks,
-Chad
On Wed, Aug 26, 2009 at 7:15 PM, Jason Martin
wrote:
Aright, here's one set of request/response headers:
Request:
{
Authorization
"Www-Authenticate" = "Basic realm='Twitter API'";
}
And the response body:
{"request":"/statuses/replies.json","error":"Invalid / used nonce"}
Lemme know if you need anything else.
- Jason
On Aug 26, 2009, at 6:05 PM, Chad
-Chad
On Wed, Aug 26, 2009 at 12:51 PM, Jason Martin
wrote:
I'm always getting the "Invalid / used nonce" error, even though I am
providing a new nonce. I am 100% sure my code works, because if I
remove my user cache, and the screen pops up to log into Twitter,
then
I imm
I'm always getting the "Invalid / used nonce" error, even though I am
providing a new nonce. I am 100% sure my code works, because if I
remove my user cache, and the screen pops up to log into Twitter, then
I immediately go to the user's timeline in my app, and everything
loads: followed t
ved the logs, I can't be sure.
It would be better if the failure rate for searches were lower. But
20% failure is not a big deal for me as the searches run as cron jobs,
which can always retry later.
/Martin
On Aug 23, 7:51 am, Andrew Badera wrote:
> 150 is a per-user rate, not a per
ion. How
>> would
>> you propose to distribute a usable FLOSS twitter app that uses Oauth
>> to authenticate itself but doesn't include the app's consumer key and
>> consumer secret? fetch the key and secret at runtime from a secure
>> server somewhere?
I don't feel that OAuth is a good solution for desktop applications.
If a user doesn't want the application to access their Twitter
account, why'd they download it in the first place? It seems very
redundant.
But the real problem is for mobile devices, especially for devices
that don't ha
Doug,
Thanks for letting us know about the new request limit. I was worried
something was wrong on my side. Like the others are saying; it would
have been nice with a heads-up.
Cheers,
/Martin
x27;t earn me a blacklisting :-)
Cheers,
/Martin
On Jul 15, 8:36 am, Bill Kocik wrote:
> On Jul 15, 11:22 am, iUpdateStatus wrote:
>
> > As a general question related to this topic: For all the developers
> > who are working on a solution that involves authenticated user
Hi again,
I just wanted to let everyone know that this problem does not occur
today. When I go over the API limit, I'm getting status code 403 back.
Yesterday I got status code 200 (OK) back, which made things hard.
This fix really helps us developers. Thank you, Twitters!
/Martin
On J
HTTP headers started with
HTTP/1.1 200 OK
In other words, this is the same problem I ran into yesterday. Is
there any other data that would help troubleshoot this?
All the best,
/Martin
On Jul 13, 5:52 pm, Doug Williams wrote:
> Martin,
> This sounds like issue 795 [1].
>
> When you
iMWI4MmQ3MDNmOWFhZjdiMD
hiYmI1%250AZTYzN2I1NjgwIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6%250ARmxh
c2hIYXNoewAGOgpAdXNlZHsAOhNwYXNzd29yZF90b2tlbiItMWQ1YmZl
%250AMTE5NmYwOTlhYjI2OGE
1NTRiNmMwYzJjOWQ1ZWQ5ODUzZg%253D
%253D--0bb9b2c1b8d9bee81c7aa35e9a91a6745df9a888;
domain=.twitter.com; path=/
Vary: Accept-Encoding
/Martin
On Jul 13, 7:48 pm
s update I just sent.
Should I examine the element to verify that the update worked,
instead of checking for HTTP error codes? Or was this just a temporary
glitch today?
All the best,
/Martin
e time the response contains an hourly-limit of
20,000, for my IP address I assume. But occasionally the exact same
curl command returns an hourly-limit of 150. Very odd. I assume curl
handles the credentials correctly.
Any thoughts?
/Martin
On Jul 13, 9:54 am, Justin wrote:
> Sorry about em
Best of luck to the Twitter Team with the jump forward.
Martin
www.wherecloud.com
On Jun 12, 5:52 pm, Doug Williams wrote:
> Just an update, there is a lot of coordination that it takes to pull
> something like this off. We need the operations team to watch the servers
> and applica
You are absolutely right. Forgot about daylight savings
So looks like around 5pm EDT.
Martin
On Jun 12, 4:28 pm, Chad Etzel wrote:
> On Fri, Jun 12, 2009 at 4:24 PM, Martin Dufort wrote:
>
> > I think this is delayed. And also 21:00 GMT is 16:00 Eastern and 13
> > Pacifi
I think this is delayed. And also 21:00 GMT is 16:00 Eastern and 13
Pacific.
Please let us know when the move forward in time will happen.
Martin - www.wherecloud.com
On Jun 12, 3:45 pm, Steven Degutis wrote:
> To clarify:
>
> This problem only affects applications who use a "
Matt: Are you going to intentionally bump the tweet unique id sequence
over the 2.1B mark ?
I think this is a very good move to this now instead on letting it go
by over the weekend.
Thanks - Martin
On Jun 12, 2:30 pm, Matt Sanford wrote:
> Hello again,
>
> The responses to @t
I'd be interested to see a document that details the standards for
this as well.
On May 15, 12:01 pm, leoboiko wrote:
> > On May 15, 2:03 pm, leoboiko wrote:
> > while one with 71 UTF-8
> > bytes might not (if they’re all non-GSM, say, ‘ç’ repeated 71 times).
>
> Sorry, that was a bad example:
And you can check on the progress of that Status ID on: www.twitpocalypse.com
Unless Twitter decides to blacklist us) for sending too many requests
to the public timeline API...
So Twitter, if you do so, please send me an email martin [insert at]
wherecloud [dot] com so we can work something out
a soft transactional layer to ensure
we get all the proper data for a user.
But if this is you final answer than we must go with that...
Martin - www.wherecloud.com
On May 11, 8:14 pm, Doug Williams wrote:
> David,
> As with any solution there are compromises (the normal big three ar
Doug,
I think using the same "URL" would work, but it might be nice to have
an extra (or different) param added in order to determine the reason.
For example, if a user revokes access from the web and Twitter
notifies the "URL", the app may just be updating values in a DB, not
displaying anythin
Alex - seems to still be an issue. Any updates on when we might see a
fix?
On Mar 30, 12:49 pm, Alex Payne wrote:
> We're on this. Thanks for the reports.
>
>
>
> On Sun, Mar 29, 2009 at 18:27, Gary Zhao wrote:
> > I'm seeing it too.
>
> > 2009/3/29 Günter Grodotzki
>
> >> since some days I am
I'm seeing inconsitent user attributes within the *same* request for
the *same* user. One result has full attributes disclosure, and the
other one has not.
I've updated Issue 409 with my results.
Martin
On Apr 2, 8:36 pm, Doug Williams wrote:
> Jeffery,
> This is valid criticis
Done. Registered as http://code.google.com/p/twitter-api/issues/detail?id=419.
Thanks - Martin
On Apr 3, 4:46 pm, Doug Williams wrote:
> Sounds like a bug. Can you file an issue [1]?
>
> http://code.google.com/p/twitter-api/issues/entry
>
> Doug Williams
> Twitter API Support
aren't we all on the same sinking ship then ;-)
On Apr 3, 4:13 pm, Abraham Williams <4bra...@gmail.com> wrote:
> If it helps motivate any as soon as this method is added I will be launching
> a revolutionary app. :)
>
> Abraham
>
>
>
>
>
> On Fri, A
Doug: This has been opened by Craig a number of months ago. Any ETA
for inclusion in the Twitter API ? Thanks - Martin
On Apr 3, 12:56 pm, Doug Williams wrote:
> Remy,
> A track already exists for this request [1].
>
> 1.http://code.google.com/p/twitter-api/issues/detail?id=
Doug: I've rechecked everything and it seems the problem was on my
side. Sorry for the false report - Martin
On Apr 2, 5:40 pm, Doug Williams wrote:
> Martin,
> I'm not seeing the problem with statuses/replies.json you are reporting. For
> which account are you missing data
I'm seeing the same thing on my side. In the JSON api, i'm even seeing
inconsistent behavior such as:
following = 0;
following = ;
with the same request. And people following me are somewtimes marked
as:
following = 0;
On Apr 3, 2:54 pm, Doug Williams wrote:
> I vaguely remember something, t
And is this available now via the JSON API interface because,
according to my tests, I do not see any "in the middle of a tweet
mentions" being reported by the API.
Thanks - Martin
On Mar 31, 1:33 pm, Joshua Perry wrote:
> This hasn't been said but I'm assuming this is on
73 matches
Mail list logo