> no sane client would ever use them Unfortunately, that's not the case. From RFC 5246: Note: some server implementations are known to implement version negotiation incorrectly. For example, there are buggy TLS 1.0…
That'll teach me to post late at night. I forgot wildcards existed. I was thinking that (if I built tumblr) they would do subdomain searching at the DNS level to avoid hitting their database. Makes it even worse if they…
That's pretty bad. Admittedly, they update their zone very frequently (every time a user signs up/changes name/deletes themselves), but you'd think they would have an independent secondary DNS provider somewhere.
Crashed for me too, twice. EDIT: A colleague is seeing it too.
Just tried it on my iPad 2 and (in portrait) got 1004x768. I couldn't get it to change with the number of tabs open.
OP probably didn't disable dropbox speed limiting - this is the default: http://i.imgur.com/wTWzG.png
> no sane client would ever use them Unfortunately, that's not the case. From RFC 5246: Note: some server implementations are known to implement version negotiation incorrectly. For example, there are buggy TLS 1.0…
That'll teach me to post late at night. I forgot wildcards existed. I was thinking that (if I built tumblr) they would do subdomain searching at the DNS level to avoid hitting their database. Makes it even worse if they…
That's pretty bad. Admittedly, they update their zone very frequently (every time a user signs up/changes name/deletes themselves), but you'd think they would have an independent secondary DNS provider somewhere.
Crashed for me too, twice. EDIT: A colleague is seeing it too.
Just tried it on my iPad 2 and (in portrait) got 1004x768. I couldn't get it to change with the number of tabs open.
OP probably didn't disable dropbox speed limiting - this is the default: http://i.imgur.com/wTWzG.png