Is it possible with the current search api to search for multiple
hashtags? I'm looking to do an OR search which will look for up to 3
hashtags.
Is it just me or is the rpp call not being processed correctly? Here
is a link from the api documentation:
http://search.twitter.com/search.atom?q=+the+%23sxsw&rpp=10
>
> -chad
>
> On Sun, Apr 5, 2009 at 2:36 PM, Matt wrote:
>
> > Is it possible with the current search api to search for multiple
> > hashtags? I'm looking to do an OR search which will look for up to 3
> > hashtags.
Hello all,
My app has quickly outgrown the basic functionality of the search API.
I am searching for a few specific hash tags along with some keywords
to pull out a niche group of tweets. This results in about a 35%
return of non-related tweets that are cluttering up my results. I am
not looking
ant use of twitter data.
On Apr 7, 11:37 am, Doug Williams wrote:
> Matt,
> You can easily combine steps 3 and 4 by using the tweet's status_id as the
> primary key in the table you are using to store the updates. Any duplicates
> will be implicitly rejected by the database upon inse
I know as of right now the search API does not return any user
location information but I am just wondering exactly how some apps
manage to gather this info. I'm looking specifically at
http://micro.ilist.com/.
It looks like this app simply tracks hash tags and I would assume they
are caching th
hering location data, although it
hasn't been implemented into the search yet.
http://www.twitshop.com
On Apr 7, 11:37 am, Doug Williams wrote:
> Matt,
> You can easily combine steps 3 and 4 by using the tweet's status_id as the
> primary key in the table you are using to store
)
>
> On May 1, 4:58 pm, Matt Sanford wrote:
>
> > Hi there,
>
> > Nope, sorry to say we do not support wild cards. We've discussed
> > it in the past internally but there is no good way to make it work
> > fast enough to be useful based on our c
Is it possible to get a user's actual time including daylight savings?
Matt
ing their time zone.
>
> On Sun, Aug 2, 2009 at 17:43, Matt wrote:
>
> > Is it possible to get a user's actual time including daylight savings?
>
> > Matt
>
> --
> Internets. Serious business.
call we
are making, which may or may not be picking up all geotagged tweets
based on our keywords.
Thanks,
Matt.
Are you aware of whether or not this feature will be returning, as it
seems the API has been "turned off" as well, which means this has been
done on purpose?
On Dec 3, 7:07 pm, Abraham Williams <4bra...@gmail.com> wrote:
> The retweet features were turned off a few hours ago.
>
> Abraham
>
> Abrah
I haven't, but you have a space in the link you posed as the thread
title.
On Dec 3, 5:13 pm, dhaval wrote:
> Hey all
>
> Updating profile background image doesnt work for me. Is any one else
> facing the same issue?
>
> Let me know
>
> thanks
I have the same code in two places (Dev and Production). On my dev
server, I am able to use OAuth with no issues. On my Production
server, I get 401 unauthorized every time I make a request.
I tried regenerating my keys, I back tracked through every line of
code to figure out if it was me. As f
Can anyone help me figure out how to get data back from this and what
I'm doing wrong?
Incidentally, that dev console is maddeningly frustrating to use since
it immediately forgets the entered parameters as soon as you submit a
query. Couldn't it submit via ajax, too?
thanks,
Matt
--
Twitter
Hi there,
It doesn't sound like the search API rate limiting, as that returns
a different response code (503) along with an error message. What URL
are you using when you get the 400?
Thanks;
— Matt Sanford
On Oct 26, 11:29 am, wcrtr <[EMAIL PROTECTED]> wrote:
> Just doi
ses are very long URLs or
unescaped spaces in the URL itself. Can you please run curl with a -v
and send along the output of the problem request? If nothing else this
will give me a full trace to work from.
Thanks
— Matt Sanford
On Oct 27, 9:48 am, wcrtr <[EMAIL PROTECTED]> wrote:
> using
If the follow button is created in an iFrame on a foreign domain, the
button will not render in Firefox due to a XSS permissions error.
Consider this:
Page: abc.com/index.html
[
iframe: xyz.com/iframe.html
[
{Follow button}
]
]
Firefox will throw a "Permission denied to call Locat
We've just implemented @anywhere's hovercard feature on our website
and noticed that in addition to the initial loading of jQuery from
Google which we were already doing, by including the Twitter script it
loads jQuery 2 or 3 more times from Google. This should be fixed to
only load jQuery once if
Can confirm this is happening to me too, for this request:
http://search.twitter.com/search.json?&q=from%3Atfr%20OR%20from%3ASOIANYC&rpp=5&callback=jQuery16106527990615355083_1308086280457&_=1308086281400
(I'm fetching tweets from two users - "tfr" and "SOIANYC" - if I
remove SOIANYC from the que
Simple - Access to read/write direct messages, and just have a HIG rule
(maybe) about what they're doing below the login box.
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https:
Hi Ricardo,
This is listed as a feature request on our issue list (http://code.google.com/p/twitter-api/issues/detail?id=242
). If this is something you want to see I suggest you add a star to
that issue.
Thanks;
— Matt Sanford
On Feb 21, 2009, at 11:16 AM, Ricardo Sousa wrote
minutes you're
building something unscalable and you can expect to hit the rate
limit. Not that I'm sure this is what people have in mind but I
thought I'd put this out there ahead of time just in case.
— Matt
On Feb 22, 2009, at 02:17 AM, Karthik Murugan wrote:
No, they show
Hi there,
I added this info to the ticket.
Thanks;
— Matt
On Feb 23, 2009, at 06:21 AM, Karthik wrote:
Can you accept the request for the colon character too? I may use the
prefix $IN for Indian stocks and would like to retrieve only the
updates containing the term $IN:REL for example
Hi Emmanuel,
Since we improved the error messaging a bit that error message
now leads to something useful. When we tried to lookup your token it
was not found. Was this right after you exchanged the request token
for an access token, or had some time passed?
Thanks;
— Matt
On Feb
quests and
not others because you don't hit the same database every time. Like I
said, working on a fix for it now. Once the fix is done I'll keep and
eye out for more reports like this.
Thanks;
— Matt
On Feb 21, 2009, at 02:47 PM, Santosh Panda wrote:
Hi Paul,
We see the
an
of an access token is detailed at http://apiwiki.twitter.com/OAuth-FAQ.
Thanks;
— Matt Sanford
On Feb 23, 2009, at 09:49 AM, Abraham Williams wrote:
How long does it take for a request token to expire?
On Mon, Feb 23, 2009 at 11:29, Matt Sanford wrote:
Hi Emmanuel,
Since we improved
Hi there,
I looked into this a bit and it looks like non-admins are not
seeing the field. Hoping I can make Google Code play ball, otherwise
I'll keep doing the triage comments.
— Matt
On Feb 23, 2009, at 12:17 PM, Chad Etzel wrote:
On Mon, Feb 23, 2009 at 3:13 PM, Alex
I usually lack any whale humor, but here goes:
v vv
| | v | v
| .-, | | |
.--./ / | _.---.|
'-. (__..-" \
\ a|
',.__. ,__.-'/
'--/_.''`
T H EW H A L E
S L E E P S
T O N I G H T
On Feb 23,
Hi all,
Looks like someone opened a Google Code issue (http://code.google.com/p/twitter-api/issues/detail?id=312
). We'll look into it.
Thanks;
— Matt Sanford
On Feb 24, 2009, at 07:29 AM, Burhan TANWEER wrote:
Yes, I have tried this url as XML vs JSON. It shows false in XML
o
Hi Rainer,
Sounds like a bug. Open an issue at http://code.google.com/p/twitter-api/issues/list
and we'll take a look.
Thanks;
— Matt Sanford
On Feb 24, 2009, at 03:43 AM, Rainer Müller wrote:
Hi,
I am experimenting with the new API and I stumbled upon a problem.
Why do I ha
Hi there,
This is behind a few other projects and I don't know the ETA for
it.
Thanks;
— Matt
On Feb 24, 2009, at 08:39 AM, Karthik wrote:
Hi Matt,
We are building an App which heavily depends on this new feature. Can
you please let me know a tentative date for its release?
ling
you so.
Thanks;
— Matt
On Feb 24, 2009, at 10:59 AM, Karthik wrote:
Please confirm, if the following is allowed?
1. Set rpp=100 and retrieve 15 pages search results by incrementing
the param 'page'
2. Get the id of the last status on page 15 and set that as the max_id
for
Hi there,
I believe both following and notifications are incorrectly
returned due to the same cacheing bug (http://code.google.com/p/twitter-api/issues/detail?id=157
). I have been working on this off and on for quite some time and hope
to get it resolved soon.
Thanks;
— Matt
and notification values of the person who triggered the
cache population, not themselves. I'm not totally sure it's the cause
but it seems the most likely. I just cleared the cache for your two
example users, did that change things at all?
Thanks;
— Matt Sanford
On Feb 24, 2009
): Changed OAuth tokens to work correctly during
database replication delays.
* Feature (OAuth): Removed the approval process for new
applications. New applications will be allowed by default and we will
review and revoke as needed.
Thanks;
— Matt Sanford
Hi there,
I see this for both XML and JSON. Looking into it now. If I wait
a few moment (10 seconds or so) it works correctly, which points me
toward the correct cache. I'll let you know when I find something.
Thanks;
— Matt Sanford
On Feb 25, 2009, at 05:39 AM, Dimebrain
Hi Chad,
This anchor is how search gets the data from Twitter so we keep
it consistent and pass it along that way. For the next version of the
API we have an outstanding request to break these two apart (See http://code.google.com/p/twitter-api/issues/detail?id=75)
.
Thanks;
— Matt
Hi there,
I found the source of the issue and have a fix ready. The issues
is a 1 minute cache elsewhere in the system. I'm awaiting a code
review now and hope to make it in time for today's deploy to fix it.
Thanks;
— Matt Sanford
On Feb 25, 2009, at 05:39 AM, Dimebrain w
etail?id=307)
Thanks;
— Matt Sanford
Hi there,
It seems GMail has been eating some of my outgoing mail today so
you may not have seen my last reply. This has been fixed.
— Matt
On Feb 25, 2009, at 05:39 AM, Dimebrain wrote:
I think there's some erroneous caching occurring with these optional
parameter
Hi Samunai,
You can have people follow you on Twitter and the follow them
back. Once you have that you'll have an easy we to collect this
information via direct messages. I suggest signing up for and account
at Dopplr (dopplr.com) to see how they have done it.
— Matt
On Feb 26,
Hi Nick,
The since_id parameter hasn't changed as far as I know. When you
request anything from the friends timeline we return 20 statuses by
default. Perhaps you should add a count=50 parameter as see if that
does what you expect.
Thanks;
— Matt Sanford
On Feb 28, 2009, at
Hi there,
I'm sorry, but no total result count is available.
Thanks;
— Matt Sanford
On Feb 28, 2009, at 05:56 AM, Gilles Frydman wrote:
Is there any simple way to return, via an API call, the total # of
hits for a hashtag search?
--
G. Frydman
Hi Kevin,
The permission difference is a known issue (http://code.google.com/p/twitter-api/issues/detail?id=268
) that we plan to correct. I suggest putting a star on that issue so
you get email updates when there are changes.
Thanks;
— Matt Sanford
On Mar 1, 2009, at 05:09 AM, Kevin
Hi Daniel,
Please open an issue at http://code.google.com/p/twitter-api/issues/list
and we'll take a look.
Thanks;
— Matt
On Mar 1, 2009, at 07:30 AM, Daniel Morales wrote:
Hi there.
I got this when i request Public Timeline:
Public Timeline:
"id":"1265475
/p/twitter-api/issues/detail?id=315
). I have a fix ready and am hoping to get it deployed today.
Thanks;
— Matt Sanford
On Mar 1, 2009, at 09:59 PM, TjL wrote:
On Sun, Mar 1, 2009 at 9:15 PM, Scott C. Lemon
wrote:
What is the current maximum size of the location field? I've l
Hi all,
This migration is something we've been discussing internally.
We're not sure yet what we want to do about it but I'll keep people
posted. Remember, we'll be running things in parallel for a while so
there is some time to figure these things out.
Don'
Hi Paul,
It sounds like whatever is generating your API requests is double
URL encoding. So the space becomes %20, and then on the second url
encoding the % becomes a %25.
Thanks;
— Matt Sanford / @mzsanford
On Mar 3, 2009, at 07:34 AM, Paul Kinlan wrote:
Hi,
I am noticing
ing it %25
in the request but displaying it correctly to you. Try replacing it
with a + or a space and see what you get.
Thanks;
— Matt
On Mar 3, 2009, at 08:06 AM, Paul Kinlan wrote:
Forgot to add, I am checking our client library now too.
Paul.
2009/3/3 Paul Kinlan
Hi Matt,
I was
Hi all,
If you send something invalid we do attempt to fix-up invalid
requests rather than just 400. This looks like a case where the bad
request becomes a different sort of badness on the way out. Escaping
the quotes seems like the only real fix.
— Matt
On Mar 3, 2009, at 09:13 AM
Hi Steve,
There definitely seems to be a bug there. Please open an issue at http://code.google.com/p/twitter-api/issues/entry
and I'll take a look. I see you update issue #80 but please open a
new one since this seem unrelated and I don't want to forget about it.
— Matt
On M
searching for 'recipe' will also find '#recipe'
if they don't know about hashtags.
— Matt
On Mar 3, 2009, at 01:35 PM, Chris wrote:
Hi guys,
When I search for "recipe #food" - I was expecting to see tweets that
are tagged with #food, and also contain the tex
Hi Chad,
The search.twitter.com query parser does not support grouping
like this. We've talked about it a few times internally but it's
pretty difficult and never seems to have a high enough priority. Go
ahead and open a Google Code issue on it so I don't forget.
T
chines, so it
may take a little bit before you see the changes take effect.
Thanks;
— Matt Sanford
Hi all,
This is related to the login error (http://status.twitter.com/post/83602310/problems-logging-in
) and people are working on it.
Thanks;
— Matt Sanford
On Mar 4, 2009, at 03:32 PM, dean.j.robinson wrote:
For example:
https://twitter.com/oauth/authorize?oauth_token
Hi there,
That looks like a bug, please open a Google Code issue (http://code.google.com/p/twitter-api/issues/entry
) and we'll take a look.
— Matt
On Mar 6, 2009, at 01:05 AM, TjL wrote:
is 'count' not working for friends timeline if you use XML?
I r
Hi Kevin,
The most likely cause if that you have multiple widgets, all with
very low refresh rates. Since the rate limiting is per-IP that can add
up to be enough to rate limit.
Thanks;
— Matt Sanford
On Mar 6, 2009, at 05:52 AM, Kevin D wrote:
I have also been getting the &quo
d that OAuth is confusing
enough without moving choices onto the user. We also worked on a way
for users to change the access type of a token but in the end every UI
was confusing. Re-approval allows your app to handle the state change
rather than sendinf them to the connections tab with instruc
s in the
next version of the API.
Thanks;
— Matt Sanford
On Mar 6, 2009, at 08:25 AM, TjL wrote:
On Fri, Mar 6, 2009 at 11:11 AM, Doug Williams
wrote:
In your experience, do trending bots have a disproportionate
participation in the search results for trending topics? Have you
done
an
I deployed a batch of explicit length checks this week to try and stop
that madness. I didn't do the same for status text because it has
another validation routine altogether. The Service Team should be able
to help out with in making that more sane.
— Matt
On Mar 6, 2009, at 11:
some information inline …
On Mar 6, 2009, at 01:25 PM, Scott C. Lemon wrote:
I'm working on our site - http://www.TopFollowFriday.com - and am
currently using the search API to search for the #followfriday
hashtag. All is well, and it's working ... except ...
The search feed only returns the
m
busy trying to collect that to see when we can finish this closed
beta. When I know, you'll know.
— Matt
On Mar 6, 2009, at 02:10 PM, dmoney wrote:
Any timeline on WHEN the beta will open up to others? We'd like to
build some twitter functionality into our app, but I'd
d, compromising user privacy, users will
blame every app and twitter. This is a Bad Thing™
I don't think any of this is news to anyone, but it's useful to
keep in mind when suggesting we keep BasicAuth.
Thanks;
— Matt Sanford
On Mar 10, 2009, at 07:55 AM, TjL wrote:
On Tue, Mar
Hi Ronnie,
Did the output contain any sort of warning message? When the
max_id is too old we have to adjust it and the output will contain a
warning saying as much.
Thanks;
— Matt Sanford
On Mar 11, 2009, at 02:34 AM, ronin wrote:
Hi Doug,
I tried the approach that Karthik
r memory space
being taken up by old data that a very small percentage of requests
need.
Thanks;
— Matt
On Mar 11, 2009, at 09:11 AM, Ronnie wrote:
Hey Matt,
Nish is right, I don't see a warning message that the max_id that
max_id is adjusted unless since_id is not specified
I think it does if you use: @user -to:user
On Mar 11, 2009, at 09:42 AM, Jeff Bishop wrote:
Right, but using the Search API doesn't provide a way of filtering
out those already processed by the Twitter Replies API. See what I
mean?
Jeff
- Original Message -
From: Doug Williams
To
Hi there,
The show_user=true was only ever intended to work with atom feeds
due to some feed readers not displaying the author. If you need this
to work via JSON please file a ticket at http://code.google.com/p/twitter-api/issues/entry
Thanks;
— Matt Sanford
On Mar 11, 2009, at 02
owing/
notifications are either missing or incorrect. Alex is also working on
some code (http://twitter.com/al3x/status/1313993905) that will clean
up even more issues. Hopefully that will fix these issues in the
process.
Thanks;
— Matt Sanford
On Mar 11, 2009, at 10:18 PM, dacort wrote:
I'll
.
I'll check with the person who added that restriction and see if it's
something we can remove without causing massive HTP 500s (which is
what you get when a query takes too long and we mark it as timed out).
Thanks;
— Matt Sanford
On Mar 12, 2009, at 05:18 AM, Stefan Hueg wrote:
H
here r off list and I can look into it.
Thanks;
— Matt Sanford
On Mar 12, 2009, at 08:18 AM, Stefan Hueg wrote:
It seems that the "filter:links" method uses a cached version, using a
predefined threshold for how frequently a user is posting
his tweets. It's not affected by
Hi all,
It looks like the max length of a hashtag in search is 16
characters. I'll make a not to add it to the documentation.
Thanks;
— Matt
On Mar 15, 2009, at 02:19 AM, jeffsonstein wrote:
same happens for me: #greybitchqueencat returns 0 while
greybitchqueencat returns
hanks;
— Matt
On Mar 15, 2009, at 05:41 PM, Abraham Williams wrote:
http://code.google.com/p/twitter-api/issues/detail?id=152
On Sun, Mar 15, 2009 at 17:42, Chris Westbrook
wrote:
OK, thats what I thought. It seems pretty fundamental so I thought
maybe I was missing something. Hopefully tw
Hi Chad,
Back-in-the-day at summize.com it seemed like most where <8
characters so we doubled it and figured all was well. Changing the
data size is a pain but if people feel it's important please open an
issue and start marking it with stars.
Thanks;
— Matt Sanford
O
Hi Allen,
This is the same cache bug that is effecting friendships (http://code.google.com/p/twitter-api/issues/detail?id=157
). I have a fix and it's awaiting review.
Thanks;
— Matt Sanford
On Mar 16, 2009, at 10:59 AM, Allen wrote:
I'm having the same issue.
This is probably exacerbated by http://status.twitter.com/post/86986973/some-delays-on-followings-direct-messages
(referenced here also: http://twitter.com/twitterapi/status/1337508172)
.
— Matt
On Mar 16, 2009, at 11:38 AM, blairblends wrote:
I hate to sound like a broken record, but
Hi all,
I think this is a side-effect of the replication lag issues we've
been having all day. We're working on it but you may seem these kinds
of oddities until we do.
Thanks;
— Matt
On Mar 16, 2009, at 08:57 PM, Joshua Perry wrote:
Well, maybe it is a caching issue,
overwhelming response to the open beta … I have an inbox *full* of
people saying the updates are not taking effect. Hold tight, they
should appear within a few hours.
Thanks;
— Matt Sanford
ct. Hold tight, they should appear within a few hours.
Thanks;
— Matt Sanford
We're working on that now.
— Matt
On Mar 17, 2009, at 04:55 PM, Shannon Whitley wrote:
Push worked. The authorization page looks good in IE.
I'm still getting valid tokens for "andiojeda" if I leave the username
and password fields blank and click 'Allow&#
pup flow
from Brooks and that seems like a much better choice.
Thanks;
— Matt
On Mar 20, 2009, at 08:24 PM, Scott Carter wrote:
For the case where the user is already logged in, there doesn't appear
to be any risk here.
Hi Justin,
Any sort of automated following runs a risk of having users
suspended as suspected spammers [1]. My suggestion would be to
approach the lack of groups in some other way.
Thanks;
— Matt Sanford
[1] - http://help.twitter.com/forums/26257/entries/18311
On Mar 23, 2009, at
Responses inline:
On Mar 24, 2009, at 09:13 PM, Basha Shaik wrote:
Hi,
Please answer below questions:
1. If in any case if my IP is blocked What should i do?
How can i request twitter api to unblock it.
We don't do many while-sale blocks, but if you cannot reach
twitter.com at all check ou
ve a clear
picture of what needs to be done. All of these seem like good
suggestions so I'll put them on the list. If you have specific
suggestions send them to me off-list and I'll include them.
Thanks;
— Matt Sanford
P.S. I believe this is the first time I have ever seen "desig
A few comments inline:
On Mar 26, 2009, at 02:03 PM, John Mazz wrote:
Hi.
I'm working on a twitter based webapp that would use
search.twitter.com/search a lot and I was wondering about search
quantity limitations, both hard coded and also just friendly limits.
First, I'm assuming that runnin
=374
As always, you can keep up with these changes at http://bit.ly/api_changelog
.
Thanks;
— Matt Sanford / @mzsanford
databases and still return you the correct results. The fix for this
bug is a long time coming because we wanted to be sure it would fix
the issue, perform well, and be resistant to breaking again in the
future. Sorry for the long delay.
Thanks;
— Matt Sanford
[1] - http://code.google.com/p
more, so don't everyone reply at once about what's not on there ;).
Since this isn't the highest priority change being discussed I wanted
to get a minimal version out so people could use it while we talk it
over.
Thanks;
Matt Sanford / @mzsanford
On Feb 26, 2009, at 02:4
around but I can't say I'll be holding my breath.
Thanks;
— Matt Sanford / @mzsanford
On Mar 26, 2009, at 09:12 PM, Julio Biason wrote:
Hi there,
I just found a problem with rate limit count. A few days ago, my app
(Mitter) started getting weird "always 100 remaining request
Hi Chad,
Correct. This was just for sites that have a Web UI, want to
suggest people to follow, and don't want to collect passwords just for
that one action. Things like wefollow.com (though they didn't ask for
it) are a prime example.
Thanks;
— Matt
On Mar 27, 2009, a
Hi there,
Is your application registered as read-only by chance? If it is
POSTs will fail but the message should be a little more descriptive.
Thanks;
— Matt
On Mar 26, 2009, at 11:34 AM, Baishampayan Ghose wrote:
I'm having a little trouble with oAuth - I'm getting
ose at the
moment. Just started work on it so the details are scarce. I'll let
you know when I know more.
Thanks;
— Matt Sanford / @mzsanford
On Mar 27, 2009, at 09:39 AM, Abraham Williams wrote:
2 options:
1) Roll your own authentication or use something like OpenID,
Facbook Connec
days fighting it. I know it
sounds bad, but better to be honest with you folks … we're all friends
here.
Thanks;
— Matt
On Mar 24, 2009, at 10:28 AM, Chad Etzel wrote:
I have been encountering this scenario lately (especially with testing
OAuth apps with test accounts).
Say I am l
t it, those that are close (desktop
apps) try it, and those that are totally outside of it hang tight. We
need some desktop and mobile apps to try it so we can find out what
works. Everybody knows it's hard, but if you've used desktop apps with
the Flickr API you know it can be don
Hi Paul,
In a reply to a previous thread today I mentioned we're working
on making that login scenario easier. I am working on it as we speak
(or, type, rather).
Thanks;
— Matt
On Mar 27, 2009, at 02:32 PM, Paul Kinlan wrote:
Hi matt,
I generally like the idea and implement
Hi there,
I don't know CF, but it looks like you're passing username and
password as form fields. You need to use HTTP Basic authentication and
only pass in status as a parameter.
Thanks;
— Matt Sanford / @mzsanford
On Mar 29, 2009, at 11:32 AM, Craig328 wrote:
I'
Hi all,
I think I mentioned it the end of last week, but perhaps not.
I'm working on the mobile pages since it was one of the beta-isms
surrounding OAuth. There is no ETA yet but it's being worked on.
Thanks;
— Matt Sanford
On Mar 30, 2009, at 04:51 AM, dean.j.robi
Hi Leo,
The update method should take a source parameter, but you have to
register one first. Check out http://apiwiki.twitter.com/FAQ#INeedSomething
Thanks;
— Matt Sanford / @mzsanford
On Mar 30, 2009, at 08:04 AM, leo wrote:
I am working on a wpf twitter client that talks to the
This is a known issue [1] and we're working on it right now.
Thanks;
— Matt Sanford
[1] - http://code.google.com/p/twitter-api/issues/detail?id=399
On Mar 30, 2009, at 01:02 PM, Abava wrote:
request messages with since_id attribute returns old messages:
request new messages
Actually, that 'follow' button it a great clickjacking target, unless
you already follow @britneyspears … which is cool. I'm not here to
judge.
:)
— Matt
On Mar 30, 2009, at 02:52 PM, Ryan wrote:
clickjacking does not really affect pages like http://twitter.co
1 - 100 of 1107 matches
Mail list logo
