[twitter-dev] Allowing users of my social networking site to send their posts to twitter if they want?
I don't think twitter allows integration with other social networks, more specifically to provide content to the other network but I'm not 100% if tweeting solely from another network is allowed I may wanna check the tos for ur specific situation. -- 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] New Photo upload feature: What's new coming on the API side
Arnold, can u say a general time when devs will have access to the upload function? -- 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] oAuth with twitpic or yfrog photo uploads in mobile apps
I am having some trouble integrating either yfrog or twitpic into my app. All the others I see are asking for users names and passwords inside the app, and not using oauth. Is it possible to let people post pictures to their stream using one of these services if the application uses only oAuth and not xauth? I am just assuming the people asking for account and passwords are using xauth. I am trying to integrate it using their new API which uses oauth access tokens. I get this error consistently: Timed out verifying authentication token with Twitter.com. This could be a problem with TwitPic servers. Try again later. -- 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] A new permission level
Did anyone else change their permission on Twitter to rwdm and now their app doesn't show anything? I changed mine, and today I had to reauthorized my account because nothing would load inTo the app. Now it works as usual after I re added my info. Am I the only one? could possibly just be a glitch idk. -- 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] A new permission level
I wish they would just tell the developers to go to hell in a way and let us know they hate us instead of doing these back handed attacks on our apps all the time. This has very very little to do with privacy. Especially for the developer that wants to abuse accounts, this doesn't stop them and serves no real purpose. And putting it to the media as we having access to their DM's is misguided at best. Users now think we are reading their DM's and have access to monitoring their conversations. Which is just crap. This is all about clients having a large control over the twitterverse and the mismanagement of the situation by Twitter execs. Seeing us instead as competitors for the same resource. To disguise this as a security issue is laughable at best and a bit insulting. You have to realize the benefit Twitter is getting to know why they are doing this. It isn't mandatory to break all the client apps to make this change, but its convenient for Twitters current attack scheme on client apps. This will cause mass exodus from 3rd party apps. If you have an app now, you are about to face a wave of pissed off people and bad reviews. There is no way you can realistically avoid this, and they know that. Thats the real meaning for this not because we all wanted it and have been requesting it. No serious Dev would want this. Maybe we want some more security options like Facebook has but we don't want to ruin our relationship with our customers to get it. Twitter should hire some people with sense enough to know how to work with developers. It is no secret that Twitter is at war with the devs, so just tell us yes or no. You want us or you don't. Opening up for developers helped grow Twitter, now they don't need us anymore so they want to weed us out because we control too much of their market again, the same market we all created for them. All this whole thing does is make people weary of client apps with saying we can access their DM's and then a whirlwind of confusion and complaints from our users will guarantee we loose many many users. Think about the normal person that uses tweetdeck. They will load the all, see nothing, and think its broken. If they figure out they need to confirm their info again and accept new permissions, they will be confused and weary as to why they have to do that. There is NO positive outcome for developers or their customers on this. It's a shame that we keep getting slammed with these sneaky back door slaps in the face disguised as some enhancement for users and more laughable, developers. -- 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] A new permission level
Yes janol, everything but twitters official apps will fail. This is specifically aimed at client apps. It is a way to specifically Target client apps because it deals only with DM's which are mostly viewed through client applications. And specifically you said even tweetdeck, I would say especially tweetdeck. They control the largest amount of users outside of the official app and they have been attacking these large clients for some time now. By directly targeting DM's only it should be obvious to everyone why they are doing this. It's presented as some small change but the fallout for clients will be insane. You can't spin the news in a way to make it sound positive or even necessary. It's going to cause a storm of user confusion, deleted apps, bad reviews, complaints to customer support, uncertainty as to why they have to regive permission and religion their accounts. And if you app holds multiple accounts, your in for a nightmare. No one will want to go through putting all their info back into the app. -- 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] A new permission level
I'll give an example for people using multiple accounts. From a customer point of view. I have 12 Twitter accounts, and I use 3 separate clients for different things. When this comes out I will have to re-authorize 36 times over these 3 apps alone. And they won't work until I do. If I was a normal user and didnt hear about the change, what am I going to think about this? I can already tell you I don't want to do it, and its gonna take a lot of time just to get these apps working again. That is for a power user though. Now someone like my mom who uses tweetdeck just to follow celebrities, she will have no clue what happened or why its not working and will be weary when tweetdeck asks her to confirm a new permissions scheme and wonder why they want her info again. Just step back and look at it for what it is and how people will react. We all know what's going to happen. -- 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] A new permission level
Cartmetrix, We don't know for sure what will happen. That's kinda the problem. My guess is we all prepare now by making our app request rwdm access, then when the switch takes effect any token that has been changed with this update will then need to be reauthorized. Not effecting us now, but when that change takes hold, I imagine all our tokens will be basically unauthorized because its an all new permission request, thus forcing each user to accept the new authorizations before they can use the app to communicate with the Api. Also I spoke unclear earlier about all apps failing. It will only be ones that use DM as a feature. Which is basically any client app. I just assume everyone here is effected by the DM permission change in some way, so I say all our apps. But little Twitter apps that just read and write won't be effected at all. Because Twitter isn't afraid of them, just client apps. Also there is no way Twitter will make themselves do the same thing. Lol that would be hilarious. They will in no way form or fashion make all their users go through this process. That would be something I would be fine with. If they want this change, let them do it also lol. But yeah, there is no way they would, because they know exactly what would happen. -- 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] A new permission level
That would be much better cartmatrix but either way, its a negative and unnecessary to take this approach. I am still a bit sceptical that everything will still work fine, just if they try to send a DM it will fail to a 403 error. There is language in the post that suggests both outcomes as possible. I would really like someone from Twitter to clarify exactly what will happen. Very clearly and plainly. I am interested also to here the way they will dance around not doing this themselves as well. They won't, I can guarantee that. I would bet my house on it. Eiyer way the outcome will be negative in any scenario, so they won't want any part of that. But they think its fine if we have to. -- 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] Stream problems on 2010-12-17?
Hi Adam, thanks for your answer. That is about what I'm telling them all the time, but hearing this from someone else makes me feel a little more confident. I wish you and everyone who cares about it a nice christmas time! Frank Adam Green schrieb: I just did a quick count of tweets per day over that period for two systems that track keywords. One looks steady for the 16th. The other glitched on the 16th and had to be restarted. Depending on how you track the streaming API, what I experienced as a failed connection may have been just a temporary loss for you. So the answer is maybe. The fact that software works for a long time with the API is no guarantee it will continue to do so. I look at that as job security. If your bosses are very angry over lost tweets from the API, they have a lot of stress to look forward to. They should deal with it. The data is free, right? If they want no losses, they can pay Gnip. That is what it is there for. On Sat, Dec 18, 2010 at 10:32 AM, Frank Sorro xoo9i...@googlemail.comwrote: Hi Twitter admins and developers, I am developing a social media application which uses a follow stream with track words. At about 21:00 on Dev 16 2010 (UTC), the tweet rate rapidly dropped from about 2800 tweets per minute to about 700, including none we are looking for. Since today (Dec 18th) at about 5:15 UTC, the rate is continuously rising again. This is weird because nothing was changed and we lost the tweets of almost two days. I am quite certain my software didn't have a problem because it worked properly for quite some time, and I didn't change anything during this time. Is it possible that the Twitter Stream API may behave this way? The API status page does not report any problems, but maybe it does not report this kind of problems because I did get Tweets, but not enough and not the right ones seemingly. It would be very good to hear something from Twitter admins or other developers who had the same problem because my bosses are very angry with me anyway right now. If it helps, I'll send more info by e-mail. Thanks in advance and best regards, Frank -- 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 -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- 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] Stream problems on 2010-12-17?
Hi Twitter admins and developers, I am developing a social media application which uses a follow stream with track words. At about 21:00 on Dev 16 2010 (UTC), the tweet rate rapidly dropped from about 2800 tweets per minute to about 700, including none we are looking for. Since today (Dec 18th) at about 5:15 UTC, the rate is continuously rising again. This is weird because nothing was changed and we lost the tweets of almost two days. I am quite certain my software didn't have a problem because it worked properly for quite some time, and I didn't change anything during this time. Is it possible that the Twitter Stream API may behave this way? The API status page does not report any problems, but maybe it does not report this kind of problems because I did get Tweets, but not enough and not the right ones seemingly. It would be very good to hear something from Twitter admins or other developers who had the same problem because my bosses are very angry with me anyway right now. If it helps, I'll send more info by e-mail. Thanks in advance and best regards, Frank -- 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: Connevct to another users application
Hi John, Thanks for answering my question. Do I understand that for every twitter account which I want to use to for automatically twitter I have to register an application. This is what i did right now but I would like to have a more simple construction. I was in the opinion that I could use just one script with the keys in it of the registered application (so it is registered just once) and also the keys of the user in in so it uses the twitter account of that user and the application of another user. Thanks, Frank On 2 sep, 16:02, John Meyer john.l.me...@gmail.com wrote: On 9/2/2010 2:48 AM, Frank P wrote: Hi There, I am a website builder and used a Twitter API to update a Twitter status when a webaster wrote a new newsitem on his site. Now I have to rewrite the api to use oAUTH. I got it working but is it possible to register the application once and let other users make use of that application. I think I need the access token and the ouath token secret of that user to connect. But I can't find those keys in the users profile. When you initially get the user to authorize your website/application, you receive back the token combo. You then need to store those somewhere (database, cookie, etc) for subsequent authorizations. -- 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?hl=en
[twitter-dev] Connevct to another users application
Hi There, I am a website builder and used a Twitter API to update a Twitter status when a webaster wrote a new newsitem on his site. Now I have to rewrite the api to use oAUTH. I got it working but is it possible to register the application once and let other users make use of that application. I think I need the access token and the ouath token secret of that user to connect. But I can't find those keys in the users profile. Hope someone can help me. Thanks, Frank -- 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?hl=en
[twitter-dev] Re: link to disabled acct
When I click on the link the page comes up so folks can see my recent tweets. However, when I try to log in then I get the This account has been disabled message. What I don't understand is that the page mentioned in my first sentence comes up if the account has been disabled. On Mar 5, 10:24 am, Thomas Woolway tswool...@gmail.com wrote: Twitter brings up a page saying something like 'This account has been suspended'. That's the same whether you try to open the user's profile page or an individual tweet. Tom On Fri, Mar 5, 2010 at 11:39 AM, Frank gn...@windstream.net wrote: If an account is disabled will a link to it on a webpage still bring it up?
[twitter-dev] link to disabled acct
If an account is disabled will a link to it on a webpage still bring it up?
[twitter-dev] Re: hits, visits, etc to my tweets
What a bit.ly kink? How do I get and apply one to my tweet? On Dec 17, 10:01 am, Terry Jones te...@jon.es wrote: Frank == Frank gn...@windstream.net writes: Frank Is there any way the number of hits on my tweet? I am interested Frank only in the number of folks who have viewed or visited ... not the Frank names nor the numbers of posts? This might include mostly Frank unregistered viewers If your tweet includes a bit.ly link, you can go to the bit.ly URL with a + sign appended, and see stats there. Terry
[twitter-dev] Re: How do I know when user posted new tweet
On Dec 9, 6:31 pm, John Kalucki j...@twitter.com wrote: You should use the follow parameter on the track resource in the Streaming API. Please correct me if I am wrong, but as far as I know the Streaming API only delivers public statuses. So you would miss the updates of friends who protected their tweets.
[twitter-dev] Re: Twitter API call to statuses/followers.json / xml - protected users out of sync.
Hi, I am experiencing exactly the same behavior and described the problem for the statuses/friends call at http://groups.google.com/group/twitter-development-talk/browse_thread/thread/c63e3288e76ed581 and in issue http://code.google.com/p/twitter-api/issu/detail?id=1121. Other calls to retrieve a status like statuses/friends_timeline or users/show do not have this problem and include new tweets of protected friends right away in the response. Unfortunately they are not useful for the use case of my application. Therefore, I am also very interested in a fix of this problem. Thanks and best regards, Frank
[twitter-dev] Re: new statuses not showing in statuses/friends call (only after long delay)
Still experiencing the problem of several hours delay until a new tweet of a user's friend appears in the statuses/friends response (strangely only for friends with protected statuses). I have opened an issue on this problem including some example responses: http://code.google.com/p/twitter-api/issues/detail?id=1121 I know you must be really busy, but could someone of the Twitter API team please give a short comment on this issue? Thanks, Frank
[twitter-dev] Re: Issue with Search API 'show_user' URL parameter
I'll do that.
Thanks Matt.
On Mar 11, 6:18 pm, Matt Sanford m...@twitter.com wrote:
Hi there,
The show_user=true was only ever intended to work with atom feeds
due to some feed readers not displaying the author. If you need this
to work via JSON please file a ticket
athttp://code.google.com/p/twitter-api/issues/entry
Thanks;
— Matt Sanford
On Mar 11, 2009, at 02:17 PM, Frank wrote:
I'm integrating Twitter's search api with a PHP based application. I'm
using the Search API in JSON format, and I found out that when i
specify 'show_user=true' in the url, user information does not get
returned in the response.
The request i'm making looks like this:
http://search.twitter.com/search.json?q=soccershow_user=truerpp=100
And the response for each entry looks like:
{
text:About to warm up for soccer match.,
to_user_id:null,
from_user:scooter42481,
id:1312698600,
from_user_id:2456152,
iso_language_code:en,
source:lt;a href=quot;http:\/\/www.atebits.com\/software\/tweetie
\/quot;gt;Tweetielt;\/agt;,
profile_image_url:http:\/\/s3.amazonaws.com\/twitter_production\/
profile_images\/68476866\/JSC_normal.jpg,
created_at:Wed, 11 Mar 2009 21:11:26 +
}
Am I doing anything wrong?
Thanks in advance.
