[twitter-dev] Re: Where to send questions re: terms of service?
Brian, Taylor, Thanks very much for your quick responses. I'll send a message to the above once I can think it through more precisely -- or decide that what I was thinking of doing isn't needed after all. (FWIW, the issue is not so much a shouldn't but more of a gray area that I'm not sure the policy contemplated.) cheers and thanks again, Miles On Feb 9, 12:22 pm, Brian Sutorius bsutor...@twitter.com wrote: Hi Miles, I work on the API Policy team and monitor the messages at a...@twitter.com. We'd be happy to answer any questions you have about our policies or a specific feature you're thinking of. Brian Sutorius On Feb 9, 11:56 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Miles, While this public forum is great if you want to discuss the terms themselves with others, if you want to privately discuss API terms with Twitter, it's best to send a message to a...@twitter.com -- it might take a bit for you to get a response but the policy team will get your inquiry. That said, it's best to steer clear of anything explicitly prohibited in the terms and to follow the shoulds as closely as possible. Taylor @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Wed, Feb 9, 2011 at 11:39 AM, Miles Parker milespar...@gmail.com wrote: Hi, I've got a case where I'm not sure whether a potential use would conflict with terms of service. I'd rather not get into details on public forum ;) but I can if this is the only place for it. But I'm wondering if there is someone or somewhere to ask questions? i.e. re: If you are doing something prohibited by the Rules, talk to us about whether we should make a change or give you an exception. -- Who is us? thanks, Miles -- 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 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] Where to send questions re: terms of service?
Hi, I've got a case where I'm not sure whether a potential use would conflict with terms of service. I'd rather not get into details on public forum ;) but I can if this is the only place for it. But I'm wondering if there is someone or somewhere to ask questions? i.e. re: If you are doing something prohibited by the Rules, talk to us about whether we should make a change or give you an exception. -- Who is us? thanks, Miles -- 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] Show User API performance
I haven't been using the Search API for a while while I sorted out my Oath stuff. :) In the meantime, I think I've noticed a significant slow down in show user queries. Is anyone else seeing this or is it my imagination? thanks! -- 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] Social Graph Methods Page Size change?
I'm noticing now that page for friends and followers (for arbitrary user ids) are returning 100 users, not 5,000 as I'm seeing in the API docs. Is it my imagination that this has changed just in the last couple of days?
[twitter-dev] Friends and followers
This question is sort of pedantic, but I'm wondering why the API refers to friends instead of followers. The API say's that friends == following, but I understand (e.g. see this nice little article http://andrewchenblog.com/2009/03/16/friends-versus-followers-twitters-elegant-design-for-grouping-contacts/) that friends are mutual followers, that is: 1. I follow you (following)- 2. You follow me (follower) - 3. We follow each other (friends)- 4. Nada ø So would it be correct to substitute following for friends WRT to API? To keep it straight on my side, I'm going to have to come up with a word that means friends in the sense of 3 above.
[twitter-dev] Location finding practices
I've taken a look at recent posts on locations and geo-tagging. My read of all of this is that we can associate tweets with locations in ~3 ways.. 1. Geo-tags (user opt-in) 2. Location (user provided, pretty um.. low quality) 3. Some kind of behind the scenes magic that Twitter is doing For case 3, that means that when we specify geo-boxes we're getting something more than just 1. Is there anything available publicly about how this is done? i.e. is it parsing of User.location, some kind of IP thing, spy satellites..? ;) As someone posted a while back, it seems that we can get all tweets within a geo-box, but we can't get the inverse, i.e. an (approximate) lat lon for an arbitrary tweet. So suppose: Tg[] = all tweets within box g. Tg[k] = some tweet in that bounding box, *without* a geo-location U[l].tweets.contains(Tg[k]) From which I know that Tg[k] is in g. Now, is that based solely on info from U[l] or does it take into account anything about Tg[k]? And, is my understanding correct that if I discovered Tg[k] from somewhere outside of that location search, I *can't* determine g (unless of course it is geo-tagged or I do some kind of bone-headed exhaustive search..) ? Finally, has anyone else in API-consumer land come up with a good set of heuristics for determining location from the user.location alone? I mean, there are some obvious steps, but I don't want to re-invent the wheel and given the uncertainty about the data available (TeaPartyVille,USA, Beer City In Flavor Country (sounds like a nice place to visit)) I'm not certain it's worth it. Are people having pretty good results about just parsing place names? Code? :) And of course, does anyone want to tell us/speculate about what TrendsMaps is doing here? My assumption is that they are just doing searches based on the twitter geo-boxing, but perhaps there is more magic here that might be sharable. enquiring minds... Miles
[twitter-dev] Re: Friends and followers
On May 25, 8:05 pm, John Kalucki j...@twitter.com wrote: It's not always possible to evolve the API at the same pace. Of course..not moaning, just curious. I wouldn't say that mutual followers are friends. They're just mutual followers. Yes, I guess that's a matter of semantic interpretation. :D Personally I find the whole friending thing a bit obnoxious and I'm quite happy to see that the term hasn't been asopted for the web UI.
[twitter-dev] Invalid XML 0x14
Hi all, When trying to persist a stream I'm getting an invalid Unicode char 0x14, which is DEVICE CONTROL FOUR. Takes me back to my childhood, when there was probably some TTY or LPT out there that that meant something to, lol. But it's just appearing in an normal element content. Unfortunately, its giving my XML serializer fits. Is it possible that stray control chars will just appear like this and I need to handle them gracefully by pre-filtering them or pimping my serializer or is this actually something that shouldn't be showing up in the stream at all? thanks, Miles
[twitter-dev] Re: Searching date limitations
Thanks Taylor! Can you say anything about wether you actually persist them anywhere? I mean it would be an enormous challenge to actually allow those to be queried interactively online. But if you do have the data somewhere an intermediate step might be to allow batch requests for large data sets which are then provisioned for download say at off peak times. Though I just realized, you prob. don't have an off-peak time! On May 14, 8:20 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Miles, You're right in that we don't go back very far with search right now. We want to improve that. There's no timeline right now, but it's certainly something we're looking at. There are so many tweets. We want you to have them all. Some day. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Thu, May 13, 2010 at 6:34 PM, Miles Parker milespar...@gmail.com wrote: This is one of those questions where I'm pretty sure I know the answer, but I'd really like to be wrong. :) There doesn't seem to be anyway to get tweets past ~7 days. Which sort of makes me wonder what the point of the since and until params are -- for the usages where only being able to search back 7 days makes sense, it seems like you'd want more granularity. So my deeper question is whether this is simply a matter of not being able to *store* all of the data (seems highly unlikely) or just not being able to adequately *serve* that data through an open http interface? It would be really nice for research purposes to be able to have access to that data...
[twitter-dev] Searching date limitations
This is one of those questions where I'm pretty sure I know the answer, but I'd really like to be wrong. :) There doesn't seem to be anyway to get tweets past ~7 days. Which sort of makes me wonder what the point of the since and until params are -- for the usages where only being able to search back 7 days makes sense, it seems like you'd want more granularity. So my deeper question is whether this is simply a matter of not being able to *store* all of the data (seems highly unlikely) or just not being able to adequately *serve* that data through an open http interface? It would be really nice for research purposes to be able to have access to that data...
