Earlier in my career, I looked to the HTML5 boilerplate for ideas on how to set up websites. I just grabbed bits I liked and modified them as needed. For a time they had shortened links off of the h5bp.com domain that redirected to descriptions of why certain choices were made. But eventually, the person maintaining that domain let it lapse and someone else bought it. Continue reading post "h5bp links"
Apparently del.icio.us was bought by pinboard and will be switched to read only mode soon. I created an account long ago and have used it off and on to store 1007 bookmarks. Continue reading post "End of del.icio.us"
I've been looking for a short domain to potentially use for permashortlinks. For a domain to be usefully short, it must have both a short TLD and short SLD. Having three characters each would make for seven total characters (including the period) for the domain. Much more than that and it starts to lose its usefulness. There are no one character TLD's (though they'd be great for permashortlinks). Two character TLD's are reserved for country codes. I'm a bit reluctant to use a code for a country I don't live in, and the one I do disallows whois privacy. I'm a bit reluctant to decide that my address, phone number and email address will be "perma"nently available for all to see (assuming I keep the permanent promise of of permashortlinks). So three characters have been where I've been doing most of my looking.
There are a number of good lists of available TLD's. Indiewebcamp has a list of options with a brief blurb on their fitness and possible problems. It only has country code domains though. United Domains has a list with current TLD's and their prices plus soon to be available TLD's. It has a page for each with some information about the TLD and marketing-speak thoughts on uses. Name.com has a list with per-TLD pages as well that are often more brief. It's hard to parse these lists to find just the short ones though.
I found two plain-text lists of TLD's (IANA's and publicsuffix's), which got me to thinking that I could parse these to find just the ones with three characters. I wrote a script in PHP and modified it to handle any number of characters. It looks like:
Continue reading post "Finding short TLD's"I've been interested in Indieweb lately, and have been looking for a good domain for permashortlinks. The article goes into more detail, but advantages include:
I have a domain that's six characters total (SLD + dot + TLD), but I'm not sure I like it: It has a '0' in place of an 'o' (might confuse people); is on a TLD that disallows whois privacy; and doesn't feel as representative of me as some others I've thought of. It's hard to find good short domains. One reason, of course, is that short domains are desirable and are taken more quickly when available. Another is that ICANN and predecessors traditionally seem to have been reluctant to allow short SLD's. One and two character SLD's are often reserved or "premium".
ICANN could make available single character TLD's for URL shortening purposes, and make available on them SLD's of one or more characters. This would make available, using normal ASCII domain rules:
Continue reading post "Idea: Single character TLDs for permashortlinks"XHTML 2 was going to allow use of the href attribute on any element, allowing for block level anchors and eliminating repetition of the same anchor in some cases or unnecessary additional tags in others. This really made sense, since the <a> tag is just a span, but the only span with an added ability of linking to somewhere else. There is really no special semantic meaning to the <a>, and all links on a page could be found in parsing by finding tags with the href. In the early days of the development of HTML 5, the "href anywhere" approach was discussed, and I was excited thinking it was going to be part of HTML 5. At the time, that was the most interesting thing about HTML 5 to me. But "href anywhere" would mean all previous browsers would not be able to see links at all (besides for the ones put in <a> tags for some reason), so the idea was scrapped. Instead, the HTML 5 creators took advantage of an against-spec ability that current browsers already had: block level anchors. Browsers at least back to IE 6 will happily make "flow content" placed in an <a> tag into a link.
I was somewhat unhappy that we had to kowtow to current browsers by preventing such a wonderful ability as href's on any tag, but the backwards compatibility thing is huge in real world development (though I would have just done some server side browser sniffing to output the <a>'s in appropriate places for incompatible browsers) and the solution handles most use cases, though with a bit of extra markup. Over time, I began thinking that perhaps I could just use <a>'s in place of any tags that have no semantic meaning (ie <div> and <span>), only using href when required and thus have href available most anywhere.
Continue reading post "HTML5 href Anywhere Attempt"