We're continuing to experiment with the feasibility of this feature, and SSL
support is one gating factor among a few others. There are future solutions
that we can envision that would obviate the need for this less-than-friendly
model.
Taylor
On Sat, Jul 17, 2010 at 12:35 PM, Abraham Williams
There is an open issue for SSL support on dev.twitter.com -
http://code.google.com/p/twitter-api/issues/detail?id=1665
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [
Excerpts from Cameron Kaiser's message of Fri Jul 16 01:00:55 -0400 2010:
Actually, no. The process creates a completely new app key and secret
cloned from the original one. They do not have anything in common with
each other apart from the name and branding (and the user can change it
later;
So basically Twitter's solution to keep consumer keys out of oss
apps code base is:
- to require a hard coded url, which will be easily found in any apps
source( or by simply scanning one's network traffic ).
- this uri than responds by displaying the consumer key, consumer
secret,
So basically Twitter's solution to keep consumer keys out of oss
apps code base is:
- to require a hard coded url, which will be easily found in any apps
source( or by simply scanning one's network traffic ).
- this uri than responds by displaying the consumer key, consumer
