ICANN ( the Internet Corporation for Assigned Names and Numbers ), the people responsible the IPv4 & IPv6 address space and the top-level domain ( TLDs ) space, are rolling out a large list of new top-level domains. Tired of being limited to the traditional .com / .net / .org and country domains? Soon you’ll have a bizarre set of new possibilities.
Here is a sample of what is coming:
Some of these have obvious categories, like .recipes for recipe web sites. Others I think are just random names people pulled out of a hat, like .ninja.
The title of this post, Dot Kitchen Sink, was meant to be a joke, but there is some truth to it. On the list of new TLDs is .kitchen, so you could have a email@example.com email address or joseph.kitchen/sink/ as a web site. Telling someone your email address in a voice conversation is only going to get harder.
Time to go all the way with dot.dot just to make things even more confusing :-)
Ever get the feeling that it is going to be a bad year for TLS implementations?
First the Apple iOS / Mac OS X TLS bug, then a GnuTLS bug. Gives me the feeling that we are just waiting for more of these to be discovered.
Ultimately this will be a good thing, but painful to get through.
ZDNet reports that over 30 Comcast mail servers were compromised recently:
NullCrew FTS used a Local File Inclusion (LFI) exploit to gain access to the Zimbra LDAP and MySQL database — which houses the usernames and passwords of Comcast ISP users.
I am a Comcast customer and I haven’t heard anything from them about this. Which is line with what ZDNet has reported, that they haven’t been forth coming with details yet.
Off I went to change my Comcast password. That is when I ran into this disappointing password policy:
The good part is that they do support special characters, which is more than I can say for some other password policies I’ve seen.
The bad part is that it only supports up to 16 characters and doesn’t allow spaces. That suggests that Comcast might be storing the passwords in plain text. Which of course would be bad.
John Gruber has posted an update to his Regex Pattern for Matching URLs post. The pattern itself now lives at https://gist.github.com/gruber/8891611.
Related to this is a review of URL validation regular expressions. It compares 13 different methods, but only for URL validation, not necessarily matching.
I’m not super keen on the idea of having a list of TLDs as part of the regex, since the number of TLDs is continuing to grow. I do like that Gruber’s regex includes comments in it, that is really helpful for longer, more complex expressions.
Mark Nottingham on Nine Things to Expect from HTTP/2.
If you have any interest in the future of HTTP then mnot’s blog is well worth reading.
Drew McLellan wonders Why is Progressive Enhancement so unpopular?:
Simon St. Laurent touched on this as well in Web Application Development is Different (and Better):
Let’s extend the Web and help it do more – but let’s do that by valuing the many strengths it already brings.
Intentional or not the last few years have brought us a strong push to ignore the idea of progressive enhancement. In many cases that has been to our detriment.
Ever wonder what Steve Jobs would have looked like as a four year old blond kid? Now you know.
Saw this in the parking lot during the SkiPHP conference.
Marco Arment on forcing a link to open in a new tab or window (emphasis is mine):
Most people know how to open your article’s outbound links in new tabs or windows, especially readers of a tech site. Modern browsers make multiple-tab/window management very easy for almost everyone who wants them, and the people who don’t know how to manage them usually don’t want them.
Up until last year I would have agreed with him.
What changed was watching a friend browsing the web and noticing that they never opened links in new tabs, even though it would have made things easier. I asked if they were familiar with using the middle click on a mouse to open the link in a new tab ( this was Firefox on a Windows system ). I wasn’t surprised when I got a no back.
I took a few minutes to walk them through middle clicking to open links in a new tab and general tab management. They were thrilled with this new piece of information, declaring how much this had changed ( for the better ) their web browsing experience.
This is only one data point, but it reminded me to very careful about my assumptions of what people know, especially for things that I take for granted. The little voice in your head that says “everyone knows that” can easily be wrong.
It simply isn’t true that every single Internet user has already made up their own personal policy on forcing links to open in a new tab or window. In some cases they didn’t even realize they had that feature in the first place.
For web sites with a mostly technical audience I think Marco is right, those are visitors who likely already know what they want and don’t want. But believe it or not there are still people who use computers and browsers to do things that don’t involve reading about computers and browsers.