Hacker News Reader

Comment by notwedtm | Hacker News Reader

This sounds like a good article (from the title), however my company seems to have bulk-blocked the .xxx TLD. Out of curiosity, why did you put your blog on the .xxx domain?

Unless you are talking about open-source boobs, or something. Then I understand completely.

View on HN

> Out of curiosity, why did you put your blog on the .xxx domain?

Maybe it helps to point out how silly it is to filter based on the TLD.

Or underlines how silly it is to use a TLD ostensibly intended for porn sites for a blog.

Would you prefer .com? Or .org?

30 years ago .com may have been intended specifically for commercial purposes but that is buried underneath three decades of use as a generic catch-all TLD and as such using it communicates almost nothing about the site in question.

.org is by convention and usage largely reserved for nonprofit organizations. As such use of .org (intentionally or otherwise) communicates that the website in question is for a nonprofit.

xxx is, at merely 4 years old, brand spanking new. There hasn't been time for intent and practice to diverge meaningfully, ergo it's perfectly reasonable to assume a site that uses the .xxx tld is in fact a porn site.

In much the same was as io meaning input output and not an island!

pretty sure the only point of the .xxx TLD (aside from it being yet another source of income for ICANN of course), is that it clearly signals that the content is NSFW. It is totally reasonable for certain organisations to block it.

Even when that was the original sole purpose of the TLD?

Because it's @fat, and that's how he do. No boobs here though all fairly SFW.

haha <3

And, FWIW, boobs are SFW as well. At least in the USA.

While you are technically correct, the term has an exact meaning in internet culture.

The term "safe for work" refers specifically to a lack of sexual and...medical... content. Looking at cat pictures might get you fired, but it's still "safe for work".