[twitter-dev] Re: Suggestion: Search for [hashtag] but exclude people following [username] from the results
Thanks Cameron. I thought as much. I hope the team take it on as a suggestion. Although I imagine this is quite a demanding task. 1 million plus followers for some accounts would be a big filter! On Aug 2, 2:38 am, Cameron Kaiser spec...@floodgap.com wrote: I've been searching for the below functionality in Twitter's search API: Search for [hashtag] but exclude people following [username] from the results Currently it doesn't seem possible from what I can tell, but I would be very grateful if you do know of a way to achieve this and can share it with me here. No, there is no way to do this specific action from the API. You would have to ask for the results, either from the Search API or the Streaming API, and then do your own filtering based on the follower list you would have already constructed. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- Generating random numbers is too important to be left to chance. ---
[twitter-dev] Getting Mentions using API (not for authenticated user)
Hi Everyone,
I have a script that was happily grabbing all of the @ mentions for certain
twitter handles ('http://search.twitter.com/search.json?q=%40) as per
http://apiwiki.twitter.com/Twitter-Search-API-Method:-search
I just joined the group but as of the past several days, the @mentions have
completely been obliterated. I tried directly from the URL (
http://search.twitter.com/search.json?q=%40brassmonkeynyc) for several
different handles and have received no return information. I have read the
documentation and understand that the new GET statuses/mentions runs off of
the authenticated user. Is there any way to get all of the @mentions for
just a certain handle without requiring authentication or has this
functionality been deprecated? If there is a way and it is not what I posted
in the first line of this email, can someone point me in the right
direction? Any help would be much appreciated.
Thanks!
-Evan
[twitter-dev] Twitter OAuth Example?
Hi everyone, could somebody please help me I need a simple Twitter OAuth example that fully running along with the source code I've tried some example that I found in the internet but all of them is not running and the code is in a mess (unreadable) please help me my brothers and sisters :)
[twitter-dev] Re: Twitter OAuth Example?
could somebody please help me I need a simple Twitter OAuth example that fully running along with the source code 1. What particular language are you using? 2. To better tailor your response, what part of the OAuth process is difficult to understand? - Konpaku
Re: [twitter-dev] Re: Cannot access homepage/timeline for over 24 hours
Hi Everyone, Are you still experiencing this issue of getting a 500 when you load your home page? We had a brief time on Saturday where there were some systematic issues (and scheduled maintenance). Thanks, Taylor On Sun, Aug 1, 2010 at 7:35 AM, xfreakyn cheryl_funkys...@hotmail.comwrote: Hello. I am also experiencing the same problem for over 24hours. I cannot see the timeline and also unable to get in to the home page as the robot page will appear. And when i checked the API status, it seems that the service is disrupted. Please help! Thankyou!
Re: [twitter-dev] Can i hav an Auto Response to Tweets via API.
We have a few rules on automation that are germaine to all who are considering building applications like this: http://support.twitter.com/articles/76915-automation-rules-and-best-practices Taylor On Sun, Aug 1, 2010 at 7:37 AM, Cameron Kaiser spec...@floodgap.com wrote: We can read Tweets using API. But is there anything (Method/API workaround) that lets me reply to Tweets by a predefined msg (viz. I'm on Vacation. Will Get back on Friendship Day) automatically and real time? No, but any number of bots could. However, if you reply to every tweet this way, you are likely to hit the update limit, and Twitter will probably filter the duplicates anyhow. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Yes, but when I try to see things your way it gives me a headache. -
Re: [twitter-dev] Getting all retwitts for a specific twitt
There would be no stable way to accomplish querying for all retweets performed on a specific Tweet using the REST or Search API today. A path to accomplishing this would be through the Streaming API ( http://dev.twitter.com/pages/streaming_api_methods#statuses-retweet ) -- specifically the retweet firehose. By capturing and indexing all retweets, you could query your own index to determine this. Taylor On Sun, Aug 1, 2010 at 8:39 AM, Omri omr...@gmail.com wrote: Hey, i wonder if there is anyway to query twitter to all retwitts performed on a specific twitt. im looking for a method to gather up recursivly all the retwitts originating from a specific twitt so i can line up the full conversation from twitter. thoughts ? Omri
Re: [twitter-dev] Getting Mentions using API (not for authenticated user)
The mentions timeline via the REST API requires authentication as you
noticed. While you can use the search API for this, your results will be
limited by the tweets that enter the Search API's archive (more about what
you won't find in the Search API:
http://support.twitter.com/articles/66018-my-tweets-or-hashtags-are-missing-from-search).
You may want to check out the follow variation of our Streaming API:
http://dev.twitter.com/pages/streaming_api_methods#follow
Taylor
On Sun, Aug 1, 2010 at 11:26 PM, @evanmrose evanmr...@gmail.com wrote:
Hi Everyone,
I have a script that was happily grabbing all of the @ mentions for certain
twitter handles ('http://search.twitter.com/search.json?q=%40) as per
http://apiwiki.twitter.com/Twitter-Search-API-Method:-search
I just joined the group but as of the past several days, the @mentions have
completely been obliterated. I tried directly from the URL (
http://search.twitter.com/search.json?q=%40brassmonkeynyc) for several
different handles and have received no return information. I have read the
documentation and understand that the new GET statuses/mentions runs off of
the authenticated user. Is there any way to get all of the @mentions for
just a certain handle without requiring authentication or has this
functionality been deprecated? If there is a way and it is not what I posted
in the first line of this email, can someone point me in the right
direction? Any help would be much appreciated.
Thanks!
-Evan
[twitter-dev] Image Uploading
Hi there, My name is Dominiek ter Heide and I have a little gimmicky project called Blinkly, slick profile image overlays: http://blink.ly/ Ever since about a month ago I've been experiencing some problems with image uploading through the REST API. I managed to fix this (meaning less failures) by using the V1 API, other developers with this problem should look into this! However, every time I upload an image through the API or through the website even, it scales it down in a strange way. When the aspect ratio wasn't squared, it used to crop it in a smart way. Right now however, black borders are added to all uploaded images. E.g. http://a0.twimg.com/profile_images/1093873780/blink_23.jpg Are the Twitter devs changing this back to the smart cropping like it used to? If so, I will not bother in adjusting my backend and cope with the glitch for now. Sincerely, @dominiek
Re: [twitter-dev] Image Uploading
Hi @dominiek, Here's that state of image uploading and the Twitter API (and website): Up until very recently, image upload via the API or on the site was a bit of a crap shoot -- it was a synchronous process, and if our servers couldn't process the image quickly enough or ran into any problems, it would throw a 500 error. My own personal estimate was that about 3/5ths of the time you tried to perform an image upload operation, you'd get an error. Recently, an engineer began refactoring our image upload process so that it was an asynchronous process. This means that in most cases, we'd acknowledge an image upload as it was received, and unless there was anything particularly problematic about the upload, we'd return a 200 status code, put the image in a queue, and after processing, update the image on record. This means from an API perspective, you now need to check back later to see what the new image URL is. We're still working through these implications, but the move to an async model was a requirement to be able to service these uploads at all. Now, meanwhile when the async service was developed, the image manipulation libraries used were also changed. This is what's resulted in the black bar effect you've noticed. Long story short, we're continuing to iterate on this issue and tweak the image manipulation routines we are using. I'd recommend when uploading images that you assure they are as square as possible before upload, but overall, this is something we (Twitter) need to fix so that its behavior is more deterministic. Taylor On Mon, Aug 2, 2010 at 9:53 AM, dominiek i...@dominiek.com wrote: Hi there, My name is Dominiek ter Heide and I have a little gimmicky project called Blinkly, slick profile image overlays: http://blink.ly/ Ever since about a month ago I've been experiencing some problems with image uploading through the REST API. I managed to fix this (meaning less failures) by using the V1 API, other developers with this problem should look into this! However, every time I upload an image through the API or through the website even, it scales it down in a strange way. When the aspect ratio wasn't squared, it used to crop it in a smart way. Right now however, black borders are added to all uploaded images. E.g. http://a0.twimg.com/profile_images/1093873780/blink_23.jpg Are the Twitter devs changing this back to the smart cropping like it used to? If so, I will not bother in adjusting my backend and cope with the glitch for now. Sincerely, @dominiek
[twitter-dev] Using twitter @nywhere with rest api
This is probably an easy one, but I haven't been able to figure it out, and I can't find anything on the web that points me in the right direction. Is there a way to use @nywhere and the rest api of without forcing the user to log in twice? I like the features of @nywhere, but also need ability to send tweets on the users behalf.
[twitter-dev] Re: Image Uploading
Ah, that makes sense, I'll wait for the black bar effect fixes then. Thanks! On Aug 2, 7:19 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi @dominiek, Here's that state of image uploading and the Twitter API (and website): Up until very recently, image upload via the API or on the site was a bit of a crap shoot -- it was a synchronous process, and if our servers couldn't process the image quickly enough or ran into any problems, it would throw a 500 error. My own personal estimate was that about 3/5ths of the time you tried to perform an image upload operation, you'd get an error. Recently, an engineer began refactoring our image upload process so that it was an asynchronous process. This means that in most cases, we'd acknowledge an image upload as it was received, and unless there was anything particularly problematic about the upload, we'd return a 200 status code, put the image in a queue, and after processing, update the image on record. This means from an API perspective, you now need to check back later to see what the new image URL is. We're still working through these implications, but the move to an async model was a requirement to be able to service these uploads at all. Now, meanwhile when the async service was developed, the image manipulation libraries used were also changed. This is what's resulted in the black bar effect you've noticed. Long story short, we're continuing to iterate on this issue and tweak the image manipulation routines we are using. I'd recommend when uploading images that you assure they are as square as possible before upload, but overall, this is something we (Twitter) need to fix so that its behavior is more deterministic. Taylor On Mon, Aug 2, 2010 at 9:53 AM, dominiek i...@dominiek.com wrote: Hi there, My name is Dominiek ter Heide and I have a little gimmicky project called Blinkly, slick profile image overlays:http://blink.ly/ Ever since about a month ago I've been experiencing some problems with image uploading through the REST API. I managed to fix this (meaning less failures) by using the V1 API, other developers with this problem should look into this! However, every time I upload an image through the API or through the website even, it scales it down in a strange way. When the aspect ratio wasn't squared, it used to crop it in a smart way. Right now however, black borders are added to all uploaded images. E.g. http://a0.twimg.com/profile_images/1093873780/blink_23.jpg Are the Twitter devs changing this back to the smart cropping like it used to? If so, I will not bother in adjusting my backend and cope with the glitch for now. Sincerely, @dominiek
[twitter-dev] Re: Open-source, distributed PHP app and consumer secret
Hi Tom, Thanks for the thoughts. I like your second solution. To host a tweet service on my site (You can use your own server as a service which sends all requests to twitter. ). I spoke with a colleague of mine and his advice was the same. My question (concern) is doesn't this open me up as a potential target for would-be-do-badders and create an additional layer of potential security issues? Michael On Aug 1, 1:21 pm, Tom allerleiga...@gmail.com wrote: I've thought about this a lot myself as well, and haven't really came up with a proper solution either. - You can try encoding all of your code with zend encoder and hope that nobody decodes it. - You can use your own server as a service which sends all requests to twitter. (This would be my solution) - You can simply not care at all about the keys - after all, there is (imo) no real threat in exposing them to customers. - You can let them use the new Twitter extension for open source twitter clients - although I am not sure whether it's ready yet. Tom On Aug 1, 1:49 am, Michael Babcock mjet...@gmail.com wrote: So, I think the solution has to be that the user downloads my app, installs it on their site, then registers my app as their own app with dev.twitter. After which, they will receive their own key secret pair. They will then input their key secret pair into my app which is living on their site, stored in some configuration file or database settings table. This way I don't distribute my secret. They will have to store their own key secret pair, but this wouldn't be different than a site with its own proprietary solution. The only stick point is that I will not get any branding rights on their posts/tweets, as they will have registered the app as their own and will be in control of the post branding. The other option is to host a tweet service somewhere in the cloud. My app, installed on their site, would point to the service and they would have to grant permission to the service to make the tweets to their accounts. I like this second solution because it seems cleaner for the end user to set up and get running. However, this would mean that I would then be responsible for maintaining a service. And frankly, that sounds like a drag on resources. These two are the best solutions I can figure given the circumstances. Normally, I would wait for Twitter to get this sorted, however, I don't want to risk disappointing my user base when the August 16th deadline rolls around. Does these solutions sound viable or am I all wet? Pros, cons, alternatives? Thx. On Jul 27, 7:18 am, Decklin Foster deck...@red-bean.com wrote: Excerpts from Michael Babcock's message of Mon Jul 26 19:28:15 -0400 2010: So, I after spending the day looking through documentation, developer's discussion and testing various OAuth code bits, it is my understanding that there is no secure OAuth solution for open-source PHP developers. But, the August 16th deadline is still looming. I am also concerned about this. Here is the response I got from support: we're continuing to experiment with this feature, and have not made it available further. I apologize for the delay and inconvenience, but keep an eye on our developer talk group for future announcements. I have been watching this list for about a month (prior to checking with support) in case the feature is discussed here before being announced. @twitterapi, could we get some clarification on whether or not something will be ready before the August 16 deadline?
Re: [twitter-dev] Getting Mentions using API (not for authenticated user)
Gotcha,
So basically there is no way to grab only the @mentions for specific
handles? It was working just fine using the Search API until very recently
(past week) so I dont think the search limitations were the issue. Was the
archive purged in the past week? If so, is there any plan to duplicate this
@mention grabbing functionality at any point or will the mentions be
repopulated slowly as the occur?
Sorry to pester, the app I'm working on requires a couple of streams of
specific types (from xHandle, mentioning xHandle) of tweets
On Mon, Aug 2, 2010 at 10:43 AM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
The mentions timeline via the REST API requires authentication as you
noticed. While you can use the search API for this, your results will be
limited by the tweets that enter the Search API's archive (more about what
you won't find in the Search API:
http://support.twitter.com/articles/66018-my-tweets-or-hashtags-are-missing-from-search).
You may want to check out the follow variation of our Streaming API:
http://dev.twitter.com/pages/streaming_api_methods#follow
Taylor
On Sun, Aug 1, 2010 at 11:26 PM, @evanmrose evanmr...@gmail.com wrote:
Hi Everyone,
I have a script that was happily grabbing all of the @ mentions for
certain twitter handles ('http://search.twitter.com/search.json?q=%40) as
per http://apiwiki.twitter.com/Twitter-Search-API-Method:-search
I just joined the group but as of the past several days, the @mentions
have completely been obliterated. I tried directly from the URL (
http://search.twitter.com/search.json?q=%40brassmonkeynyc) for several
different handles and have received no return information. I have read the
documentation and understand that the new GET statuses/mentions runs off of
the authenticated user. Is there any way to get all of the @mentions for
just a certain handle without requiring authentication or has this
functionality been deprecated? If there is a way and it is not what I posted
in the first line of this email, can someone point me in the right
direction? Any help would be much appreciated.
Thanks!
-Evan
[twitter-dev] Re: OAuth page showing opening and ending tag mismatch
I'd assume the language depends on the http Accept-Language header, but just changing that doesn't seem sufficient to trigger the bug. On Jul 27, 3:21 am, Bess bess...@gmail.com wrote: I don't see that error on mobile Twitter page but I am testing it in US. Do you think it is related to callingURL IP Address? Would Twitter process it differently for non-US IP Address on callingURL? On Jul 26, 2:10 pm, Jonathan del Strother jdelstrot...@gmail.com wrote: Hi - thanks for the response. Both the users who have come to us with this problem are non-english speakers - one was definitely viewing it in French, the other claimed to be using English but I kinda suspect a communication problem there... I've not been able to reproduce it, even when setting my phone to different locales - do you have a guaranteed way of reproducing it yet? Any idea what percentage of users see the problem? I've been wondering about sticking a ?lang=en parameter in there till it gets fixed. -Jonathan On Jul 26, 6:49 pm, Matt Harris thematthar...@twitter.com wrote: Hi Jonathan, Our mobile team is aware of this issue and is looking into it. From my tests it looks like it only happens for users whose language is not English. Do you know if these users are viewing the site in anything other than English? Thanks Matt On Mon, Jul 26, 2010 at 12:06 AM, Jonathan del Strother jdelstrot...@gmail.com wrote: Any further progress on this? Is there anything I can get my users to try, to try diagnose the problem some more? -Jonathan On Jul 22, 3:10 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Jonathan, One conjecture I can think of based on the screenshot is that this may be due to the broken image upload issues we were having recently -- but the further reports on the original link you provided suggest otherwise. Looking into this. Taylor On Thu, Jul 22, 2010 at 3:11 AM, Jonathan del Strother jdelstrot...@gmail.com wrote: No takers? On Jul 15, 1:10 pm, Jonathan del Strother jdelstrot...@gmail.com wrote: Hi, We use Twitter Oauth for third party signin. I haven't been able to reproduce this myself, but one of our users is seeing an error page showing this page contains the following errors: error on line 397 column 156: opening and ending tag mismatch:divline 0 andstrong. Someone at Boxcar seems to be having similar problems - http://help.boxcar.io/discussions/problems/455-i-cant-sign-in-in-twitter Anyone else run into this? Any suggestions on fixing it? -Jonathan -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Frequent errors when using OAuth, none when using basic
I sent the following to Twitter support via their web form; they suggested I should post here instead. - I currently have two automated accounts, thethirdstroke and this one (servologyalerts). thethirdstroke tweets every hour on the hour, and has been working fine for a long time. I converted it to using OAuth a while ago, and it continued to work fine. servologyalerts tweets when my nagios installation detects a fault or a fault clears, and has been having problems since I switched it from password authentication to OAuth on 12 July. Since that time, most attempts to tweet get the Something is technically wrong response. However, most test tweets seem to go through without any problem, and reviewing the logs I notice that any alert which is long enough that my script has to truncate it to 140 characters before tweeting, and therefore loses (part of) the packet loss = nnn% which is often at the end of the tweet, goes through fine. I wonder if the problem is that my alerts are somehow triggering spam filtering, which is then returning a Something is technically wrong error message rather than actually saying it's spam filtering. That doesn't seem a likely explanation, though, as the problem started precisely when I switched from basic auth to OAuth - surely OAuth would, if anything, need to do *less* spam filtering. Both automated accounts tweet using the same script, which uses curl to post through a python program called oauth-proxy, which I have altered to listen only on the loopback interface, and which is started up just before each tweet and shut down just afterwards. As mentioned, there doesn't seem to be any problem with the OAuth signing - thethirdstroke posts fine pretty much all the time, while servologyalerts can post test messages and, occasionally, live messages with no problems. It also does not seem to be a problem with OAuth signing requests containing % signs, as I've posted test messages with % signs with no problem. I'd be grateful if you could check any logs you have and let me know if you can see why this problem occurs, and if you can suggest a fix. Thanks for your help. - Update: I have temporarily switched back to using basic authentication for servologyalerts; the errors have stopped and notifications arrive on twitter as expected. Thanks for any light you can shed; and let me know if more information is needed - I didn't think there was any need to copy-and-paste the Something is technically wrong page's HTML here, for example.
[twitter-dev] Re: Twitter OAuth Example?
Yes it is Depending on which 3rd party library. Be ware of the publishing date of those info b/c there has been a lot of changes. I can confirmed that I am able to 1) Oauth in web app PHP 2) Oauth in Samsung bada C++ 3) Oauth in Android SDK 2.1 Java I am confirming that it can be done b/c I get these OAuth working this month using the latest version of Oauth libraries. Unfortunately I wasn't able to show them in the last Twitter hackathon b/c I haven't started working on them at the time. On Aug 2, 7:12 am, Konpaku Kogasa kogasa.l...@gmail.com wrote: could somebody please help me I need a simple Twitter OAuth example that fully running along with the source code 1. What particular language are you using? 2. To better tailor your response, what part of the OAuth process is difficult to understand? - Konpaku
[twitter-dev] lets test OAuth POST using this client
Amy users using this REST client to test OAuth header https://addons.mozilla.org/en-US/firefox/addon/9780/ so we can have a common base to check against
[twitter-dev] Re: Twitter OAuth Example?
Exactly how many developers out there are having troubles with OAuth? I don't hear too many complaints in developer events except many developers are still having UXP issues on OAuth in mobile native app. There is no good solution using OAuth and Callback Out-of-band. On Aug 2, 6:17 pm, Bess bess...@gmail.com wrote: Yes it is Depending on which 3rd party library. Be ware of the publishing date of those info b/c there has been a lot of changes. I can confirmed that I am able to 1) Oauth in web app PHP 2) Oauth in Samsung bada C++ 3) Oauth in Android SDK 2.1 Java I am confirming that it can be done b/c I get these OAuth working this month using the latest version of Oauth libraries. Unfortunately I wasn't able to show them in the last Twitter hackathon b/c I haven't started working on them at the time. On Aug 2, 7:12 am, Konpaku Kogasa kogasa.l...@gmail.com wrote: could somebody please help me I need a simple Twitter OAuth example that fully running along with the source code 1. What particular language are you using? 2. To better tailor your response, what part of the OAuth process is difficult to understand? - Konpaku
