[twitter-dev] Re: Access level changed to Read, Write AND Direct Message but still can't access DMs!
I have the same problem. On the App settings it is set to: Read, Write and Access direct messages But when users authenticate with OAuth, it's telling users: This application will not be able to: Access your direct messages. How do we fix this? On Jul 4, 5:38 pm, alexre...@gmail.com alexre...@gmail.com wrote: Most of my apps require read access forDirectMessages, but they're only reading from one account. Many users DM to one account and I need access to that one account to grab all the DMs (which no longer works as of June 30th). I changed the Access Level of all my apps to Read, Write andDirect Message, but it doesn't seem that the change has taken place, or I'm missing something, somewhere in terms of what I need to do? When I try and re-authorize an account I see the following on the Twitter / Authorize screen: This application will not be able to: Access yourdirectmessages. See your Twitter password. What else do I need to do? I have confirmed that the application settings on Twitter do say, Read, Write andDirectMessagesfor my app but I can only use my access token (for the Twitter handle associated with the app) to accessdirectmessages, anytime I try and re-authorize any account through my actual app, I see: This application will not be able to: Access yourdirectmessages. See your Twitter password. ... which isn't inline with how I setup the settings. Any help would be greatly appreciated. I'm really hoping I'm missing something small here. -- 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: frustration with Tweet Button counter
BUMP
Anyone?
On Feb 27, 11:26 am, Mr Blog mrblogdot...@gmail.com wrote:
We cannot get the official Tweet Button to count tweets - it always
shows zero.
Here's an example page:
http://140plus.com/question/why-do-i-need-nosql-mongodb-cassandra-cou...
And the code for the button is:
a href=http://twitter.com/share; class=twitter-share-button
data-url=http://140-pl.us/8Tyz1;
data-counturl=http://140plus.com/question/why-do-i-need-nosql-
mongodb-cassandra-couchdb-etc-if-i-have-lucene-or-solr/8Tyz1
data-via=mrblog
data-text=Why do I need NoSQL (MongoDB, Cassandra, CouchDB,
etc) if I have Lucene (or Solr)?Tweet/a
The idea is we want to tweet our custom shortened URL specified by the
data-url attributehttp://140-pl.us/8Tyz1that redirects to
Location:http://140plus.com/question/why-do-i-need-nosql-mongodb-cassandra-cou...
And that's the url we want to count, as specified by data-counturl
attribute shown above.
However, the count stays zero. Here are two tweets of the URL:
http://twitter.com/patriottweakers/status/40123917301456896http://twitter.com/unclefisty/status/40123256140873728
Yet the counter on the tweet button stays at zero. What am I doing
wrong?
I note that calling the API with the dataurl URL gives:
{count:0,url:http://140plus.com/question/why-do-i-need-nosql-
mongodb-cassandra-couchdb-etc-if-i-have-lucene-or-solr/8Tyz1/}
Note the URL shown in the result has the / appended, even though the
URL being passed to the counter API did NOT have the trailing / and
the url being linked to does NOT have a trailing / - not sure if
that matters.
--
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] frustration with Tweet Button counter
We cannot get the official Tweet Button to count tweets - it always
shows zero.
Here's an example page:
http://140plus.com/question/why-do-i-need-nosql-mongodb-cassandra-couchdb-etc-if-i-have-lucene-or-solr/8Tyz1
And the code for the button is:
a href=http://twitter.com/share; class=twitter-share-button
data-url=http://140-pl.us/8Tyz1;
data-counturl=http://140plus.com/question/why-do-i-need-nosql-
mongodb-cassandra-couchdb-etc-if-i-have-lucene-or-solr/8Tyz1
data-via=mrblog
data-text=Why do I need NoSQL (MongoDB, Cassandra, CouchDB,
etc) if I have Lucene (or Solr)?Tweet/a
The idea is we want to tweet our custom shortened URL specified by the
data-url attribute http://140-pl.us/8Tyz1 that redirects to
Location:
http://140plus.com/question/why-do-i-need-nosql-mongodb-cassandra-couchdb-etc-if-i-have-lucene-or-solr/8Tyz1
And that's the url we want to count, as specified by data-counturl
attribute shown above.
However, the count stays zero. Here are two tweets of the URL:
http://twitter.com/patriottweakers/status/40123917301456896
http://twitter.com/unclefisty/status/40123256140873728
Yet the counter on the tweet button stays at zero. What am I doing
wrong?
I note that calling the API with the dataurl URL gives:
{count:0,url:http://140plus.com/question/why-do-i-need-nosql-
mongodb-cassandra-couchdb-etc-if-i-have-lucene-or-solr/8Tyz1/}
Note the URL shown in the result has the / appended, even though the
URL being passed to the counter API did NOT have the trailing / and
the url being linked to does NOT have a trailing / - not sure if
that matters.
--
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] My Access Token
I keep seeing references to a way to see your own access token for an app: http://dev.twitter.com/apps - application - My Access Token E.g. http://dev.twitter.com/pages/oauth_single_token I can't find this link under http://dev.twitter.com/apps anywhere. Did it go away, or am I just not finding it? -- 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: Twitter4J and sun.security.validator.ValidatorException
FWIW, api.twitter.com cert also fails in Safari: http://twitmart.org/img/UoNgE/apicerterr2.png On Jul 1, 4:26 am, Yusuke yus...@mac.com wrote: Hi, Twitter4J users are facing sun.security.validator.ValidatorException as of July 1 GMT. It looks to be an API side issue. Is it a known one? It can be workarounded with -Dtwitter4j.http.useSSL=false or System.setProperty(twitter4j.http.useSSL,false);. The exception stack trace looks like as following: Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.validator.PKIXValidator.doBuild(Unknown Source) at sun.security.validator.PKIXValidator.engineValidate(Unknown Source) at sun.security.validator.Validator.validate(Unknown Source) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(Unknown Source) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(Unknow n Source) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(Unknow n Source) ... 48 more Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown Source) at java.security.cert.CertPathBuilder.build(Unknown Source) ... 54 more Cheers, -- Yusuke Yamamoto yus...@mac.com this email is: [x] bloggable/tweetable [ ] private follow me on :http://twitter.com/yusukeyamamoto subscribe me at :http://samuraism.jp/
[twitter-dev] Re: moving the OAuth switch over date to august 16, 2010
I have a suggestion that I think will be helpful for developers. When the FCC shut of analog OTA TV, they scheduled a number of test periods, where OTA TV was shut off briefly so people could see if their TV was ready for the switch. I suggest that after the World Cup related trouble subsides, that @twitterapi schedule a few tests where Basic Auth is turned off for 5 minutes, or 30 minutes or something, so developers can ensure their apps actually don't have any latent (accidental) Basic Auth dependent code hiding somewhere. Otherwise, we won't REALLY know for sure we've plugged all Basic Auth holes until the real cutoff and then it will be much more painful for our (mutual our) users. On Jun 17, 4:46 pm, Raffi Krikorian ra...@twitter.com wrote: hi all. as you've all probably noticed, with the world cup going on, twitter is experiencing record load. because of this, we're moving the oauth switchover date to august 16, 2010. we want to make sure that you all have calm waters to test your new codebases where you're not dealing with whales, robots, and whatnot. with the world cup ending on july 11th, you will all have over a month's time of calm waters and site stability to finish the switch over. also, with the vast majority of media providers already switched over to OAuth Echo, you now also have an additional month of time to work out your integrations with them. just to review what we're going to be doing: starting on august 16 we'll be ramping down the rate limits on basic auth roughly by 10 calls/hour/day ending on august 31st. on the 31st, you won't be allowed to make any other basic auth calls. in other words, if you don't do anything, you'll get more and more frequent rate limit errors as you approach august 31st. starting on august 31st, any basic auth request will get a HTTP 403 response back. as always, please reach out if there are any questions or concerns. for those who have already switched over, thanks! -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: statuses/update 403 error
Agreed. If the API is going to overload an error code, Twitter needs to enumerate the error details and provide those details in a consistent machine readable form. On May 25, 1:52 am, akaii chibiak...@gmail.com wrote: There seem to be a variety of possible causes for getting an 403 error in responses to a calling statuses/update... you could be duplicating a tweet or hitting the update limit for an hour or for the day. How can you tell which one these errors actually occurred? The only 2 ways I can think of is to try and parse the error message, or to follow up the request with a query about whether you've hit any limits. The problem with checking the error message is that: 1) It's fragile. If the twitter dev team decides to change the error msg, the solution breaks. 2) I'd have to know the error message first... and the specific error messages for hitting the update limit don't seem to be documented anywhere that I can see. Not in the wiki for sure. Which means that I'd have to hit the limit to find out directly what the messages are... not exactly practical, especially for the 1000 per day limit. It would take me a minimum of 7 hours to hit that limit, since I'd get capped by the hourly limit first. The problem with a follow-up request is that: I can't seem to find a way to get current remaining tweets available to the user before hitting the status update limit in the api. There's one for rate limiting: account/rate_limit_status But where's the corresponding api for the status update limits? What should I do about this? Is there some third, better way to find out which specific error resulted from the update attempt?
[twitter-dev] Re: duplicate tweet behavior has changed within the last few days
Thanks for the response, Taylor. I do appreciate it. There is some irony in the fact that I have to inject some superfluous drivel into a perfectly legitimate non-duplicate tweet to appease the Twitter spam filters - more collateral damage hitting innocent, legitimate users - very indicative of the state of the Twitterverse. Thanks again. On May 26, 9:39 am, Taylor Singletary taylorsinglet...@twitter.com wrote: We're always working to improve our duplicate tweet detection routines, and as such there's no hard equation you can follow for issuing duplicate tweets reliably. I'm a big advocate for expressing these kind of limits in a way you can interpret programatically but in this case the target is moving. By indicating the time window when a duplicate of the recently submitted tweet could be resubmitted, we would be opening an abuse vector. Including something unique in the string might be your best bet to get around this. On May 22, 11:19 pm, Mr Blog mrblogdot...@gmail.com wrote: My GaragebBot tweets when doors are opened or closed:http://twitter.com/connectedthings The tweets are of the form: tweet 1: Door 2 opened tweet 2: Door 2 closed manually tweet 3: Door 1 opened tweet 4: Door 2 opened tweet 5: Door 2 closed automatically tweet 6: Door 1 closed manually The behavior up until a few days ago was duplicates were defined as tweet N+1 being identical to the prior tweet N, but now there appears to be some kind of cache where tweet 4 above fails with a 403 duplicate tweet error even though it is not a duplicate of the most recent tweet (but is the same message as tweet 1, but a different in time, so thus meaningful). In this case, the garage only tweets about 6 different messages and it has been doing so for several years, with great success, but now almost all tweets are being rejected as duplicates. I could change it to put some random garbage at the end of each new tweet, but that doesn't seem very elegant.
[twitter-dev] duplicate tweet behavior has changed within the last few days
My GaragebBot tweets when doors are opened or closed: http://twitter.com/connectedthings The tweets are of the form: tweet 1: Door 2 opened tweet 2: Door 2 closed manually tweet 3: Door 1 opened tweet 4: Door 2 opened tweet 5: Door 2 closed automatically tweet 6: Door 1 closed manually The behavior up until a few days ago was duplicates were defined as tweet N+1 being identical to the prior tweet N, but now there appears to be some kind of cache where tweet 4 above fails with a 403 duplicate tweet error even though it is not a duplicate of the most recent tweet (but is the same message as tweet 1, but a different in time, so thus meaningful). In this case, the garage only tweets about 6 different messages and it has been doing so for several years, with great success, but now almost all tweets are being rejected as duplicates. I could change it to put some random garbage at the end of each new tweet, but that doesn't seem very elegant.
[twitter-dev] Re: Basic authentication
Perhaps, but I think it's a mistake to shut supertweet down. It's solving a real-world problem, doing them a favor by doing something for twitter so they don't have to. It pushes all these corner cases off of their API front-end. It doesn't expose the user's Twitter passwords and users never expose their passwords to supertweet. Supertweet isn't so people can be lazy - people should still supprot oAuth and nobody should be using to make API calls on behalf of others (as in a normal Twitter user client). But it will really help PHP scripts and the like bridge over until their hosting service or whatever supports tools for OAuth. So again, I'd say http://www.supertweet.net is doing Twitter a favor. On May 21, 6:14 am, Tammy Fennell tammykahnfenn...@gmail.com wrote: Hey, I'm pretty sure that Twitter isn't going to like that very much. The whole point is that everyone uses it not tries to get around it... I can't imagine supertweet will maintain it's own oauth for very long... On May 20, 12:02 pm, Jef Poskanzer jef.poskan...@gmail.com wrote: Thanks to @mrblog and SuperTweet I now have a backup plan in case I don't get OAuth implemented by the time Basic Auth goes away. It's a Twitter proxy - you use Basic Auth to talk to the proxy, and it uses OAuth to talk to Twitter. Easy peasy. http://www.supertweet.net/
[twitter-dev] Re: oauth and embedded microcontrollers
Brian, there is no TLS or root CA certificates on this platform. No browser. No X11. No screen or keyboard for that matter. On May 14, 11:13 am, Brian Smith br...@briansmith.org wrote: Mr Blog wrote: For example, the current 'tweet' code binary is 18K bytes. If you can add oAuth in 100K bytes or less, that might work, but that one function would then still be bigger than the entire rest of the application. In fact, the entire file system ROM image, with all the binaries and data is 114K bytes. How large is your TLS stack and root CA certificate database? Regards, Brian
[twitter-dev] Re: oauth and embedded microcontrollers
Thanks. As I note, that is a non-trivial project/barrier. FWIW, I'm putting together a generic service for this application, where a user can oAuth to the site and then create proxy credentials that can be used to tweet etc. http://www.supertweet.net/ Feedback welcome. On May 12, 7:35 am, John Kalucki j...@twitter.com wrote: Why not have the controller proxy through a full-featured webserver that can oAuth in to Twitter? -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, May 12, 2010 at 2:03 AM, glenn gillen gl...@rubypond.com wrote: oAuth is a big burden for microcontroller based devices like this - OAuthcalypse will probably simply kill this app. It seems like way too much overhead to push oAuth code into this little chip. oAuth alone would probably exceed all the rest of the application code on the device combined. I couldn't find anything on the blog or the related sites given examples of the code being used to run this GarageBot other than it was running on uClinux. What code/libraries (if any) are you presently using to connect to the API? The curl guys are working on building oauth support direct into curl, so that should provide a fallback for these kind of apps. You could probably use curl now provided you had a way of generating the oauth_nonce parameter (http://oauth.net/core/1.0a/#auth_header). If you could divulge a little more about your setup, and what kind of constraints you have to work within, we might be lucky enough to have someone in this group that can think of a solution. -- Glenn Gillen http://glenngillen.com/
[twitter-dev] Re: oauth and embedded microcontrollers
Hi Glenn, FWIW, the application and platform is extremely small and lightweight - there is nothing as powerful or huge as 'curl' there. It is all raw C code, stripped down libraries, etc. measured in K-bytes, not Megabytes, to say nothing of Gigabytes. For example, the current 'tweet' code binary is 18K bytes. If you can add oAuth in 100K bytes or less, that might work, but that one function would then still be bigger than the entire rest of the application. In fact, the entire file system ROM image, with all the binaries and data is 114K bytes. On May 12, 2:03 am, glenn gillen gl...@rubypond.com wrote: oAuth is a big burden for microcontroller based devices like this - OAuthcalypse will probably simply kill this app. It seems like way too much overhead to push oAuth code into this little chip. oAuth alone would probably exceed all the rest of the application code on the device combined. I couldn't find anything on the blog or the related sites given examples of the code being used to run this GarageBot other than it was running on uClinux. What code/libraries (if any) are you presently using to connect to the API? The curl guys are working on building oauth support direct into curl, so that should provide a fallback for these kind of apps. You could probably use curl now provided you had a way of generating the oauth_nonce parameter (http://oauth.net/core/1.0a/#auth_header). If you could divulge a little more about your setup, and what kind of constraints you have to work within, we might be lucky enough to have someone in this group that can think of a solution. -- Glenn Gillenhttp://glenngillen.com/
[twitter-dev] oauth and embedded microcontrollers
I have a device that tweets using the API. It is a microcontroller that is hooked to garage doors http://www.toyz.org/GarageBot http://www.toyz.org/images/GarageBot_sm.jpg It is a small box mounted on the wall in the garage as shown in the photo. Unlike a full PC, it has no hard drives and draws very little power. There is no screen or keyboard. All interaction is via the net. Plug it in and it boots and starts doing its thing. You don’t need to think about it. I added LEDs to provide some indication that the device was running. oAuth is a big burden for microcontroller based devices like this - OAuthcalypse will probably simply kill this app. It seems like way too much overhead to push oAuth code into this little chip. oAuth alone would probably exceed all the rest of the application code on the device combined. It's too bad Twitter doesn't provide a way for the user to authorize Basic Auth for their own Twitter ID under certain terms, or some other lightweight Twitter API option. By forcing oAuth, Twitter has substantially raised the bar for API interaction and particularly for embedding Twitter into lightweight devices. Twitter used to be a uniqely lightweight API - not anymore.
[twitter-dev] Re: Upcoming changes to the way status IDs are sequenced
The ability to create apps like http://www.tweespeed.com/ as a result of a few quick APIs to get the difference between two status IDs is really nice. Perhaps even if status IDs are not sequential there could be some kind of a an API method like tweetCount(firstID, secondID) that if given two statusIDs the API returns the number of tweets between these two? -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Introduce yourself!
Hi Folks, David Beckemeyer here, founder of BDT.COM, SF Bay Area ISP and consulting firm during in the 80's - 90's and founding CTO of EarthLink 1995-2005. http://www.bdt.com/david/index.html http://www.linkedin.com/in/davidbeckemeyer Twitter mashups include Taglets.org and Twitmart.org (which is under a re-design/restart phase).
[twitter-dev] enumeration of time_zone values
Does Twitter document the possible values of the time_zone field? The values I see do not work directly to get the user's time zone, and I'd like to map to UNIX times zones, or Java time zones. I can (almost) use the utc_offset value, but that doesn't help me know if this particular user is in an area that obeys daylight saving time, so that I can display time in that user's native local format. 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.
[twitter-dev] Re: What tools do you use?
Twitter4J - a Java library for the Twitter API - is really nice: http://twitter4j.org The author, Yusuke Yamamoto @yusukeyamamoto is very active, quick to fix bugs, and stays current with rapidly evolving Twitter API. Highly recommended. 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.
[twitter-dev] Re: trying gistinc TwitterClient with Streaming API - having issues with socket leak
I moved to Twitter4J Streaming - so far so good.
[twitter-dev] Re: Twitter Update, 8/9 10am PST
search.twitter.com is not working for me from either API or directly in the browser. Is it working for others? If I am blacklisted, how does one go about getting it fixed?
