andrewmccall

10 ms·

1. 31.▲
   by andrewmccall 16y ago

   This makes perfect sense. If for example you're accepting 140 characters there is no reason you should have an excessive content-length for that URL.
2. 32.▲
   by andrewmccall 16y ago

   True. Though it's a safe assumption that if you suddenly have a large number of spotty satellite users and they're DOSing your site it's probably something malicious.
3. 33.▲
   by andrewmccall 17y ago

   If you're handing dates straight back into the interface sure, but if you're calling an ajax api or similar it may be better on the client side. Twitter for example, nice dates on the web and in clients, the ajax stuff gives the long ones.
4. 34.▲
   by andrewmccall 17y ago

   I was thinking the same thing, but I'd be willing to be they thought of that. Likely it has more to do with the types of tasks they're doing. If you think about facebook and how it's used, it's mostly a lot of little bits of data. An awful
5. 35.▲
   by andrewmccall 17y ago

   It sounds like a reasonable argument, but it also gives them the right to turn around and tell someone else they can't use it and for some of these really common expressions that's just not right. Also if they're already using it and someon