You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I wonder how you would make Twitter without resolving all the templates on the server. Enlighten me :)
You are conflating many things that are simultaneously arbitrary and confused. What “templates” do you think are actually necessary, as opposed to being an arbitrary overcomplex way of doing things? Twitter is a relatively trivial application from a UI perspective.
I mean, traditionally, the way client/server systems work is that the server does the server part and the client does the client part. Having the server do the client part is a bad idea in terms of efficiency as well as quality of experience for the end-user.
The genesis of this whole discussion is the assertion that web people make easy things difficult and slow and have no idea they are doing that because they don’t understand simple and fast, and ... you are kind of just helping to prove the point.
I agree that the bloat is everywhere, but I don't agree that the solution is doing more of the same, just more effectively. Much of the unnecessary complexity is based on treating the browser as an operating system and using JavaScript as a system programming language.
I believe that it is the responsibility of the site owners to ensure that the client do as little work as possible. This simple Twitter page I'm currently at, which has about 3KB worth of text, has a memory footprint above 100MB. This is just wrong.
This is completely backwards. The point of a distributed system is to distribute work so the cost isn’t concentrated unrealistically in a central point. And you want the visuals generated on the client so they can be maximally responsive at e.g. 120Hz with subtle color changes
I believe that the solution is to focus on what we are doing on the server side and optimize one that end - in regards to both what we are doing and how we are doing it. And I do believe treating the browser as a thin client, is a big part of this.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
New website: 