d3ft.com

I find that there are certain parts of the web that I am drawn toward less and less. This could be maturity, a lack of time, or just that they are no longer interesting. Mostly, it is because I just can’t find a connection with the writer.

One of those places on the web I no longer frequent is sites of web developers. Another such place is application developers. It seems my desire to learn about the creation of content about content creation has come to an end. No real reason for this, just an observation of how I spend my time.

This could be because the creation of applications and web sites are now so commonplace, and the tools so simple to use, that there just isn’t the greatness associated with “getting a website!” It doesn’t take a genius to code up an iPhone app, or to make yet–another text–based to–do application. It just takes time and the ability to market well.

One of the recent trends in marketing was blogs. Sadly, it appears that real–time web is going to make even blogs seem slow. Google will get you to the data (and the answers) as fast as it used to take think up the question. This makes it seem like even blogs are becoming inessential. Especially blogs about coding for blogs that market to people who want to know how to code for blogs.

I’m not sure it’s the lack of time that keeps me away, now. With constant iPhone-y internet, I’m a couple of clicks from anything. It isn’t the lack of enthusiasm and topics from the writers, either. I think it’s because I just don’t need them anymore. Content about the construction of tools to create content has become inessential.

A while ago I whined about the inability to block certain iPhone apps. Luckily for me, Apple saw fit to just remove the questionable apps themselves. So it’s “good for them, good for me,” right? Or is it?

It comes down to this: Apple can do whatever they want to with their store. It’s their store. Nobody can tell them what to do with their store. Other than just not purchasing Apple products, consumers have no say in what Apple does with their services.

So, there.

None, at all. Could hardly care less.

It had to be said.

I care nothing for implications for Apple in the laptop–replacement milieu, nor their impending fight with Amazon’s Kindle. Nor, do I care anything about Apple’s continued use of touch technologies.

If one were to ask me if Apple is creating another G4 Cube, I would have to ponder how little I care about the situation, in total. This is a product that does not concern me. The state of the company does not rest with either my love for or hatred of this new piece of hardware.

It is made by Apple, big deal. They also make mini DVI to VGA adaptors, should I pontificate on that? No. No, I should not, because I care nothing about the laptop–to–display adapter segment of Apple. Nor, do I care about the iPad sector of Apple.

If you are going to put up a blog with the expressed purpose of creating nothing but great content, then gain notoriety, then cash in on that notoriety by putting advertising on your site, can you do one thing for me? Please?

Keep producing great content or stop putting up ads.

I was going to link to many, many examples of this, but I figure it wouldn’t be acted upon. Seriously, if I am out–blogging you, then you need to stop with the ads.

Until a couple of minutes ago, I had this in my Colophon:

If you’re looking at this on a Windows–based system, it may be hard to see. That’s because Mac OS X displays tend to have a much brighter gamma than Windows. If you can’t see it, then, blame Windows.

Pim from the Time Capsule Memorial Register kindly pointed out that, as of Mac OS X 10.6, this is no longer the case. Now Apple shoots for the minimum and makes your screen darker than necessary. Just brilliant (pun intended).

I also went ahead and removed some WebKit–specific hacks to make the letters on the screen theoretically more legible. The hacks were reportedly not successful. A few color changes, and the site should read more effectively, regardless of the operating system or monitor you are using.

Plus, I’m stuck on white backgrounds.

Perusing the iPhone apps in the iTunes store, it reminded me how much absolute garbage gets in there. It’s as smarmy as Facebook. I have an idea to make it better.

Looking at the list of the top 100 free apps, you’ll find free versions of apps. Nice idea, but most of them are free versions of apps that you wouldn’t pay for. Others are limited versions of apps that you wish you didn’t have to scroll past. How’s about we introduce something else they have in Facebook?

Block App

Tired of seeing that stupid Sex Quiz thing again? Just click the ‘Block App’ button. One quick confirmation message later, and never see it again (unless, of course, you want to go into the preferences and unblock it).

I’m not sure if this has been proposed before, but it seems rather obvious to me.

No computer that is incapable of running Mac OS X 10.6 is capable of running an app that can only run on Mac OS X 10.6. Therefore, to use the logo for ‘Universal’ apps on your software is illogical. Please stop doing it immediately.

I’m trying to be succinct. It bugs me when software developers don’t pay attention to detail. It goes beyond irritation and into mild rage when I see something like that used in marketing materials and blog flair.

For review: 10.6 only runs on Intel processors. If your app requires 10.6, do not use the ‘Universal’ badge.

Some brilliant writer person once suggested that people write the first paragraph of a blog entry last. That way, you’d have a good idea what you were writing about, so you could introduce the idea more clearly. I love the idea, and I did it with this entry. It amazes me, in how I’ve been writing somewhere on the internet for something like 20 years, that I never have stuck to one thing long enough to really see how good of a site I could make.

In September, I decided to put together a minimalist website that had the primary function of sifting through the ever–growing number of interesting things on the internet. A rather fortuitous domain name search and registration later, I created this site. The original intention was to put it here then leave it be, but that changed.

