Re: [twitter-dev] Feedback wanted on Twitter + iOS

2011-06-28 Thread Paul Haddad
Ryan,

On Jun 28, 2011, at 6:44 PM, Ryan Sarver wrote:

 We'd love to see your apps, give feedback and help make developing on Twitter 
 and iOS 5 a great experience so let us know how we can help.
Simple, open up access to DMs via the API.

---
Paul Haddad
paul.had...@gmail.com, p...@tapbots.com, p...@pth.com

-- 
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


Re: [twitter-dev] Feedback wanted on Twitter + iOS

2011-06-28 Thread Sean Heber
 Ryan,
 
 On Jun 28, 2011, at 6:44 PM, Ryan Sarver wrote:
 
 We'd love to see your apps, give feedback and help make developing on 
 Twitter and iOS 5 a great experience so let us know how we can help.
 Simple, open up access to DMs via the API.

This.

l8r
Sean

-- 
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


Re: [twitter-dev] Feedback wanted on Twitter + iOS

2011-06-28 Thread Tom van der Woerdt
First of all, I think Twitter should make it more clear that this 
implementation is focused on providing Twitter access for non-client apps. 
Think of this implementation as a 'post on Twitter' feature that doesn't 
require any API knowledge or other very complicated stuff. That, and you have 
the ability to get some information about the user. I think it would be a very 
bad thing if this gave the app DM level access as that kind of access is either 
abused or for client apps and this framework isn't for either of those. 

What I noticed while studying the framework (and I'll avoid violating the
Apple NDA here) is that the requests are signed using a fixed pair of 
credentials and always say 'from iOS'. It would be very nice to be able to make 
that say something like 'from appname on iOS' or something. I think that a 
LOT of devs are going to ask for that. 

I have some other ideas but they are improvements over the current framework 
and if I posted them on a public list I'd have to shoot you ;-)

Tom



On Jun 29, 2011, at 1:44 AM, Ryan Sarver rsar...@twitter.com wrote:

 Hey all,
 
 With iOS 5 and the Twitter integration coming in a few months, we have been 
 getting a ton of inbound interest and questions around how to effectively 
 leverage the Twitter integration. We wanted to get your feedback on how we 
 can best support you and your users in developing meaningful experiences. I 
 also hope you have had a chance to dig into the documentation and watch the 
 WWDC session video.
 
 We've heard that it would be helpful for us to provide some standard graphics 
 for use with your upcoming iOS integrations. We wanted to understand what 
 types of buttons and styles would be most helpful. We think the most common 
 use case is going to be Sign in with Twitter (SSO) but let us know what 
 formats would be helpful.
 
 The two use cases that we're hearing the most interest around are:
 
 1. Instant personalization - frictionless Single Sign-on (SSO) and social 
 graph will allow apps to provide a personalized experience to their users 
 with one click. What things can we provide to make this more effective for 
 you.
 2. Distribution - using the build-in Tweet Sheet functionality to post great 
 content from your app out to the Twitter stream where it will drive 
 engagement and clicks back to your application.
 
 Let us know if there are any other resources that would help make your 
 Twitter iOS integrations easier on you or help you provide more value to your 
 users on iOS.
 
 We'd love to see your apps, give feedback and help make developing on Twitter 
 and iOS 5 a great experience so let us know how we can help.
 
 Ryan
 
 --
 Ryan Sarver
 @rsarver
 
 -- 
 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 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


Re: [twitter-dev] Feedback wanted on Twitter + iOS

2011-06-28 Thread Tom van der Woerdt
Absolutely disagree. No DM access via twitter.framework. Would be a major 
threat to the user's privacy.

Tom


On Jun 29, 2011, at 2:05 AM, Sean Heber s...@spiffytech.com wrote:

 Ryan,
 
 On Jun 28, 2011, at 6:44 PM, Ryan Sarver wrote:
 
 We'd love to see your apps, give feedback and help make developing on 
 Twitter and iOS 5 a great experience so let us know how we can help.
 Simple, open up access to DMs via the API.
 
 This.
 
 l8r
 Sean
 
 -- 
 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 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


Re: [twitter-dev] Feedback wanted on Twitter + iOS

2011-06-28 Thread Paul Haddad

On Jun 28, 2011, at 7:09 PM, Tom van der Woerdt wrote:

 Absolutely disagree. No DM access via twitter.framework. Would be a major 
 threat to the user's privacy.

This could be handled by different wording on the Alert Panel that asks for 
permission, or by app id white listing or probably a handful of other solutions.

If this framework is supposedly only going to be used for non client 
applications then can we assume that Twitter for IOS won't have access to it 
either?


---
Paul Haddad
paul.had...@gmail.com, p...@tapbots.com, p...@pth.com

-- 
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


Re: [twitter-dev] Feedback wanted on Twitter + iOS

2011-06-28 Thread Ryan Sarver
Paul, thanks for following up and we definitely understand where you are
coming from.

The current Apple implementation allows for a single permission for all apps
and therefore we have to err on the side of being less permissive. The vast
majority of the apps will not need DM read access and we need to optimize
for that.

