[twitter-dev] Site Stream - users per stream?
I'm in the early stages of a project using site streams. The docs say there is a limit on the follow count of 100 users per stream. Is that still the case? Is that apt to change any time soon? Just curious, Charles. -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] Re: statuses/show rate limiting clarification
Jean, Unless this graphic of a grassy knoll somehow has something to do with rate limiting, you appear to be a Robot. I'm drawing that also from looking at your other posts on the board. On May 25, 5:32 am, JEAN HALL jeanhall...@btinternet.com wrote: From: Charles ch...@evri.com To: Twitter Development Talk twitter-development-talk@googlegroups.com Sent: Wednesday, 25 May, 2011 1:34:34 Subject: [twitter-dev] statuses/show rate limiting clarification Hi, Going through the docs on statuses/show (http://dev.twitter.com/doc/ get/statuses/show/:id) we find ourselves going around in circles with a particular issue, and were wondering if someone could help us out. Specifically we're confused about what authentication does and does not allow us to do vis-a-vis rate limiting (as authentication is not required to make this call). I realize that's kind of a jargony sentence, so here's a completely fictional example, the answer to which should answer our question: Say we have N authenticated users using our application, and that we have been archiving statuses by ID (and only ID) coming through their public timelines for some arbitrarily long period of time, such that we have stored thousands of status ID's per user. Now, we'd like to provide a feature allowing our users to recall various of these statuses, and since we've only been storing them by ID, we'll be using the statuses/show method to do this. The rate-limiting doc (http:// dev.twitter.com/pages/rate-limiting) specifies that no more than 150 anonymous requests, or 350 requests via OAuth can be made per hour. However, the statuses/show documentation explains that authentication is not required. Assuming we weren't doing any cacheing, what is the maximum number of requests our application could make to the statuses/ show method, and how does it scale? Specifically, could we make: * 150 requests / hour (because authentication is not required, might all calls count as being anonymous) * 350 requests / hour (from the authenticated account that administers our application) * 350 • N requests / hour (making each set of requests on behalf of each of our authenticated users) And, lastly, does the status' relation to a given user affect anything? That is, if the status appeared in user n1's timeline, would a request for that status via statuses/show be treated any differently if it were made on behalf of user n1, as compared to some other user (nx) or simply by the application administrator? Please let me know your thoughts. 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 PIC_0075.JPG 318KViewDownload -- 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] statuses/show rate limiting clarification
Hi, Going through the docs on statuses/show (http://dev.twitter.com/doc/ get/statuses/show/:id) we find ourselves going around in circles with a particular issue, and were wondering if someone could help us out. Specifically we're confused about what authentication does and does not allow us to do vis-a-vis rate limiting (as authentication is not required to make this call). I realize that's kind of a jargony sentence, so here's a completely fictional example, the answer to which should answer our question: Say we have N authenticated users using our application, and that we have been archiving statuses by ID (and only ID) coming through their public timelines for some arbitrarily long period of time, such that we have stored thousands of status ID's per user. Now, we'd like to provide a feature allowing our users to recall various of these statuses, and since we've only been storing them by ID, we'll be using the statuses/show method to do this. The rate-limiting doc (http:// dev.twitter.com/pages/rate-limiting) specifies that no more than 150 anonymous requests, or 350 requests via OAuth can be made per hour. However, the statuses/show documentation explains that authentication is not required. Assuming we weren't doing any cacheing, what is the maximum number of requests our application could make to the statuses/ show method, and how does it scale? Specifically, could we make: * 150 requests / hour (because authentication is not required, might all calls count as being anonymous) * 350 requests / hour (from the authenticated account that administers our application) * 350 • N requests / hour (making each set of requests on behalf of each of our authenticated users) And, lastly, does the status' relation to a given user affect anything? That is, if the status appeared in user n1's timeline, would a request for that status via statuses/show be treated any differently if it were made on behalf of user n1, as compared to some other user (nx) or simply by the application administrator? Please let me know your thoughts. 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: Site Streams beta update
Hi Taylor, I wanted to ask about the possibility of finding out about the status of our application to the Site Streams beta. We submitted it on March 24th and have heard nothing back. If you require more information we're happy to provide it, but since we've heard nothing back at all after more than a month we thought we should at least check in. The company is Evri and I believe our application was submitted by David Kellum. Please let me know, thank you. Best, Chuck On Apr 19, 11:54 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers, We know a lot of you are excited to get started with Site Streams (http://dev.twitter.com/pages/site_streams), but the API will continue to be in beta for at least the next few months as we continue preparing it for wider release. During the beta, the criteria we're looking for and applications we're interested in will change as needs criteria evolve. Before applying for the Site Streams beta, we ask that you've developed your application far enough along with User Streams and that you've already built the necessary status event consumption routines for a single-user scenario. This will prepare you to work with Site Streams at a faster clip when access is provided. Site Streams does not support any of the search/track features of the User Streams, so if your application requires these capabilities, Site Streams may not be the right fit. Some developers have asked for Site Streams access with the misunderstanding that it can provide a greater percentage of the firehose than the self-serve options available to them today -- this is also not the case. If you're a developer who has hoped for early access to this beta program but has been unable to join and are looking for alternate implementation options in the meantime, our team is happy to discuss alternate strategies on this mailing list with you. Thanks for your continued patience as we continue productionizing this new platform feature. Taylor Singletary -- 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
Re: [twitter-dev] Getting users' location
Hello Marcelo, Semiocast had released some time ago an API that could be used for what you are trying to do. You can look it up here: http://developer.semiocast.com/ More specifically, for a tutorial on using the API on tweets: http://developer.semiocast.com/tutorial/twitter Hope you'll find this interesting. Bear in mind that, as you say, interpreting what the user wrote can sometime be really difficult (even for a human), but statistically we have some decent results. Cheers, Jean-Charles PS: I'm resending this email as the first one did not went through... On 27 avr. 2011, at 18:22, Marcelo Jenisch wrote: Hello everyone, I need to display the location of someone's followers in a map, so he can see the distribution by country of his followers. I couldn't use the location, since it is just a text box where the user can enter anything and it would be pretty complicated to interpret that without some level of error. So my second idea was to use the place info in the user's last tweet, but then I realized that most tweets don't attach such info. So now I'm at a loss. Do I invest time in interpreting the location field, or are there better (easier or more accurate) ways to get such info? It doesn't even need to be down to the city level, as long as I can get a country, it's fine. Thank you all in advance. Best regards, Marcelo -- 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] Re: Streaming Api returning tweets with NULL value for object place
Same question here. Eric On Feb 17, 12:59 am, aci acicartag...@gmail.com wrote: Hello, I am using the streaming api in order to be able to save tweets that uses the geoJSON place key of the returned json object. Tt was working fine last Tuesday, Feb 15, But now, there seems to be a problem with the place tag of the tweet object. I was just wondering if it's just me or is there some sort of bug or changes have been made in the API? Aci Cartagena -- 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: Frequent errors when using OAuth, none when using basic
On Aug 4, 3:54 pm, Cameron Kaiser spec...@floodgap.com wrote:
ITYM twurl
Could well have been. I seem to remember spending ages installing
dependencies with gem install (few of them appeared to be available
in Debian packages) and eventually ran into a brick wall where the
versions required just didn't seem to be available from wherever gem
install gets them from.
Dave Ingram d...@dmi.me.uk wrote:
I'm in the middle of tidying up a python-based oauth command-line client
Cameron Kaiser again:
I'll also throw in a plug for TTYtter, which has no dependencies other than
Thanks for the suggestions, but actually I think I've managed to fix
things without switching to something completely different.
Main thing was, I'd either misread, or just failed to read, the
documentation for curl's -d option. It needs to be URL-encoded
before passing to curl. I am how stuffing the text I want to send
through the following; probably overkill, but it seems to work:
TWEET=$(echo -n $MSG | head -c140 | od -An -tx1 -v | tr '\n' ' ' |
sed 's/^/ /;s/[^0-9A-Fa-f]/ /g;s/ *$//;s/ */%/g')
Basically, it %-encodes every character.
The other thing I fixed was oauth-proxy itself. Including the status=
parameter in the Authorization header does seem to break things
sometimes, probably depending on which special characters are included
(and probably not properly escaped) in the value. This patch seems to
fix that:
--- oauth/oauth.py.orig 2010-08-04 20:06:55.0 +0100
+++ oauth/oauth.py2010-08-04 16:16:42.0 +0100
@@ -118,12 +118,22 @@
parameters[k] = v
return parameters
+# get only oauth parameters
+def get_oauth_parameters(self):
+parameters = {}
+for k, v in self.parameters.iteritems():
+# ignore oauth parameters
+if k.find('oauth_') == 0:
+parameters[k] = v
+return parameters
+
# serialize as a header for an HTTPAuth request
def to_header(self, realm=''):
auth_header = 'OAuth realm=%s' % realm
# add the oauth parameters
-if self.parameters:
-for k, v in self.parameters.iteritems():
+parameters = self.get_oauth_parameters()
+if parameters:
+for k, v in parameters.iteritems():
auth_header += ', %s=%s' % (k, v)
return {'Authorization': auth_header}
With these two fixes, I haven't yet had any problems. Thanks for the
help!
--Charles
[twitter-dev] Re: Frequent errors when using OAuth, none when using basic
Hi Taylor, Thanks for your analysis. As mentioned, I'm using oauth-proxy (http:// github.com/mojodna/oauth-proxy, I think was the URL); I wrote none of the OAuth code, so I have no idea what it may or may not be doing. I tried it, it seemed to work (until these problems posting nagios notifications) so I used it. You mentioned % characters not being properly encoded - I did wonder whether the problem was %-related before, but tried some test tweets containing % characters and generally found that they posted properly. I had a bit of a brainwave while on the train today, though, and realised that if = signs are being mishandled (not sure why I overlooked = before!), that would fit the symptoms. And indeed, it does look like that might be the problem - I just tried substituting _ for = in a previously failed notification, and it posted fine. However, if oauth-proxy is indeed doing OAuth as badly as your list of faults implies, I may have a bit of a job on my hands to figure out what it's doing and fix it, or might try to find some other OAuth proxy or client. Pity, though, as oauth-proxy was about the only thing I'd found so far which lets me send tweets relatively easily from a shell script. (There was a curl-alike with OAuth support whose name I forget, which had so many dependencies (Ruby, I think) that I eventually gave up trying to get it to work.) It's also possible that I may be curling data into oauth-proxy incorrectly - I will try doing %-escaping on my argument to curl's -d option and see how that affects things. Anyway, for now, I can replace = with _. When I have time, I can either try staring hard at oauth-proxy to try to understand and fix it, or look for an alternative tool. Hmm, maybe by then, curl will have OAuth support... Thanks for your help, --Charles
[twitter-dev] Frequent errors when using OAuth, none when using basic
I sent the following to Twitter support via their web form; they suggested I should post here instead. - I currently have two automated accounts, thethirdstroke and this one (servologyalerts). thethirdstroke tweets every hour on the hour, and has been working fine for a long time. I converted it to using OAuth a while ago, and it continued to work fine. servologyalerts tweets when my nagios installation detects a fault or a fault clears, and has been having problems since I switched it from password authentication to OAuth on 12 July. Since that time, most attempts to tweet get the Something is technically wrong response. However, most test tweets seem to go through without any problem, and reviewing the logs I notice that any alert which is long enough that my script has to truncate it to 140 characters before tweeting, and therefore loses (part of) the packet loss = nnn% which is often at the end of the tweet, goes through fine. I wonder if the problem is that my alerts are somehow triggering spam filtering, which is then returning a Something is technically wrong error message rather than actually saying it's spam filtering. That doesn't seem a likely explanation, though, as the problem started precisely when I switched from basic auth to OAuth - surely OAuth would, if anything, need to do *less* spam filtering. Both automated accounts tweet using the same script, which uses curl to post through a python program called oauth-proxy, which I have altered to listen only on the loopback interface, and which is started up just before each tweet and shut down just afterwards. As mentioned, there doesn't seem to be any problem with the OAuth signing - thethirdstroke posts fine pretty much all the time, while servologyalerts can post test messages and, occasionally, live messages with no problems. It also does not seem to be a problem with OAuth signing requests containing % signs, as I've posted test messages with % signs with no problem. I'd be grateful if you could check any logs you have and let me know if you can see why this problem occurs, and if you can suggest a fix. Thanks for your help. - Update: I have temporarily switched back to using basic authentication for servologyalerts; the errors have stopped and notifications arrive on twitter as expected. Thanks for any light you can shed; and let me know if more information is needed - I didn't think there was any need to copy-and-paste the Something is technically wrong page's HTML here, for example.
Re: [twitter-dev] Country based search
Hello Rachit, Maybe you will be interested in looking at our Semiocast API. It provides methods to filter tweets by location (and language) among other things. Please have a look at the section Filter Twitter status updates -- Example: filtering by language and location located at the URL: http://developer.semiocast.com/tutorial/twitter More information is available on the website of Semiocast API http://developer.semiocast.com/ Semiocast API also provides some method for short raw text and Facebook messages processing. It is recommend to start reading the tutorial first. Don't hesitate to contact us if you need more information or help. Best regards, Jean-Charles Campagne On Tue, Jul 20, 2010 at 9:22 AM, rachit gupta rachit.t...@gmail.com wrote: Hi All, I am a developer from India, working on integrating Twitter with few of my application. I wished to know, if there exists a way through which we can get Twitter search result only from a particular country not using the Geocode functionality, because Geocode functionality cant be extended to country wide result.
Re: [twitter-dev] US Location Stream
Hello James, Our current free access grants you 1024 calls per 24 hours for the moment. This should give you enough call credits to test the API. As of today, we grant higher-level access on a case by case basis. Please contact us for further discussion. Best regards, Jean-Charles Campagne On Tue, Jul 6, 2010 at 8:43 PM, James Kim ja...@keytweet.com wrote: Hi JC. What are the limits on free? We're wary of locking ourselves into a service that we won't be able to afford. On Mon, Jul 5, 2010 at 2:44 AM, Jean-Charles Campagne a...@semiocast.com wrote: Hello James, may be you would be interested in looking at our API which provides language and location filtering on tweets. More specifically, you'll find an example for filtering tweets based on location and on language under Example: filtering by language and location, located at the URL http://developer.semiocast.com/tutorial/twitter Do not hesitate to visit our API website: http://developer.semiocast.com or ask for more information. Hope you'll find this useful. Best regards, Jean-Charles Campagne Semiocast On Sat, Jul 3, 2010 at 1:26 AM, James Kim ja...@keytweet.com wrote: Hi John, Thanks for the quick reply. Is there a way to exclude non-english tweets from the stream like the search api does? On Fri, Jul 2, 2010 at 4:03 PM, John Kalucki j...@twitter.com wrote: Hi James, Nope. Even if we allowed all the bounding boxes to cover the US, you'd only get the tweets that are geo-tagged, which isn't a large proportion. -John On Fri, Jul 2, 2010 at 3:55 PM, James Kim ja...@keytweet.com wrote: Hi all, I'm trying to capture all the tweets originating from the US. Is there a simple way to do this without creating many bounding boxes? -- James C. Kim @jamesckim http://keytweet.com - a learning filter for twitter -- James C. Kim @jamesckim http://keytweet.com - a learning filter for twitter
Re: [twitter-dev] Farsi Twitter App
Hello Lucas, We do not provide, yet, exactly what you are looking for, but for now we might help you on the language filtering part. We provide an API for language and location filtering for micro-messages (Tweets and Facebook messages, etc.). You'll find more info on the API website: http://developer.semiocast.com Regarding the feature you are looking for, we made a request to Twitter to be able to redistribute a filtered API, so we will be able to provide something closer to what you are looking for. You can, more or less, achieve the same today with our current state of the API but it'll be more plumbing on your side. Best regards, Jean-Charles Campagne Semiocast On Sat, Jul 3, 2010 at 12:36 AM, Lucas Vickers lucasvick...@gmail.com wrote: Hello, I am trying to create an app that will show tweets and trends in Farsi, for native speakers. I would like to somehow get a sample 'garden hose' of Farsi based tweets, but I am unable to come up with an elegant solution.
[twitter-dev] [ANN] Semiocast releases micromessage analysis API
Hello Everyone, Semiocast has been developing technologies for analyzing micro-messages (such as Twitter and Facebook messages) and today Semiocast is making two of these technologies available to the public as a web service through its API: - language identification from short text: 61 languages recognized (including non-latin languages such as Arabic, Chinese, Farsi, Japanese, Korean, Pashto, Russian, Ukrainian…); - location extraction from short text: city and country recognized from free form text or GPS coordinates. Although these technologies were specifically developed for short free form texts, Semiocast API is tailored for analyzing Twitter messages (and other networks such as Facebook, StatusNet…). With Semiocast API, you can: - analyze status updates and timelines to extract language and user location; - filter timelines according to languages and locations; - prepare annotations based on semantic analysis for a message to be posted on Twitter using the forthcoming annotation feature. We are very excited by what you will be able to build using this API. For example, you can use Semiocast API to compute statistics about messages or to filter out messages in languages end-users do not understand. Semiocast has used the very same technology for the February and March 2010 studies that revealed that less than 50% of tweets were not in English and gave a break down of tweets by languages and countries. Future releases will give access to more of our technologies such as tokenization, sentiment analysis and topic extraction. For more information, please visit Semiocast API website: http://developer.semiocast.com/ Let us know what you think! Jean-Charles
[twitter-dev] Re: In San Francisco for WWDC? Come to Twitter HQ on June 9th 6-8pm for a @twitterapi meetup!
Thought I'd make an announcement that I've posted a working example of Twitter OAuth integration for the iPhone using OAuthConsumer. It's hosted on Google code and you can find it here: http://code.google.com/p/oauthconsumer-iphone/ Have fun with it. -Charles @cy_choi
Re: [twitter-dev] Problem sending tweets with nbsp chars
URL Encoding? On 4 March 2010 02:13, Roy Leban r...@royleban.com wrote: Twitter is rejecting tweets as too long when the nbsp character is used. Here is an example tweet in plain text Clue 5 of 15: R _ C __ _ N _N _ _ E __ _ T E R__ _ _ N E E R_ N_ _ R _ C U L T U R E http://www.puzzazz.com/s348 [140 chars] And, as I'm sending it with the nbsp characters: Clue 5 of 15: Rnbsp;_nbsp;Cnbsp;_nbsp;nbsp; nbsp;_nbsp;_nbsp;Nnbsp;_nbsp;nbsp; nbsp;Nnbsp;_nbsp;_nbsp;Enbsp;_nbsp;nbsp; nbsp;_nbsp;_nbsp;Tnbsp;Enbsp;Rnbsp;nbsp; nbsp;_nbsp;nbsp; nbsp;_nbsp;_nbsp;_nbsp;Nnbsp;Enbsp;Enbsp;Rnbsp;nbsp; nbsp;_nbsp;Nnbsp;nbsp; nbsp;_nbsp;_nbsp;Rnbsp;_nbsp;Cnbsp;Unbsp;Lnbsp;Tnbsp;Unbsp;Rnbsp;E http://www.puzzazz.com/s348 If the nbsp's are each counted as 6 characters, this would be 400 chars, but Twitter accepts tweets like this. For example, this tweet: http://twitter.com/Puzzazz/status/9781320047 is 114 chars but I send 304 chars with the nbsp's. I have a guess that this only happens when the resulting tweet is exactly 140 chars. To test this theory, I just modified the site to shorten that tweet below 140. Sure enough, it works: http://twitter.com/Puzzazz/status/9963348931 -- Charles A. Lopez charlesalo...@gmail.com What's your vision for your organization? What's your biggest challenge? Let's talk. (IBM Partner)
Re: [twitter-dev] Search API rate limit IP address question
On 2 March 2010 14:05, eys eddiey...@yahoo.com wrote: Hello there! I have two questions: First, I received an approval for whitelisting for my server's IP address (as in, the IP number that I see when I log onto my webhosting account). I'm currently building my application in Flash using AS3 and after I've tested my project a few times, I'll get this error: Error #2032: Stream Error...[my search request] I assume this is rate limiting in action? If this were true then sometimes your request works and other times it doesn't. Is that the case? I read on this discussion board that whitelisting doesn't affect Search API. Does this mean I will always be limited to some arbitrary (unpublished) search limit? Then, I noticed the IP address used for the GET request is the IP address of the computer I'm using, NOT the IP address of my web server. How is this happening even though I'm using a proxy installed on my web server? Shouldn't the call be made from the server, not the computer? There are multiple requests happening here. I assume the following, which may or may not be correct: - From your browser you call your app - Your app runs some call through the twitter API - Twitter servers process the call and send it back to your app - Your app returns processed code back to your browser From the above processes your IP address is passed through by the Twitter API to the twitter service. I'd suggest try running your request from a completely different network and see what happens. Thank you. I'm pretty new at developing applications, so any help or advice is greatly appreciated! -- Charles A. Lopez charlesalo...@gmail.com What's your vision for your organization? What's your biggest challenge? Let's talk. (IBM Partner)
Re: [twitter-dev] Twitter Application Suspended
you might be doing something perceived as offensive. In the past on projects i have worked on, I had over utilized the processing resources of a remote server. Are you doing anything like that? 2010/1/26 Proxdeveloper prox.develo...@gmail.com Hello folks, This is the 3rd time I get my application suspended from twitter, the 2 different names I've tried are : Twhit,TwhitClient, and both have been suspended; Twhit has been suspended for 2 times already, I deleted the app and then registered it again. My experience of developing with twitter has been awful, it's one problem after another. Could anyone help me on why I'm getting my app suspended. --
[twitter-dev] Re: Whitelisted IPs only work when authed?
Thank you, Waldron -- that may be the solution. I will look into it! On Oct 10, 11:36 am, Waldron Faulkner waldronfaulk...@gmail.com wrote: Are you sure your requests are coming from the same IP you whitelisted? If you're on a shared host, for example, your outbound requests may come from a different IP as your dedicated inbound IP. I had this issue, had to bind curl to my dedicated IP, and it worked fine. Setting the CURLOPT_INTERFACE option is what worked for me. On Oct 9, 5:08 pm, Charles colei...@gmail.com wrote: I recently received email that confirmed my whitelisting status. I have several IPs whitelisted, as well as the account. From a shell on one of the whitelisted servers, I make a couple requests and then try: curlhttp://twitter.com/account/rate_limit_status.xml ?xml version=1.0 encoding=UTF-8? hash hourly-limit type=integer150/hourly-limit reset-time-in-seconds type=integer1255123230/reset-time-in- seconds reset-time type=datetime2009-10-09T21:20:30+00:00/reset-time remaining-hits type=integer147/remaining-hits /hash If, on the other hand, I try: curl -u username:passwordhttp://twitter.com/account/rate_limit_status.xml hash remaining-hits type=integer1/remaining-hits reset-time type=datetime2009-10-09T21:57:09+00:00/reset-time hourly-limit type=integer2/hourly-limit reset-time-in-seconds type=integer1255125429/reset-time-in- seconds /hash I was under the impression I did not have to auth if I was making calls from the API? Also: if I use my application's oauth credentials to generate an oauth_request and use the oauth URL, I am still getting the lower rate limit. Is this normal behavior?
[twitter-dev] Whitelisted IPs only work when authed?
I recently received email that confirmed my whitelisting status. I have several IPs whitelisted, as well as the account. From a shell on one of the whitelisted servers, I make a couple requests and then try: curl http://twitter.com/account/rate_limit_status.xml ?xml version=1.0 encoding=UTF-8? hash hourly-limit type=integer150/hourly-limit reset-time-in-seconds type=integer1255123230/reset-time-in- seconds reset-time type=datetime2009-10-09T21:20:30+00:00/reset-time remaining-hits type=integer147/remaining-hits /hash If, on the other hand, I try: curl -u username:password http://twitter.com/account/rate_limit_status.xml hash remaining-hits type=integer1/remaining-hits reset-time type=datetime2009-10-09T21:57:09+00:00/reset-time hourly-limit type=integer2/hourly-limit reset-time-in-seconds type=integer1255125429/reset-time-in- seconds /hash I was under the impression I did not have to auth if I was making calls from the API? Also: if I use my application's oauth credentials to generate an oauth_request and use the oauth URL, I am still getting the lower rate limit. Is this normal behavior?
[twitter-dev] Re: Whitelisted IPs only work when authed?
Bump On Oct 9, 4:08 pm, Charles colei...@gmail.com wrote: I recently received email that confirmed my whitelisting status. I have several IPs whitelisted, as well as the account. From a shell on one of the whitelisted servers, I make a couple requests and then try: curlhttp://twitter.com/account/rate_limit_status.xml ?xml version=1.0 encoding=UTF-8? hash hourly-limit type=integer150/hourly-limit reset-time-in-seconds type=integer1255123230/reset-time-in- seconds reset-time type=datetime2009-10-09T21:20:30+00:00/reset-time remaining-hits type=integer147/remaining-hits /hash If, on the other hand, I try: curl -u username:passwordhttp://twitter.com/account/rate_limit_status.xml hash remaining-hits type=integer1/remaining-hits reset-time type=datetime2009-10-09T21:57:09+00:00/reset-time hourly-limit type=integer2/hourly-limit reset-time-in-seconds type=integer1255125429/reset-time-in- seconds /hash I was under the impression I did not have to auth if I was making calls from the API? Also: if I use my application's oauth credentials to generate an oauth_request and use the oauth URL, I am still getting the lower rate limit. Is this normal behavior?
[twitter-dev] Re: What is 140 characters?
2009/9/9 Matt Sanford m...@twitter.com Hi There, I'm sorry this never got updated. Some changes have been made and are waiting to go out now. When I switched from working on the Platform (formerly API) team to my focus on international I took over this issue. Once this current fix is deployed (probably in a week or so since I'm traveling at the moment) the definition of a character will be consistent throughout our API. The new change will always compute length based on the Unicode NFC [1] version of the string. Using the NFC form makes the 140 character limit based on the length as displayed rather than some under-the-cover byte arithmetic. I more than agree with the above statement that a character is a character and Twitter shouldn't care. Data should be data. The main issue with that is that some clients compose characters and some don't. My common example of this is é. Depending on your client Twitter could get: é - 1 byte - URL Encoded UTF-8: %C3%A9 - http://www.fileformat.info/info/unicode/char/00e9/index.htm isn't that 2 bytes? -- or -- é - 2 bytes - URL Encoded UTF-8: %65%CC%81 - http://www.fileformat.info/info/unicode/char/0065/index.htm + plus: http://www.fileformat.info/info/unicode/char/0301/index.htm and this three bytes? So, my fix will make it so that no matter the client if the user sees é it counts as a single character. I'll announce something in the change log once my fix is deployed. Thanks; — Matt Sanford / @mzsanford [1] - http://www.unicode.org/reports/tr15/ On Sep 9, 6:05 am, TjL luo...@gmail.com wrote: It's been nearly 6 months. Has this question been answered? If so I missed it. On Tue, Mar 24, 2009 at 9:36 PM, Alex Paynea...@twitter.com wrote: Unfortunately, nothing definitive. We're still looking into this. On Tue, Mar 24, 2009 at 07:56, Craig Hockenberry craig.hockenbe...@gmail.com wrote: Any news from the Service Team? I'd really like to get the counters right in an upcoming release... -ch On Mar 6, 12:18 pm, Alex Payne a...@twitter.com wrote: I'm taking this email to our Service Team, the folks who work on the back-end of the service. The whole message body changing as it moves from cache to backing store thing is totally unacceptable. Answers soon. On Fri, Mar 6, 2009 at 09:43, Craig Hockenberry craig.hockenbe...@gmail.com wrote: Some discussion about this thread popped up on Twitter yesterday: http://groups.google.com/group/twitter-development-talk/browse_thread/ thread/44be91d5ec5850fa Alex states that it's 140 bytes per tweet. So, of course, Loren Brichter and I tried to prove that. With the following results: 1) 140 characters that including ones that include HTML entities: http://twitter.com/gnitset/status/1286202252 At the time of posting, this tweet showed up on the site and in feeds with all 140 characters. After a few hours, the was converted to lt;, increasing the count per character from one to four bytes and decreasing the tweet length from 140 characters to 69. (You can see this truncation at the end of the tweet: the is from lt;) Presumably, this happens as tweets in the memcache are written though to the backing store. I also see a lot of Twitter clients that don't realize how special the lt; and gt; entities are. It took me a LONG time to figure out what was going on here. 2) 140 Unicode _multi-byte_ characters: http://twitter.com/atebits/ status/1286199010 What's curious is that Loren's example with 140 characters uses the Unicode 27A1 glyph. It uses 3 bytes in UTF-8. Why didn't it get truncated? This seems to contradict Alex's statement in the thread mentioned above. As people start to use things like Emoji, tinyarro.ws and generally figure out that Unicode (UTF-8) is a valid type of data on Twitter, our clients should adapt and display more accurate characters remaining counts. I can count bytes instead of characters, but I'm not sure if I should or not. No one likes a truncated tweet: we need an explicit statement on how to count and submit multi-byte characters and entities. -ch -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: FW: Twitter is Suing me!!!
Has nothing to do with anything. Enforce your trademark evenly or don't enforce it at all. Selective enforcement is not allowed. On Aug 12, 10:57 am, Rich rhyl...@gmail.com wrote: and I'm certain the reason for adding the Twitter name violation in there in addition to all the others is that they don't want their name associated with, what is effectively a Web 2.0 spamming operation. On Aug 12, 3:55 pm, Duane Roelands duane.roela...@gmail.com wrote: Are any of these developers -selling- their products? You are. Are any of these developers violating the Terms of Service? You are. Just because another website has Twitter in the name doesn't make their situation the same as yours. You made a tool for spammers. You get caught. Get over it. On Aug 12, 10:14 am, Dean Collins d...@cognation.net wrote: So has anyone heard from or know any of the other developers? Did they also get an email last night?
[twitter-dev] Re: FW: Twitter is Suing me!!!
I love how in this discussion people keep trying to bring emotion and personal beliefs into a legal context. So he made a tool for spammers. What does that have to do with anything? First they came for the Spammers and I didn’t speak up, because I wasn’t a Spammer. There are two LEGAL issues here - The Twitter Trademark - Violation of TOS Twitter trademark - as has been mentioned by many - you can NOT selectively enforce a trademark. I don't care what the application's intended use. As for the violation of TOS - the section of the TOS that Chris quoted is explicit, but then goes vague by injecting brevity and 'kindas'. Strict interpretation would evaluate that Chris's game application is in violation of the TOS. Unfortunately most of the Twitter TOS is vague. Every application you write requires an evaluation against nothing certain. 'Hmmm this service provides value to me, and I believe it provides value to the Twitter community that it targets, but will it provide value to the Twitter lawyers?' I don't know the specifics of the My Twitter Butler application but there is probably wiggle room. On Aug 12, 10:55 am, Duane Roelands duane.roela...@gmail.com wrote: Are any of these developers -selling- their products? You are. Are any of these developers violating the Terms of Service? You are. Just because another website has Twitter in the name doesn't make their situation the same as yours. You made a tool for spammers. You get caught. Get over it. On Aug 12, 10:14 am, Dean Collins d...@cognation.net wrote: So has anyone heard from or know any of the other developers? Did they also get an email last night?
[twitter-dev] Aquí 1.0 released today
A heads up that I've just published an iPhone Twitter client called Aquí that lets you tweet your Google Maps location with a single push- button operation. Thanks for all the input here that helped me build this app. Here's the URL for Aquí: http://www.yummymelon.com/aqui Best regards - -Charles
Re: Can't view/retrieve full text message with length greater than 140 and = 160 characters?
It's not a flaw but a feature. On Fri, Dec 19, 2008 at 9:44 PM, Scott Carter scarter28m-goo...@yahoo.comwrote: Hi Alex, Please refer to a related thread at: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/d11a31c7ecf033b/130ed44d6b502e6c?lnk=gstq=160#130ed44d6b502e6c I am trying to send an update via the API that is greater than 140 characters, but = 160. When I try to view the whole message on the Web by clicking on the elipsis ... I do not see the full message. I tried the following two calls: http://twitter.com/statuses/user_timeline.json http://twitter.com/statuses/user_timeline.xml In both cases, I see truncated set to true, and the value of text is the same as what I see on the Web - not the full message. Is it no longer possible to see/retrieve an update where 140 length = 160 ? If this is the case, why does the documentation at http://apiwiki.twitter.com/REST+API+Documentation say Must not be more than 160 characters under the update function? An example with 155 characters is: http://twitter.com/blueskies2/status/1068333279 Almost a foot of snow was predicted for parts of central Michigan, CNN affiliate WNEM-TV in Saginaw reported. Classes were canceled in hundreds of schools. This is a protected update (my developer account) - please feel free to view it for debug as needed. Thanks in advance for a clarification. Scott
