I own a 3-letter domain with a 2-letter TLD and still spells my family name. Many of my friends finds it cool when I share links via that domain. The links are indeed easy to remember but it comes at a higher yearly cost of renewal and I had forgotten to renew twice. Luckily, I was able to re-register them (nobody wants it, ;-)). Example https://oin.am/rr/
My name is Dan Blows, and my domain is da.nblo.ws, which I thought was the coolest thing ever. Most people are confused or don’t even notice it.
Short URLs: Why and How
151–160 of 172 posts
Re: Short URLs: Why and How
#152Earlier quoted context omitted.
I used to have a mail address along the lines of d@nblows.com But beware, single letter local parts are not universally supported by web sites. Microsoft accounts with those mail addresses are possible (they used to be impossible), but recently I stumbled upon two other web sites that didn't like single letter local parts.
I get told that my email is invalid by some apps, for using a .so domain. Apple was one that would not let me create an apple ID upon buying a new laptop. Eventually, I set up the machine without Apple ID, and opted to create it after the fact via apple.com which accepted it. It makes me wonder if it is intentionally a "Hard no" during system setup, and then a "well okay if you insist" when the user has installed the…
Re: Short URLs: Why and How
#153Earlier quoted context omitted.
My name’s Corlin and I own corl.in I sign up for accounts with emails like apple@corl.in and that lets me easily filter and organize my inbox. But when I have to tell some customer service rep my email they get very confused.
Can I ask how you host your emails? I have a similar situation but the price for most hosts for a wild-card domain is prohibitive.
Re: Short URLs: Why and How
#154Earlier quoted context omitted.
My name is Dan Blows, and my domain is da.nblo.ws, which I thought was the coolest thing ever. Most people are confused or don’t even notice it.
I used to have a mail address along the lines of d@nblows.com But beware, single letter local parts are not universally supported by web sites. Microsoft accounts with those mail addresses are possible (they used to be impossible), but recently I stumbled upon two other web sites that didn't like single letter local parts.
Re: Short URLs: Why and How
#155Earlier quoted context omitted.
del.icio.us
Just like old times. https://web.archive.org/web/20080906141421/http://blog.delic... >> "So why did we switch to delicious.com? We’ve seen a zillion different confusions and misspellings of “del.icio.us” over the years (for example, “de.licio.us”, “del.icio.us.com”, and “del.licio.us”), so moving to delicious.com will make it easier for people to find the site and share it with their friends. Of course the old del.ic…
https://latonas.com/blog/web-masters-episode-9-joshua-schach...
Re: Short URLs: Why and How
#156Earlier quoted context omitted.
http is still susceptible to man in the middle attacks even if the site contains no secrets. You have no guarantee that the contents of the website haven't been tampered with (not that attackers would have much incentive to tamper with a blog).
That's pretty much my point, there is no reason to meddle with the contents here. It's different if you live in a country where your ISP automatically MiTMs you (as a sibling comment to yours pointed out), but that's not a thing here at least. If you know that's a threat and it bothers you, you would likely already have measures in place anyway? But I admit it's a valid reason to have https.
Hackernews is a global website last time I checked so even if you don't face issues like that, many other users might.
Re: Short URLs: Why and How
#157Regarding the example of instead of hi.html just name the file hi and use the nginx Config “default_type text/html” —- is there an equivalent to this for other webservers (Eg Caddy etc) ? Perhaps it would be cleaner to just create a directory called hi with and index.html?
try_files {uri}.html {uri}
Done. (You can also add a redirect if you want to enforce that ONLY the non-.html version is used.)Re: Short URLs: Why and How
#158Depending on how much your write, URL collisions can naturally become a real problem. If you use a SSG then all your post HTML documents will be in the same directory, forever. This isn't a problem if you don't spit out posts, but if you post a lot your directory can become rather unwieldy. I'd say, at least throw a year in there: /2022/su/.
SSG can usually be configured. You could have whatever folder structure you want and still have all the URLs straight under the root.
Re: Short URLs: Why and How
#159Regarding the example of instead of hi.html just name the file hi and use the nginx Config “default_type text/html” —- is there an equivalent to this for other webservers (Eg Caddy etc) ? Perhaps it would be cleaner to just create a directory called hi with and index.html?
With Caddy, keep your filename the same and use try_files: try_files {uri}.html {uri} Done. (You can also add a redirect if you want to enforce that ONLY the non-.html version is used.)
Re: Short URLs: Why and How
#160Earlier quoted context omitted.
http is still susceptible to man in the middle attacks even if the site contains no secrets. You have no guarantee that the contents of the website haven't been tampered with (not that attackers would have much incentive to tamper with a blog).
That's pretty much my point, there is no reason to meddle with the contents here. It's different if you live in a country where your ISP automatically MiTMs you (as a sibling comment to yours pointed out), but that's not a thing here at least. If you know that's a threat and it bothers you, you would likely already have measures in place anyway? But I admit it's a valid reason to have https.
By using http you are assuming your "here" (where ever that is) is the same as where your readers are.
And if your "here" is in the US then hotel WiFi providers in the US are well known to have done MiTM to insert ads.