We definitely understand the needs and we're exploring options on our side
to make it happen. stay tuned

--
Ryan Sarver
@rsarver https://twitter.com/intent/follow?screen_name=rsarver



On Tue, Jun 28, 2011 at 4:48 PM, Paul Haddad paul.had...@gmail.com wrote:

 Ryan,

 On Jun 28, 2011, at 6:44 PM, Ryan Sarver wrote:

  We'd love to see your apps, give feedback and help make developing on
 Twitter and iOS 5 a great experience so let us know how we can help.
 Simple, open up access to DMs via the API.

 ---
 Paul Haddad
 paul.had...@gmail.com, p...@tapbots.com, p...@pth.com

 --
 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 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


Re: [twitter-dev] Feedback wanted on Twitter + iOS

2011-06-28 Thread Ryan Sarver
Tom, by the time this launches all apps using TWRequest will get proper
attribution like from YourApp on iOS :)

--
Ryan Sarver
@rsarver https://twitter.com/intent/follow?screen_name=rsarver



On Tue, Jun 28, 2011 at 5:07 PM, Tom van der Woerdt i...@tvdw.eu wrote:

 First of all, I think Twitter should make it more clear that this
 implementation is focused on providing Twitter access for non-client apps.
 Think of this implementation as a 'post on Twitter' feature that doesn't
 require any API knowledge or other very complicated stuff. That, and you
 have the ability to get some information about the user. I think it would be
 a very bad thing if this gave the app DM level access as that kind of
 access is either abused or for client apps and this framework isn't for
 either of those.

 What I noticed while studying the framework (and I'll avoid violating the
 Apple NDA here) is that the requests are signed using a fixed pair of
 credentials and always say 'from iOS'. It would be very nice to be able to
 make that say something like 'from appname on iOS' or something. I think
 that a LOT of devs are going to ask for that.

 I have some other ideas but they are improvements over the current
 framework and if I posted them on a public list I'd have to shoot you ;-)

 Tom



 On Jun 29, 2011, at 1:44 AM, Ryan Sarver rsar...@twitter.com wrote:

 Hey all,

 With iOS 5 and the Twitter integration coming in a few months, we have been
 getting a ton of inbound interest and questions around how to effectively
 leverage the Twitter integration. We wanted to get your feedback on how we
 can best support you and your users in developing meaningful experiences. I
 also hope you have had a chance to dig into the 
 documentationhttps://developer.apple.com/library/prerelease/ios/#documentation/Twitter/Reference/TwitterFrameworkReference/_index.html%23//apple_ref/doc/uid/TP40011014and
  watch
 the WWDC session 
 videohttps://deimos.apple.com/WebObjects/Core.woa/BrowsePrivately/adc.apple.com.8270634034.08270634040.8367260933?i=1372307634
 .

 We've heard that it would be helpful for us to provide some standard
 graphics for use with your upcoming iOS integrations. We wanted to
 understand what types of buttons and styles would be most helpful. We think
 the most common use case is going to be Sign in with Twitter (SSO) but let
 us know what formats would be helpful.

 The two use cases that we're hearing the most interest around are:

 1. Instant personalization - frictionless Single Sign-on (SSO) and social
 graph will allow apps to provide a personalized experience to their users
 with one click. What things can we provide to make this more effective for
 you.
 2. Distribution - using the build-in Tweet Sheet functionality to post
 great content from your app out to the Twitter stream where it will drive
 engagement and clicks back to your application.

 Let us know if there are any other resources that would help make your
 Twitter iOS integrations easier on you or help you provide more value to
 your users on iOS.

 We'd love to see your apps, give feedback and help make developing on
 Twitter and iOS 5 a great experience so let us know how we can help.

 Ryan

 --
 Ryan Sarver
 @rsarver https://twitter.com/intent/follow?screen_name=rsarver

  --
 Twitter developer documentation and resources:
 https://dev.twitter.com/dochttps://dev.twitter.com/doc
 API updates via Twitter: https://twitter.com/twitterapi
 https://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 https://code.google.com/p/twitter-api/issues/list
 https://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 https://groups.google.com/forum/#!forum/twitter-development-talk
 https://groups.google.com/forum/#!forum/twitter-development-talk

  --
 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 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


Re: [twitter-dev] Feedback wanted on Twitter + iOS

2011-06-28 Thread Paul Haddad
Ryan,

Thanks for the reply, I'm glad to hear that at least its under consideration.

On Jun 28, 2011, at 8:02 PM, Ryan Sarver wrote:

 Paul, thanks for following up and we definitely understand where you are 
 coming from.
 
 The current Apple implementation allows for a single permission for all apps 
 and therefore we have to err on the side of being less permissive. The vast 
 majority of the apps will not need DM read access and we need to optimize for 
 that.
 
 We definitely understand the needs and we're exploring options on our side to 
 make it happen. stay tuned
 
 --
 Ryan Sarver
 @rsarver

 ---

Paul Haddad
paul.had...@gmail.com, p...@tapbots.com, p...@pth.com

-- 
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