I don't understand why people bend over backward and provide also the grease to FB, Tweeter, AppStore & co?
What Happens When A Twitter Client Hits The Token Limit
71–80 of 188 posts
Re: What Happens When A Twitter Client Hits The Token Limit
#72This is really idiotic. What are they trying to do? Make sure that all the top users flock to App.net or somewhere else?
What do you mean by "top users"? The top users are those with tons and tons of followers and those followers are what make Twitter valuable to them. Not any feature or any good developer relationships. Do you think any celebrity or company is going to want to put their message behind a paywall? I know I'd have a hard time moving enough of my friends to something like App.net to make it interesting for me.
It sucks that Twitter is blocking cool development like this, but they've managed to become "a place where people are" (which is no easy task) and it's a mistake to underestimate that value.
Re: What Happens When A Twitter Client Hits The Token Limit
#73*The effective rule, therefore, is even simpler: “Don’t build anything for Twitter.” Exactly, that's precisely the message they wanted you to have. What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. I don't get anyone is surprised, it's Twitter's ecosystem and if you're duplicating their functionality then it's pe…
> What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. Native > Web, if you do it right. Web has a lot of UX limitations native apps don't have.
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
Re: What Happens When A Twitter Client Hits The Token Limit
#74*The effective rule, therefore, is even simpler: “Don’t build anything for Twitter.” Exactly, that's precisely the message they wanted you to have. What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. I don't get anyone is surprised, it's Twitter's ecosystem and if you're duplicating their functionality then it's pe…
For the past several years the Facebook mobile site has been much better and performed faster than the iphone app.
Why then have people still been using the facebook app?
When you realize the answer to that, you'll understand.
Re: What Happens When A Twitter Client Hits The Token Limit
#75Earlier quoted context omitted.
> What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. Native > Web, if you do it right. Web has a lot of UX limitations native apps don't have.
And native has features that web doesn't have. Growl on OS X, for example.
Ahem: http://www.w3.org/TR/notifications/ (although support isn't great yet: http://caniuse.com/#feat=notifications)
Re: What Happens When A Twitter Client Hits The Token Limit
#76You know, back before APIs were all the rage, people wrote clients for web services by scraping. Twitter really wouldn't be able to do anything about a Twitter client that pretended to be IE9.
Considering how much javascript is involved in current twitter and how often can subtle things in markup change, I'd say it's just too brittle to rely on.
Javascript-filled sites are often cleaner to scrape. Usually, at some point in the process, a nice JSON structure containing all the useful data exists.
Re: What Happens When A Twitter Client Hits The Token Limit
#77*The effective rule, therefore, is even simpler: “Don’t build anything for Twitter.” Exactly, that's precisely the message they wanted you to have. What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. I don't get anyone is surprised, it's Twitter's ecosystem and if you're duplicating their functionality then it's pe…
"What's wrong with using the twitter.com on Windows8..."
What's wrong with everyone using the same web browser? After all, that's exactly what the HTML standard is for, right?
Re: What Happens When A Twitter Client Hits The Token Limit
#78Earlier quoted context omitted.
> What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. Native > Web, if you do it right. Web has a lot of UX limitations native apps don't have.
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
[deleted]
Re: What Happens When A Twitter Client Hits The Token Limit
#79*The effective rule, therefore, is even simpler: “Don’t build anything for Twitter.” Exactly, that's precisely the message they wanted you to have. What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. I don't get anyone is surprised, it's Twitter's ecosystem and if you're duplicating their functionality then it's pe…
>What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8?
Yes. Opening a web browser, typing twitter.com on a phone keyboard, waiting for it to load, logging in on a phone keyboard, then using a mobile site that is built to target as many users on mobile across different devices and versions is much less enjoyable than tapping the twitter icon on a phone and having it open an app built for that phone and that os, then load tweets without further action.
>This is exactly what the web is supposed to do.
That line of reasoning was true before 2008-2010, before smartphones became ubiquitous and before smart phone app experiences became way better than their mobile counterparts. Using the web on a phone is not this great, fun experience. It's typically a pain that involves a lot of typos, and a lot of zooming in, zooming out and scrolling.
Re: What Happens When A Twitter Client Hits The Token Limit
#80*The effective rule, therefore, is even simpler: “Don’t build anything for Twitter.” Exactly, that's precisely the message they wanted you to have. What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. I don't get anyone is surprised, it's Twitter's ecosystem and if you're duplicating their functionality then it's pe…
> What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. Native > Web, if you do it right. Web has a lot of UX limitations native apps don't have.
This may be true for consumer applications, but in enterprise space, Web > Native, easily. While it's much easier to implement functionality in a native application, having something run inside a browser makes it much easier for IT departments to deploy and maintain the product.