What Happens When A Twitter Client Hits The Token Limit • Hacker News Board

Re: What Happens When A Twitter Client Hits The Token Limit

#181

Post by aviswanathan » Sat, Nov 17, 2012, 4:14 PM UTC

Firehed wrote: post #147

jcromartie wrote: post #134

Earlier quoted context omitted.

The thing I don't get is: why build a Twitter client? Doing anything remotely useful with Twitter involves building something really substantial on top of the stream of tweets and users.

Hardly. I find Twitter's official clients' UIs atrocious, and happily paid for a third-party's implementation with roughly the same functionality (TweetBot, if you care). I don't find data mining of mostly-mundane content terribly interesting, with the exception of people posting photos of their debit cards ( https://twitter.com/needadebitcard )

Literally lol'd when I saw the needadebitcard feed.

Re: What Happens When A Twitter Client Hits The Token Limit

#182

Post by javajosh » Sat, Nov 17, 2012, 4:44 PM UTC

pteredactyl wrote: post #168

javajosh wrote: post #164

Earlier quoted context omitted.

I don't know, I think it's stupid to allow any private company to control the worlds data, as Twitter, Facebook, and to some extent Google are attempting to do. To expect these for-profit companies to act in any way other than "unilaterally" is naive. If you think that they violated the terms of service, then you should sue them for fraud - or if that's too expensive, make it clear that you think they are engaging in…

I blame Wall Street. Endless growth ($), forever. I like the open web you allude to. However, bills gotta get paid.

Well, Wall Street is a totally different problem - one that is essentially an expression of systemic moral hazards that are present in our legal and banking systems. Wealth = responsibility and yet people are content to just put their money anywhere the return is highest. The result is Wall Street.

The open web is not at all anathema to making money! You say, "I like the open web you allude to. However, bills gotta get paid" but would you have also said, about interstate highways, "I like the highway system you allude to, but bills gotta be paid"? No, of course not. Highways enable gobs and gobs of business to be done. Twitter and facebook have built slightly more usable highways alongside the public ones, called them free, and people have gone there in droves. But once the true cost becomes realized, I think people will go back to the public highways - especially when this means that can go anywhere they want, however they want. Twitter is limiting clients, FB is limiting reach. Both companies are merely very expensive usability innovators on how users like to interact with the public web, in my opinion.

Re: What Happens When A Twitter Client Hits The Token Limit

#183

Post by pteredactyl » Sat, Nov 17, 2012, 6:12 PM UTC

javajosh wrote: post #182

pteredactyl wrote: post #168

Earlier quoted context omitted.

I blame Wall Street. Endless growth ($), forever. I like the open web you allude to. However, bills gotta get paid.

Well, Wall Street is a totally different problem - one that is essentially an expression of systemic moral hazards that are present in our legal and banking systems. Wealth = responsibility and yet people are content to just put their money anywhere the return is highest. The result is Wall Street. The open web is not at all anathema to making money! You say, "I like the open web you allude to. However, bills gotta g…

I like your words. It's not a different problem. Doubly said "expression of systemic moral hazards" leak into these successful platforms. They get fat and then formally hire 1000x more inhouse devs, biz, and design folks when they could ad hoc pay the people who were there from the beginning. Or new people who spring up and bring the platform forward. It's creativity in contracts the status quo is lacking.

I am curious - where are the "public highway" equivalents of Twitter or Facebook? Who owns the infrastructure all this data is passed through? It's definitely not publicly owned. In my opinion, your analogy is mismatched.

Re: What Happens When A Twitter Client Hits The Token Limit

#184

Post by graue » Sat, Nov 17, 2012, 8:57 PM UTC

kmfrk wrote: post #135

jmilloy wrote: post #85

Twitter: Don't build core-feature Twitter clients, we probably won't approve them. Atta: I built a core-feature Twitter client! Twitter: Sorry, we're not approving your core-feature Twitter client. Who is surprised? How is this news? Were you expecting them to not apply their own rules? It seems like a clear-cut case, and concluding "don't build anything for Twitter" is just throwing a temper tantrum.

It's worth keeping in mind that Marco is/was doubly fucked, because in addition to cracking down on client tokens, quoth section 3b of the new display guidelines: No other social or 3rd party actions may be attached to a Tweet. This was the wording of the section at the famous time of the Twitter blog post describing the Bermuda quadrant of impending developer ostracism. This is what it reads currently: No other soci…

I'm not sure I follow. Isn't the second wording less restrictive than the first? It suggests that social and 3rd party actions dissimilar to Follow, Reply, Retweet and Favorite are now allowed.

Re: What Happens When A Twitter Client Hits The Token Limit

#185

Post by javajosh » Sat, Nov 17, 2012, 10:23 PM UTC

pteredactyl wrote: post #183

javajosh wrote: post #182

Earlier quoted context omitted.

Well, Wall Street is a totally different problem - one that is essentially an expression of systemic moral hazards that are present in our legal and banking systems. Wealth = responsibility and yet people are content to just put their money anywhere the return is highest. The result is Wall Street. The open web is not at all anathema to making money! You say, "I like the open web you allude to. However, bills gotta g…

I like your words. It's not a different problem. Doubly said "expression of systemic moral hazards" leak into these successful platforms. They get fat and then formally hire 1000x more inhouse devs, biz, and design folks when they could ad hoc pay the people who were there from the beginning. Or new people who spring up and bring the platform forward. It's creativity in contracts the status quo is lacking. I am curio…

TCP/IP, DNS, HTTP is the major part of the internet's virtual infrastructure (although you might say that there are others, such as router configuration protocols). The physical infrastructure is rather complicated, and owned by large ISPs which connect to each other and smaller ISPs that connect to one or more large ISPs. The 'last mile' provider collects money for access to this infrastructure.

Free physical access is provided in the US by public libraries. De facto free access is provided by a wide range of retail businesses, such as coffee shops.

With your own device connected to the internet you will have a NAT'd IP address from which you can request anything you want. Unfortunately, until IPv6 becomes commonplace, one has to jump through hoops to expose the device - the most common being some form of dynamic DNS.

At the coffee shop the packets that your computer sends are travelling around the world on de facto public infrastructure. It's true that a bad actor can shut down routes, but the internet is rather cleverly designed to treat a shutdown or reduction as "damage" and simply use a different route.

Re: What Happens When A Twitter Client Hits The Token Limit

#186

Post by vonuebelgarten » Sun, Nov 18, 2012, 1:26 AM UTC

kalleboo wrote: post #150

I'd like to see what would happen if a third-party client just started to use the API token extracted from the official client. What could they do?

Technically nothing, I think. It will be nice to see clients with an option "Use you own tokens" and the official client token widely available for use.

For instance, I'm thinking about this for my integrations -- that's a token Twitter will never ban or throttle.

Re: What Happens When A Twitter Client Hits The Token Limit

#187

Post by pavel_lishin » Sun, Nov 18, 2012, 2:20 AM UTC

mattdeboard wrote: post #94

pessimizer wrote: post #84

Earlier quoted context omitted.

Don't develop for the quirks of any particular browser.

Except for when the browsers implement standards differently, e.g. appcache, localstorage, etc.

I didn't know that different browsers implemented those things differently, aside from the default and maximum amount of space given to localstorage.

Re: What Happens When A Twitter Client Hits The Token Limit

#188

Post by TeMPOraL » Sun, Nov 18, 2012, 12:45 PM UTC

daleharvey wrote: post #175

qq66 wrote: post #73

Earlier quoted context omitted.

That's why we (LiveLoop ) think Microsoft Office, Adobe Photoshop, etc. will all grow to encompass Web Service in the application itself, rather than being replaced wholesale by Web apps the way Google wants you to. LiveLoop is our PowerPoint plugin that makes presentations real-time collaborative without ever having to leave Office -- available at http://getliveloop.com

The line between web apps with offline capability and native apps with online functionality is non existent. Unless by native you mean written in a language that only works on a single platform.

Of course the line is existent and it is clearly visible: the browser as a general sucks in UX compared to what can you easily do with native API of your platform.