Twitter Should Shut Me Down • Hacker News Board

Re: Twitter Should Shut Me Down

#51

Post by R41p4t4ng » Thu, Apr 25, 2013, 3:30 PM UTC

I agree

Re: Twitter Should Shut Me Down

#52

Post by abductee » Thu, Apr 25, 2013, 3:30 PM UTC

you don't need more vms to get around their rate limit, you just need to query their api using a clientside language like javascript, that way the ip twitter gets is the ip of the user, not your servers. The company I work at has awesome search, so I have a tool which grabs tweets from individual user's streams (if a customer has an issue with my product and tweets about it I like to search their public twitter stream to see if they've mentioned us or our competitors lately). My script is a python one using httplib, but I realized that I could just as easily make these queries using jquery and send them anywhere I like. This moves the rate limit from your server's ip to the user's ip. If a bunch of people are using your product from the same office it could be a bit of an issue but you could probably detect that (with their 420 chill out code) and use one of your vms ips until that office's ip cools off again. That'd probably make your overhead quite a bit cheaper I'd imagine.

Re: Twitter Should Shut Me Down

#53

Post by mseebach » Thu, Apr 25, 2013, 3:30 PM UTC

There is another flaw in the business model: It feeds off the assumption that when someone favourites one of your tweets, it's because a person liked it, not a bot trolling for followers. I suspect the reason Twitter Ads is 20x more expensive for a follower is that it explicitly states that it's a "promoted tweet" and that throws up all kinds of guards. Once that cat is out of the bag, the cost to acquire a follower using the favourite-method is going to go up.

Re: Twitter Should Shut Me Down

#54

Post by R41p4t4ng » Thu, Apr 25, 2013, 3:30 PM UTC

R41p4t4ng wrote: post #51

I agree

Me too

Re: Twitter Should Shut Me Down

#55

Post by Finster » Thu, Apr 25, 2013, 3:31 PM UTC

macspoofing wrote: post #16

It's amazing how much devs want to build on top of Twitter. There's got to be an opportunity for Twitter to monetize that instead of fighting it and pissing everyone off. Why can't they just have some reasonable fees for API access?

If they put a paywall on their IP, then they'd be bound to have a reasonable support structure in place.

No one in their right mind would want to support the Twitter or Facebook API's...

Re: Twitter Should Shut Me Down

#56

Post by chanux » Thu, Apr 25, 2013, 3:31 PM UTC

niggler wrote: post #15

mathiasben wrote: post #11

Earlier quoted context omitted.

https://followgen.com/

SSL cert issues (according to chrome for ipad)

I checked it here https://www.digicert.com/help

And the result is http://imgur.com/pXVWaue

Hope the author finds this and fixes it.

Re: Twitter Should Shut Me Down

#57

Post by R41p4t4ng » Thu, Apr 25, 2013, 3:32 PM UTC

R41p4t4ng wrote: post #54

R41p4t4ng wrote: post #51

I agree

Me too

Whew! I thought I was the only one!

Re: Twitter Should Shut Me Down

#58

Post by R41p4t4ng » Thu, Apr 25, 2013, 3:33 PM UTC

Anderkent wrote: post #30

niggler wrote: post #15

Earlier quoted context omitted.

SSL cert issues (according to chrome for ipad)

Chrome on linux is happy with it.

I use Chrome

Re: Twitter Should Shut Me Down

#59

Post by adventured » Thu, Apr 25, 2013, 3:33 PM UTC

The problem with the approach of wanting to get caught, is the assumption that Twitter is going to care whether your approach is superior to their Twitter Ads approach. They will not care, judging by their past history. They'll most likely shut you down and go about their business with Twitter Ads. These days Twitter is an extraordinarily rigid company when it comes to anything outside their borders.

Re: Twitter Should Shut Me Down

#60

Post by tehwebguy » Thu, Apr 25, 2013, 3:34 PM UTC

This is cool!

An option that is probably more likely to be API TOS friendly is to show the user relevant tweets and suggest that they favorite, rather than auto-favoriting them.