That's really unfortunate. Any chance someone could give us more
insight into this? @themattharris? @episod? @raffi?
On Nov 5, 1:21 am, Abraham Williams <4bra...@gmail.com> wrote:
> Looks like they changed it. Maybe it didn't scale.
>
> Abraham
> -
> Abraham Williams | Hacker Advocate
Looks like they changed it. Maybe it didn't scale.
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Thu, Nov 4, 2010 at 19:11, Orian Marx (@orian) wrot
Well, I was super excited to try this out, but it seems like this
endpoint has changed to only return "related" tweets that pretty much
aren't related at all. They're just recent tweets to / from the users
mentioned in the original tweet, not replies to the original tweet.
I have no idea why this
Will there been anything in the tweet payload to let us know that it
has replies, or will we need to make requests to the related_results
just to find out?
Sort of thing I was thinking was in the timeline you have a tweet
along the lines of "Dear lazy web, where's the best place to go for
pizza in
I guess unless you are allowed into the new twitter you account
doesn't have access to this API. I am getting a 401 unauthorized
currently.
On Sep 20, 9:37 pm, Vega wrote:
> Wow! Thanks to Abraham and Taylor for the quick replies. I will
> cautiously try the new api.
>
> Cheers,
>
> Edgardo
>
> O
Wow! Thanks to Abraham and Taylor for the quick replies. I will
cautiously try the new api.
Cheers,
Edgardo
On Sep 20, 7:05 pm, Taylor Singletary
wrote:
> Outstanding. I hadn't even realized this particular API was being made use
> of yet here.
>
> This, and a number of other interesting new AP
