For the first time, I’m not here to complain, but, well, you can have a pretty bad day. I mean, I’m just not going to stop! I mean, I’m not going to stop doing what I am supposed to do because I think this is what you need to do to get there.
For the past few months, I’ve been testing out this new feature on my blog, and now the developer I’ve been working with has decided to release it as an extension to WordPress. So I’ve been testing it out for myself and I’ve got some cool stuff in the works.
I love that this feature is free! It means that I can continue to post as I please without worrying about what Im going to do when Im too lazy to read my blog. Of course, I also like the fact that this feature will keep me from having to use the crappy 404 code that Im currently using. Of course, it may just be the coolest thing ever, so I’ll just keep my fingers crossed.
This is one of those things that I feel is so easy to understand and yet so hard to implement. I mean, why wouldn’t I have to include some HTTP header that says “404?”? Well, because WordPress allows you to send a 200 status code but I don’t think that would have been too popular.
Oh man, the 404 status code is a huge deal for someone like me. I don’t have a 404. I hate it with every fiber of my being. However, I can understand why it would be popular to include a 404 status code, especially in the WordPress world where people are still stuck using this crappy code that lets people get their blogs and content but you can’t get your own domains to point to it until you upgrade to a newer version.
404s are one of the major reasons I’m giving up on blogging. They’re an easy way for people to send a 404 and not be able to get their blog up and running again. As much as it sucks, I can understand why it would be popular. As an example, look at this example WordPress.com page: I see this status code there. It works fine. I am sure you can get your own WordPress.
The problem is that WordPress.com is probably a better option, but that status code basically lets you send a 404 and then get your own domain to be pointed at the 404. For years I have been annoyed at this status code. My blog is simply so small that it does not make sense to have to send a 404. If it sends a 404, it should be able to point to my blog anyway. I also can’t get my domain to point to my blog.
So, I did not try to work around that and then get my own domain to point to my blog. The 404 code is only used for WordPress.com.
I can confirm that this is not an acceptable URL. The reason is because WordPress.com is not your blog. It’s your blog’s URL. It’s so you can access your blog from anywhere on the web, and thus your blog can be accessed anywhere on the web. If it would just accept links to your blog, then I wouldn’t have to send a 404. There’s another issue with this, as well. The 404 code is only used when you have a blog or website.