That concept, of creating something and never evolving it, was something I looked forward to. It was a challenge for me to keep something in its originally–concieved state, then grow the site through external and internal ideas, rather than functions. The idea is akin to what Twitter has done — build on their core functionality without diverging from the original intention.

Most of the innovations Twitter the company has made in the past couple of years are from ways to work around limitations on the system from Twitter users. Search, lists, hashtags, and ‘re–tweeting’ are all ideas from the users that the company has wisely added to its core functionality. That way — organically — is the way I think you grow a product most successfully.

Its that way that I chose to grow this site. Organically. Built on a WordPress core, I’ve added a few touches here and there, but there’s nothing here that anybody can’t do. Just some plugins, a minimalist template, and my own ramblings, written in micro– to short–outbursts of sagacity.

A couple of months have shown me that writing alone doesn’t work any more. The internet is full of terrible writers, linkers, lurkers, and trolls. Nobody gets enough traffic that deserve it, and nobody that gets traffic deserves it. This is less of a personal quibble and more of an acknowledgment that people tend to be attracted to the grotesque rather than the tranquil.

There are no drastic changes planned for the future of this site. Just a few additions, here and there. Just a continuation of growing this thing — whatever a d3ft.com is. As I get more settled writing this thing — gain my sea legs, if you will — then I’ll keep on trying to make this the best d3ft.com it can be.

I wrote this piece in February of 2008, and thought I would resurrect it in light of the recent controversy concerning its life expectancy.

A few months ago, I had a real scare with my hard drive. One of the bullet point selling points of Mac OS X 10.5 is Time Machine, the automatic backup software. As I thought about Time Capsule, my hard drive, and backups, I came to an awesome, terrible realization: all hard drives fail.

Looking over the specs, I can’t really find any way to replace the hard drive in this thing. This is critical, because it’s your last line of defense. If this thing goes down, you’re sunk.

Pondering the possibility of losing years of data on my disk, I realized how Apple could be setting itself up for failure. No, not because the device won’t sell — it will. And not because it isn’t marketed as another boutique product. It’s because the very device they’re selling can easily go against the convention they’re trying to enforce.

Years ago, Apple introduced this application called ‘Backup.’ It was part of the .Mac service, and it let you back things up in a simple, convenient way. That was the intention, anyways, as I’m not sure anybody really knows how to get the thing to work. And I’m pretty sure nobody’s dumb enough to trust it to back up anything more important than their Safari bookmarks.

That’s the problem with the backup solutions that are supposed to be what you would expect from Apple; not as feature–rich as you would hope, but comprehensive and very easy to use. They succeeded this time with Time Machine. And somehow, Backup yet lives — there must be a reason.

Getting to the reason for the continued existence of Backup led me to think about the rationale to make Time Capsule, the wire–less, hard–drive–based backup device. As Backup is to .Mac, Time Capsule is to local storage. They both follow the same mantra, but with vastly differing success.

Backup was always hampered by its connection to .Mac. There just wasn’t enough room to backup the files on your computer. You could, at most, back up a subset of the types of files like Word documents or all the files in your Documents folder. It surely wasn’t what you’d need for the ‘prosumer’ experience, and definitely wasn’t a professional–level solution.

Mac OS X 10.5 brought Time Machine, and the promise of backing up your entire file system, down to the minutia of your fonts and preference files. Sure, you needed a pretty big hard drive, but that sort of space is cheap right now, still more so that online. With a daily backup of everything — that comprehensive approach — you could get back what was lost, and that’s what we all want.

Selling hardware to meet that demand was the next logical step. Apple did this moving from iTunes to the iPod, and they’re doing the same thing from Time Machine to Time Capsule. The wireless capability is just a bullet point — what they’re really doing is selling convenience.

With that convenience, Apple is getting you to do something you should be doing: backing your data up. It makes everybody feel good, you see. Promote that healthy behavior. But it would make sense to use a piece of hardware you can fix, right?

As far as I can tell (since I haven’t been able to get my grimy paws on one, yet), there’s no way to change the hard drive in the Time Capsule. There’s a lot of precedent for this, from the iPod to the new MacBook Air. But that’s a bad idea when you’re using this as your solitary backup.

It’s the same problem you’d have if your primary disk went bad. One well–timed lightning bolt and every source of hope you’ve got is turned into stylish, over–priced paperweights. The message I’m trying to convey is this: instead of having one last chance (your hard drive) you’ve now got two (with Time Capsule). And until somebody does something about it, that’s all you’ve got.

I love fear–mongering. Even more so when it’s right in line with the idea Apple’s trying to get across to consumers. With Time Machine, they’re trying to say that cheap storage — online or local — is within the reach of pretty much everybody. If you can afford a computer with Leopard, you can afford to get a Time Capsule for your house.

Honestly, I agree. The thing that I’m wary of is that you’re purchasing a silver bullet — and that will lead people to the inevitable complacency. That lax attitude will lead to reliance on this system, and someday we’ll be watching videos about “Time Capsule’s Dirty Secret.” Nobody wants that to happen. Nobody.

