Is there a way to see the demographics (age, sex, location) of a
user's followers with the twitter api? Any information would be
greatly appreciated.
Thanks
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Hey Jason,
We'd love to help you guys host a #devnest out here in Charlotte, NC
if you ever swing by our way.
Regards,
Corey
On Apr 27, 6:50 pm, Jason Costa jasonco...@twitter.com wrote:
Hi everyone,
On May 12th from 6:30pm to 8:30pm, we're going to be
hosting a developer event, Twitter
I hope one of the cities outside the U.S will be Toronto, there is a lot of
twitter development happening down here. If you want to do a #devnest in
Toronto please let me know, I would love to be a part of it and help in
anyway possible.
On Thu, Apr 28, 2011 at 7:45 AM, Corey Ballou
I'll second that, Corey!
Nick
On 4/28/2011 7:45 AM, Corey Ballou wrote:
Hey Jason,
We'd love to help you guys host a #devnest out here in Charlotte, NC
if you ever swing by our way.
Regards,
Corey
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API
Dear Sir or Madam,
I am programming for Number 10 iphone application.Currently,this
application has xAuth access and can post information via twitter.
However, when I try to call [twitterEngine
enableUpdatesFor:@follower] for adding a follower. it will return a
401 error.
here is my code:
-
Hi there,
You may be able to determine the user's location by their profile location
field, but it's not a reliable source of information since it is free-form
and potentially inscrutable, fictional, hilarious, and sometimes parseable.
Some users geotag individual tweets with more reliable
Well, it's definitely possible with JavaScript and even as a Web
Application, but only in one of these cases :
* User marks the web application as trusted, to avoid cross-domain
restrictions
* Twitter implements Mozilla's cross-domain XHR method
* From a file:// location or another location
You cannot perform secure OAuth 1.0A in client side Javascript. It is
insecure, unsupported, and entirely unrecommended.
Unless you want to develop a server-side based Twitter API integration, you
may want to look at Web Intents ( http://dev.twitter.com/pages/intents ) or
@Anywhere instead (
Thanks Taylor for the answer.
I guess it's very insecure beacuse all the person can see the
javascript code including the keys. ¿It is that the case?
I have read part of the documentation of twitter or OAUTH, but i
haven't seen a clue of that we can't use javascript for
authentications. In fact i
Thanks Tom
Yes, i read that part in the API that the consumer must do his best to
hide all posible form of reveal the codes.
Thats is my second achievement, the first is try to get this work
¿so can you help me? (more) .
I doesn't undesstand whyi can see the answer using a form, and why i
I have Site Streams implemented for a number of twitter accounts on my
testbed system. It is working like a charm, and for this system at
least, the home timeline, mentions and messages are all super fast
(obviously). It saves API calls, it is nice, I am pretty happy.
I wonder: What other data
Twitter, are you aware that your API is throwing 502s left right and
center on blocks/create/nnn.json and report_spam.json?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
Hey Dewald,
There is an issue filed on the public issue tracker for this but as reported
in the ticket, this seems to work sometimes and not at others:
http://code.google.com/p/twitter-api/issues/detail?id=2156
To help us track this down, an iIf you are happy to, can you paste some
I was surprised to see a newly formatted oAuth Authenticate Page. The
new page doesn't account for the scores of oAuth implementations that
popup a new window.
There is an ad-hoc standard for the window height and width that makes
for a decent user experience. The new format will cause issues
Hey Developers,
Some of you may have noticed already that earlier today we deployed a
redesign of the OAuth screens.
We know both you and your users have been asking for better clarity about
what an application can see and do with an account and these screens are a
step towards doing that.
One
Thanks guys - we're still in the early stages of
planning right now, but definitely appreciate the
feedback and enthusiasm. Stay tuned!
On Apr 28, 5:05 am, Nicholas Chase nch...@earthlink.net wrote:
I'll second that, Corey!
Nick
On 4/28/2011 7:45 AM, Corey Ballou wrote:
Hey Jason,
Hi Matt,
This is a big change and it negatively impacts many web applications
that popup a browser window to display the oAuth screen. The popup
windows were sized for the old content, and the new content will force
the user to scroll. It's not a great experience.
I wish there would have been
Here is a screenshoot of the new page.
https://picasaweb.google.com/4braham/Screenshots#5600743120809142002
Note that app descriptions are now shown to users incase you were lazy (like
me) and didn't include a real description.
Abraham
-
Abraham Williams | InboxQ http://inboxq.com/
I think it's good to be giving users more information on what they are
granting access to, but by leaving out a number of things there are
misleading implications. In particular, this list does not mention
that users will be granting access to all their private DMs. I also
find it interesting the
@Shannon: thanks for the feedback on this. The new screens are fluid in size
so wrap to the available space. Hosting in a local iframe isn't something
we've encouraged in the past. We prefer the user to be taken to the
authenticate or authorize page in a tab/new window that they can see the URL
Maybe I'm just getting old, but I can't seem to find the link for my
account's RSS feed on #newtwitter. Did it go away? Is that feed
deprecated? It's right where it always was on the old Twitter. ;-)
--
http://twitter.com/znmeb http://borasky-research.net
A mathematician is a device for turning
Matt,
Thanks for the reply. I'm referring to a popup browser window that
displays the full url. The technique is not designed to mask the
oAuth process, it's designed to improve the experience for the user.
Devs have been using this technique since Twitter released oAuth.
The popup allows the
Hey Edward,
You're not getting old :) We removed the RSS link on #newtwitter, but the
exact same content is available through /1/statuses/user_timeline.rss
For example:
http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=rno
Arnaud / @rno http://twitter.com/rno
On Thu, Apr 28,
hI ...
I am trying to map the tweets which I can retrive using Twitter Search
API.
This is what I have observed.
When I search for tweets based on location(lat n long) using the
query:
search.twitter.com/search.atom?geocode=37.781157,-122.398720,1mi
I see that (in the xml format) there is
hI ...
I am trying to map the tweets which I can retrive using Twitter Search
API.
This is what I have observed.
When I search for tweets based on location(lat n long) using the
query:
search.twitter.com/search.atom?geocode=37.781157,-122.398720,1mi
I see that (in the xml format) there is
25 matches
Mail list logo
