[twitter-dev] Re: A new permission level
For some developers it's not just a pain in the you know what, it's a case of it simply not working. @janole explained how it just doesn't work with symbian. For me, and adobe air app, it's a pain, but we can get over the inconvenience - although it's always nice to have a bit more time. I think 8 to 12 weeks should be standard for changes of this magnitude whenever possible. On May 19, 1:44 pm, Damon Parker cartmet...@gmail.com wrote: In any security or permissions context the default should be the most secure and least amount of permissions to get the job done. That is Computer and Network Security 101. A user must explicitly configure more loose permissions on their own after understanding the implications. This is the way computer network security is and always has been done. This is part of the reason Linux/Unix et al is way more secure than Windows ever could be. Just because a user isn't sophisticated enough to configure more lax permissions to get their needs met isn't a reason to default to lower the security context. This is what FB did _completely_ wrong when they updated their permissions system. They defaulted everything to being completely open, accessible and public for purely selfish reasons. They wanted to keep more user data 100% public thus increasing the amount of public and free (as in $ to FB) user-generated content created every day. More pageviews, more pics, more comments equals more ad revenue for them. Even though it's a pain in the ass for developer's to rework their apps and re-auth it's the right thing to do for the end user and the overall safety of the community. I commend Twitter for doing the right (even if unpopular) thing in this case. Damon On Thursday, May 19, 2011 at 1:50 AM, janole wrote: Hi Matt, thanks for your feedback. I think the following paragraph can't be generalized, though: Why will you not grandfather existing applications into DM access? Grandfathering all existing read/write tokens assumes they all wanted access to DMs. The feedback we’ve had from users and developers tells us otherwise. We want to give users the opportunity to make an informed choice. -- 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: Recurring Tweets
Thanks Matt, The thing is that the automated rules doesn't actually mention it anymore. I swear it used to... Is there no place that just says Yes it's allowed or No it isn't. Or, is what you are saying, that it is subjective? We are very careful about what features we put in so we like to have a resource to go to without having to ask a...@twitter.com every single time - as it's absent from the links you provided is there such a resource? Or am I missing it? Thanks! ~Tammy On Mar 7, 6:55 pm, Matt Harris thematthar...@twitter.com wrote: Hi to you both: Ken: The API should be rejecting the duplicates. Do you have an example where the duplicate is being allowed through? Tammy: The guidelines for automated Tweets can be found on our support site. Some helpful resources are: http://support.twitter.com/articles/18311-the-twitter-rules which links to our Automated Rules and Best Practices: http://support.twitter.com/entries/76915 If you have any specific queries about policy and whether what you plan to do is allowed or not please contact our policy team. You can reach them through the email address: a...@twitter.com Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Mar 7, 2011 at 9:03 AM, Ken D. k...@cimas.ch wrote: Similarly, I have noticed that an exact duplicate tweet is no longer systematically rejected. Our CMS was set up to tweet new content items when they are first viewed by a visitor. If two visitors view the same new item at nearly the same time, two tweets are sent. Until recently, one would be rejected. Now, both are published and we have to delete the duplicate to avoid looking stupid. This behaviour seems to have changed 1-2 months ago. On Mar 7, 4:17 pm, Tammy Fennell tammykahnfenn...@gmail.com wrote: Hi There, I was just scanning the twitter automation rule and it doesn't say anything about reoccuring scheduled tweets. I swear it used to say it was banned, but has Twitter ammended this now for certain business use? Hope so, it's great functionality when used right! Best, Tammy -- 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: In San Francisco for WWDC? Come to Twitter HQ on June 9th 6-8pm for a @twitterapi meetup!
Hey, any chance of ever having one of these meetups in the UK?! On Jun 7, 12:48 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Mac Devs, This time last year we hosted an informal meetup of WWDC attendees. The event turned into a fun evening so we've decided to do it again. We are inviting WWDC attendees and Twitter Platform developers to our office on Wednesday, June 9, at 6PM. There is limited space, so please register athttp://bit.ly/twitterapi-wwdcif you would like to join. During the meetup, we plan to discuss xAuth, OAuth Echo, give an update on annotations, see demos of iPhone, iPad, and Mac apps and hold an open QA. If you would like to apply to demo your Mac-based app, please fill out this form:http://bit.ly/asvBwI. Around 8 o'clock, we will all head out for a few drinks to close out the evening. We hope to see you there. Hope to see you there! Thanks, The @twitterapi Team
[twitter-dev] Re: Basic authentication
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: What's happening with Tweetie for Mac
Have to admit it is kinda scary to develop for twitter, but maybe when more plans are released we'll understand twitter's plan a bit better. I don't begrudge Tweetie for being acquired, good for them, i'm sure it was a nice deal for them. It's a very narrow tightrope twitter walks though with developers will be interested to see how it all unfolds. On Apr 12, 4:18 pm, TvvitterBug by Applgasm-Apps tvvitter...@gmail.com wrote: So if I got this right, Twitter is going to distribute both Tweetie for iPhone and Tweetie for Mac for free, thus competing with its developer community in the Twitter desktop and mobile client space with free products? And all those other desktop and mobile apps that helped put Twitter on the map, well they're just SOL? And somehow Twitter believes this move is going to encourage developers to continue to develop for a platform that will eventually compete against all but one of them with predatory free pricing? Sounds like you must be looking for developers from the Las Vegas School of Business, not business partners within a symbiotic ecosystem.On Mon, Apr 12, 2010 at 9:40 AM, Ryan Sarver rsar...@twitter.com wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Need a report app button, something isn't quite right with Oauth....
NO but twitter does shut down perfectly good apps all the time... it's very frustrating. On Mar 4, 11:11 pm, Dewald Pretorius dewaldpub...@gmail.com wrote: Why would you want Tweetie or TweetDeck reported and disabled because some users use it to post spammy tweets?? On Mar 4, 5:23 pm,TammyFennell tammykahnfenn...@gmail.com wrote: Hi, this istammyfrom MarketMeTweet... been speaking extensively with Brian Sutorius about this, but wanted to post it here too. Right now apps are going inactive that use OAUTH and sometimes it seems there's no rhyme or reason. there's no well written rules, nothing. Truth is it's going to get even harder to police so why not do it the way you deal with spammy twitter accounts? Just put a report app next the from app under the tweet. Let it be user policed. Much easier for you! If developers start getting their apps shut down willy nilly, people are going to stop developing for twitter, simple as that... Other idea is to do certified apps, and push the heck out of those Let me know if i can be of any help! -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Need a report app button, something isn't quite right with Oauth....
Hi, this is tammy from MarketMeTweet... been speaking extensively with Brian Sutorius about this, but wanted to post it here too. Right now apps are going inactive that use OAUTH and sometimes it seems there's no rhyme or reason. there's no well written rules, nothing. Truth is it's going to get even harder to police so why not do it the way you deal with spammy twitter accounts? Just put a report app next the from app under the tweet. Let it be user policed. Much easier for you! If developers start getting their apps shut down willy nilly, people are going to stop developing for twitter, simple as that... Other idea is to do certified apps, and push the heck out of those Let me know if i can be of any help!