So, solutions? I’m not sure. I’d really hate to think that this piece of hardware is going the same route as the iPods and Mac minis and Apple TVs and MacBook Airs before it. I’d hope that there was some way to replace the disk, or at least to get it recovered quickly. I would hate to think that people are trading a bag of magic beans for two bags of magic beans.

Just in case you ever wondered who you should block off and keep almost 100% of your site free from spammers and scrapers, I’ve found it’s always a good idea to block off the RIPE network. Not that it’s all a bad thing, or that you don’t get legitimate traffic from there, it’s just that a full 100% of the traffic I got from there was spammish.

Before we get started, some things to remember. Like last time, if you have no idea what I’m talking about, let the person who you bug about all things electronic do it for you. Also, this tutorial needs a modern Apache webserver. Most importantly, if you expect legitimate readers from the Asia Pacific region of the world, you could block your readers. Remember these things.

Copy and paste this into your .htaccess file:

#Amsterdam
deny from 62.
deny from 80.
deny from 81.
deny from 82.
deny from 83.
deny from 84.
deny from 85.
deny from 86.
deny from 87.
deny from 88.
deny from 89.
deny from 90.
deny from 91.
deny from 139.10.
deny from 139.12.
deny from 139.16.
deny from 139.18.
deny from 139.24.
deny from 139.28.
deny from 139.30.
deny from 147.83.
deny from 147.84.
deny from 147.91.
deny from 193.
deny from 194.
deny from 195.
deny from 212.
deny from 213.
deny from 217.
#Australia
deny from 58.
deny from 59.
deny from 60.
deny from 61.
deny from 165.228.
deny from 165.229.
deny from 168.140.
deny from 202.
deny from 203.
deny from 210.
deny from 211.
deny from 218.
deny from 219.
deny from 220.
deny from 221.
deny from 222.

That would be it.

The Amsterdam and Australia mean really nothing. They are just there to keep things organized. Doing a whois on the IP ranges shows to which branch of RIPE they belong. You can shuffle them all together into one neat list, if you like.

Like I wrote before, this is a throw-the-baby-out-with-the-bath-water approach to banning. The way I have it set up, you block everything in the IP range rather mercilessly. The only reasonable purpose for doing this would be if you are losing a lot of bandwidth to non–human traffic.

Ever had somebody (or, more likely, something) constantly hitting your website and wasting your precious internet resources? Then you have some options with Apache and .htaccess. This little tutorial will show you how to block an IP address.

Note: this will stop access to your site, not keep a site from finding your IP.

First, get a website. Got that? Good.

Now, make sure you have some sort of Apache server. If you’re not sure you have one, the rest of this won’t make much sense. If that’s the case, just go back and let your kid read the rest of this.

For those of you still with me, you’ll need to upload a file to your server called an .htacccess file. It’s simply an extension that tells the server what to do with all your files (Here’s some info from Apache). This is where the magic happens.

Inside that .htaccess file, you set up some variables to create certain events. If you use WordPress like I do, there is one uploaded when you install it. It’s in the top-level directory, just sitting there. Other content management systems use an .htaccess file as well, like Textpattern, Expression Engine, and Dupral.

If you open the file, you’ll see there’s some WordPress (or them other things’) specific code. Don’t fiddle with that. Just leave it be, because the part that the blogging software uses doesn’t really have much effect on what you are going to do.

I found this at JavaScript Kit, and it’s a wonderful way to keep the spammers, scammers, and scrapers off your site. Inside your .htaccess file, put this:

order allow,deny
deny from 123.45.6.7
deny from 012.34.5.
allow from all

This is how you deny by IP address. Find the offending IP address you want to stop, put it there, and that singular address will never be able to get to your site.

Since the inception of this site, I’ve taken to the task of tagging every post with a stunning amount of tags. I tag the posts (and links) with as much information as possible in the hopes that it will add relational value when you’re searching in this site’s search application, or using some other search appliance (e.g. Bing, Google).

Running WordPress, I’m able to add tags to posts without working at it through a function of Simple Tags. It uses comment phrases to try and add tags based on simple keywords. If I use the word ‘WordPress’, for example, it will add a WordPress tag, even if I forgot to explicitly add it.

Also, the All in One SEO Pack adds post tags to the page META tags. While this isn’t apparent to the user just looking on the page, it helps search engines to figure out what the page is about. Additionally, like I wrote before, it also helps the built–in WordPress search appliance.

One application of all the tagging (besides search) is the use of the Similar Posts plugin on the reference links page. Their function is sort of, “I’m done with this page, now what do I do?” The use of tags helps figure out what will be relevant. Granted, this is done with a combination of human tagging, computer guessing, and dumb luck, but it seems to work fairly well so far.

But the big reason I am doing all this tagging isn’t just to tag everything. It really isn’t important that I’m tagging all this stuff, but why I’m tagging all this stuff. I tag all this stuff because, at some point, somebody will try and build upon an idea I write. Or will be looking for something completely different. Or looking for just this thing.

The main reason I tag everything is because I have no idea what anyone wants to know. Think of these tags as writer’s notes when translating languages. It’s a way to translate from my mind to the reader.