Sequentiel hashtags and RT pictures

[Simon henrotte]

Hi everyone,

I'm currently working with your api and I have a few questions to ask about the sequential hashtags and the RT pictures.

First question :

I'm trying to use sequential hashtags so I have an array of hashtags/keyword/... and I'm taking the pictures with each hashtags. So If I have 3 hashtags, I have 3 requests to the API. I wanted to know if it's possible to use one request for the 3 hashtags ? I tried by using a coma but it doesn't work.  I tried to add two str in the url but it's not authorized.

Do I have to use one request for one hashtags or is there a way to use one request for the 3 (or more) hashtags ?

Second question :

Sometimes, I have the same pictures 2 times , or more, in the same request. This is RT pictures from someone or something like that. Does your api delete the duplicate / RT pictures from the flow or are they just keep in the flow and we have to delete them manually by a method ??

I have a remark to do about the library provided for the PHP users (https://github.com/teleportd/sdk/tree/master/php). A comment si added in the library about the location. The class says that we have to use an array for the location but when you do it the parse function to create the query give us a bug and think that we have 4 locations because it parse the array and return 4 values.

I figured it out by using a simple string like the other and it works perfectly( If you want the sample code and the modification about the class, ask me and I'll upload it with pleasure). 

I also added an urldecode for the reading of the url in the log but this is not necessary (It's easier to read the query during the tests.).

Thanks u in advance.

Simon

[Stanislas Polu]

Hi Simon,

1) The OR operator is not available yet. We're planning on adding it very soon but for now you'll have to run multiple searches. We'll make 

2) We're normally filtering retweets (both native retweet and textual RTs), but some part of the filtering is an heuristic so it's not 100% perfect. Additionally, sometime users repost the pictures under a new id, in which case they are considered two different pictures by our infrastructure. If the same photo is reposted somehow, the information is merged under the same document in our search engine.

> When a new comment / or post is detected for a same picture id: the information is merged in the /search API. The picture is reposted on the /stream API.

3) Thanks for that bug report on the PHP driver. I'd love to have a sample code so that I can look into it asap and come back to you.

Finally, would it be possible for you to describe in a few lines how you're using the API, we'd love to know!

Thank you so much Simon for your feedback/questions. Hope this email helps!

Best,

-stan

--

Stanislas Polu 

Mo: +33 6 83 71 90 04 | Tw: @spolu | http://teleportd.com | teleportation is cool

[Stanislas Polu]

1) => I did not finish my sentence. We'll make sure to get in touch with you as soon as it's in production.

Best,

-stan

--

Stanislas Polu 

Mo: +33 6 83 71 90 04 | Tw: @spolu | http://teleportd.com | teleportation is cool