Hacker News Reader

Comment by judge2020 | Hacker News Reader

judge2020

I don't get why people feel the need to make these unique domain names for a single blog post.

This happened with 'chrome is bad'[0] where someone anonymously registered a new domain complaining about Chrome's updater taking up CPU, but the comments later pointed out that it most likely was just a bug in activity monitor[1].

It seems the only reason for doing this instead of having a personal site with multiple blog posts is to spark debate while keeping a zero-repercussion way out in case the internet/HN determines that the situation is more nuanced than what the blog makes it out to be, or when it's outright incorrect on facts.

0: https://news.ycombinator.com/item?id=25400618

1: https://news.ycombinator.com/item?id=25401681

View on HN

I don't think in the current climate "having a zero-repercussions way out" is an unreasonable thing to want. Heck, I don't think merely having an incorrect take on a technical issue is something that should ever warrant "repercussions", unless it's intentionally claimed from a position of authority.

But more than that I think these silly single use websites are just gold marketing. They're very memorable, I don't think we'd have collectively remembered the "motherfucking website" if it was just a blog, for instance. It's a bit daft, but what can you do.

There is no such thing as "zero repercussions way out" here, and it seems to make no sense to even want that in this context. Either the bugs are real and they get fixed, or they don't and now the project looks bad; if for whatever reason the bugs turned out to not be an issue, that would be the only time it wouldn't matter in the end.

If the author isn't actively working with upstream to get them fixed, and isn't announcing that association with the project, it's probably safe to say they don't have a position of authority within that project.

Idk about why they do it, but I can remember them! I read many many blog posts and if someone happens to ask me about a certain topic and I remember reading an blog post about it, I usually have to google or search my notes for it. Not with flatkill.org and with doesmysiteneedhttps.com

These two I always remember. So that's maybe why

http://isthisyourpaperonsingleservingsites.com/

> I don't get why people feel the need to make these unique domain names for a single blog post.

It's funny and stands out.

>instead of having a personal site with multiple blog posts

It isn't like they couldn't make anonymously flatkill.some-free-hosting-site.tld.

>a zero-repercussion way out in case the internet/HN

Or when the mob doesn't like someone saying what they like is bad and proceed on a crusade.

flatkillsucks.com is $10/year on Namecheap.

Your move, I guess.

This particular blog post gets reposted and debunked almost monthly on hacker news.

Reply on news.ycombinator.com