Tech

Tech-focused ramblings. Computers, blogs, and whatever else fits.

I’ve got a fan!

by

In January of 2003, I put up a post pointing out Jakob Nielsen’s ‘Top ten web design mistakes’. Though his advice is generally aimed more at commercial sites than personal sites, many of the concepts will cary over from one to the other, so I used the list to evaluate my own site and see how I was doing.

That March, a visitor by the name of ‘Deakster‘ [Deakster’s site may come up with a ‘403 forbidden’ error if you attempt clicking on his link, as I think he may be denying any visitors referred by my website.] came by the page and left a mildly snide comment about Nielsen and his company. Not in itself a big deal, but when I visited the URL left by Deakster, I found that his own site was coded in such a way as to require Internet Explorer, and would not load for me using Safari on my Mac or Mozilla on my PC. I mentioned this in a reply comment, that was that, and I didn’t think any more of it.

Last week, almost a year since he left his original comment, Deakster came back. This time, apparently incensed by my reply to his first comment, he took it upon himself to critique myself and one of my sites (specifically, what little is left at djwudi.com) in two comments left back-to-back.

Needless to say, I was a little amused by this (not just that he attempted to take me to task, and that he did so quite poorly, but mostly that he came back nearly a full year after his last and only previous comment to my site), and responded in turn. Again, Deakster wasn’t thrilled, started to leave more comments, but soon requested that I remove all of his comments from the page, declaring that he “no longer wanted to be associated with the site.”

Unfortunately, I wasn’t actually at my computer when his request first came through, so twenty minutes later he made the same request again.

It wasn’t long after that that I did get the message, however, and while I didn’t remove the comment placeholders from the page (I saw no reason to remove my comments, and as they were replies to his, I didn’t like the idea of out-and-out deleting his comments and ‘orphaning’ mine). I did, however, remove the text of his comments, indicating that I had done so at his request.

Apparently that wasn’t good enough.

I now have 75 bogus trackback pings on that post, courtesy of my new friend, with messages such as “Michael is a first class prick and should keep his mouth shut,” “Take on a haxor an end up with an app that autopost shit to yer crap site,” “Your blog aint sexy and neither is your bald spot,” “Why are yanks such fools — cause they are all like Michael,” and his final ultimatum, “Had enough Michael — i will leave it if you delete everything I want deleting and I mean everything.”

Why, I do believe I’m being harassed, ladies and gentlemen.

All of Deakster’s comments over the past few days and every one of the bogus TrackBack pings has come from IP address 81.152.149.121. Unfortunately, while I could ban that IP address from commenting, I don’t believe that there is currently a way to ban TrackBack pings by IP.

So what now?

Obviously, I certainly could “delete-everything-i-want-deleting-and-i-mean-everything” all of Deakster’s comments (and TrackBack pings) easily enough, but something tells me that he’ll likely not be satisfied until I also expunge my reply (which contains quotes from his comments) also, which I’m in no great hurry to do (hey, I had fun responding to his attacks…). Besides, giving in to script kiddies (a category I wouldn’t have put Deakster in until I got the TrackBack ping flood) isn’t my idea of a good time. ;)

Welcome to the neighborhood

by

After watching Phil struggle with his hosting provider for a couple weeks over system resources, he and I got to talking, and in the name of good geek-karma, I offered him a spot on my personal webserver. We spent the weekend getting everything configured, tweaked, and generally doing what it’s supposed to (I’m not much of a sysadmin, really…some parts of the setup involved me giving Phil root access and telling him to figure it out himself…), and as of sometime last night, everything’s up and running.

So now I’ve got four domains running off of my old G3: djwudi.com, hanscomfamily.com, geekmuffin.com, and interalia.org. I just may have to look into a G4 upgrade card if this keeps up!

iTunes: “Breathe (Peff)” by Lizette & from the album Breathe Remix (2001, 4:40).

Well-Designed Weblogs

by

Looking for some design inspiration? Good pointers to quite a few very impressively designed sites at Well Designed Weblogs Part One and Part Two.

And no, I’m not on the list. ;) While I like what I’ve got at this point, I don’t fool myself into thinking I’m doing that well!

iTunes: “VIT” by Future Sound of London, The from the album Lifeforms (1994, 6:48).

Apple out of debt

by

Impressive, really — even with the economy in the shape it’s been lately, Apple has been doing so well that they were just able to pull themselves out of debt, according to this internal Apple memo:

Team,

Today is a historic day of sorts for our company. When I arrived back at Apple in mid-1997, the company was burdened with \$1 billion of debt. Through everyone’s hard work we turned Apple around, paid off the majority of our debt and began to amass a war chest of cash in the bank which has grown to about \$4.8 billion! But there was still \$300 million of remaining debt, which we decided to hold to maturity.

Today we used \$300 million of our cash to pay off this remaining debt.

Apple is now a debt-free company — for the first time in over a decade!

It sure feels good.

Steve

(via /.)

iTunes: “The Moon, Part 1” by Speakeasy from the album Common Ground (1995, 3:33).

More on the genealogy project

by

I spent some time last night following up on playing around with software for tracking my family’s history on our website. So far, things are actually looking fairly good — with the one caveat that I only have so much information in my head.

The first piece to the puzzle is GEDitCOM, a Mac OS X application that reads and writes standard GEDCOM files (I had no idea that there was a standard file for genealogy software before I started looking into all this). While it’s not the prettiest application in the world, it does appear to be very powerful, and I’m quite pleasantly surprised by the amount of information that the GEDCOM format supports.

Of course, I’m not sure why I’m surprised — I’m obviously not the first person to look into how to track all this information using a computer. I guess we all just like to think that we’re the first to come up with a good idea… ;)

The second piece is the web package I stumbled across the other day — PhpGedView. A set of PHP scripts, it was very easy to install and get up and running, all I had to do was copy the scripts into a directory on the webserver, tweak the permissions on two files and one directory, and I could log into the interface and start putting things together. Again, it’s not as pretty as it could be, but it does look like nearly (if not entirely) all of the functionality that I was looking for is there.

Once PhpGedView is installed, all you need to do is upload a standard GEDCOM file and PhpGedView parses it and creates the final website. Here’s the one spot where I ran into problems: each time I uploaded the GEDCOM file that GEDitCOM created, PhpGedView wasn’t able to parse it correctly, and I got a bunch of garbage data.

Turns out that the solution is fairly simple, and ties into an age-old issue between Mac and PC file formats. Mac systems use a different character to signify the end of a line than PC (DOS/*NIX) systems do, and when the scripts tried to import the GEDCOM file, they saw it as one really really really long line. I was able to get around this by running the file through BBEdit and switching the line break style, I’m sure there are many utilities to do just that floating around the ‘net for people who don’t have BBEdit.

Once I got that figured out, the import went smoothly, and as a result, the first version of our family tree is up. It’s very bare-bones at the moment (though not as bare-bones as it looks at first — just click around and experiment a bit to move around the tree), but mom promised to send me copies of the family’s “history box”. Once I get that and pop more information in, the tree will look a lot less sparse than it does at the moment.

Even better, though, is that PhpGedView does handle one of the bigger items on my wishlist — user accounts with editing ability. I’ll need to put together a simple “user’s manual/how-to”, but this will allow other people in the family to add and edit information to the database. Once changes are made, I can then download the updated GEDCOM file from PhpGedView to my computer, re-import it into GEDitCOM, and keep all the information synced between my personal workspace and the website. Not bad at all!

Every few years of my life, the genealogy bug has bit me — now that it has again, it’s great that I’ve got the technology at my fingertips to be able to store and present it like this.

Now, mom — about that box… ;)

iTunes: “I Was Walking” by Poems for Laila from the album On a Wednesday (2002, 2:50).

iPhotoToGallery

by

Adding photos to my family photo gallery, the old way:

  1. Choose the photos I want to send to the gallery in iPhoto.
  2. Export the photos to a folder on my hard drive.
  3. Copy the photos to a folder on the webserver.
  4. Log into the Gallery software on the website.
  5. Navigate to the album I want to add the photos to.
  6. Choose Add photos….
  7. Enter the URL of the directory I just copied the photos into.
  8. Upload.
  9. Done.

Adding photos to my family photo gallery with iPhotoToGallery:

  1. Choose the photos I want to send to the gallery in iPhoto.
  2. In iPhoto, choose File > Export…, then click on the Gallery tab.
  3. Choose the album I want to upload the photos to (or create a new album).
  4. Click Export.
  5. Done.

Very, very nice.

(via Forwarding Address: OS X)

iTunes: “New Style Baby, A (’91)” by Pink Stanly Ford from the album Technomancer (1996, 6:47).

Heaven and Hell

by

From Neil Gaiman, after admitting that while he is equally at home on Macs or Windows computers, he is still primarily a PC user…

When I tell Mac people this, they smile their secret smile. They know that after we die, we go to a special place, and that those who used Macs will be raised on high, where they can sip their cappucinos and look down and see the virus-infected writhings and screamings of those who used PCs, as the damned Windows users are forever bombarded with boiling projectile vomit from the thousand-foot high screaming thing that used to be Bill Gates.

But I’m sure even the damned people down in the mud will be laughing up whatever’s left of their sleeves at those of us who secretly like fountain pens best.

iTunes: “They’re Coming to Take Me Away” by Lard from the album Last Temptation of Reid, The (1990, 8:28).

Genealogy software wishlist

by

Okay, so here’s what I wish I had available in a software package. Any mad coders out there feel like putting it together? ;) (This has been submitted to the LazyWeb.)

  • A web-driven genealogy software package (PHP/Perl/Python with a database backend?).
  • One page per family member, able to display (at minimum, though not all items would necessarily exist for every page):
    • Links to immediate family members (one degree of seperation: parents, siblings, spouses, children).
    • Vital statistics (birth, marriage, divorce, death). This could be expanded to include christening, baptism, etc. for situations where such dates are recorded.
    • Biographical and/or historical information — stories, memories, etc.
    • Pictures.
    • Contact info for still-living members.
  • User registration.
  • Logged-in users would be able to easily edit any individual page on the tree to add memories, stories, information, etc. (Wiki-style ‘edit this page’ links?).
  • Logged-in users should also be able to create new pages for family members not already in the tree. New pages should follow a template to ensure that a consistent look-and-feel is maintained as much as possible.
  • Wiki-like ease in adding pages and linking pages together. IE, one of the things I really like about the Wiki concept is how easy it is to (in this concept) let the tree grow. When creating my page, all I had to do was add WikiWords for my relatives, and I could then jump to and create/edit their pages. Functionality such as this is far easier than having to log into a central database and create new records for each new entry and then have to go back and edit all pages that would link to the new entry.
    • I’m still not sure how to best work around the issue with multiple family members with the same name.
  • Administrators should be able to review and approve/disapprove new users, get a list of recent changes, possibly approve/disapprove page edits before incorporation (this is optional, I think).
  • HTML output should be clean, standards-compliant, using CSS for styling, etc.
  • RSS/XML/Atom feeds of recently changed/added pages (preferably with an option to subscribe to either ‘minimal’ feeds listing only changed pages, ‘short’ feeds listing the edited page and the changes, and ‘full’ feeds listing the edited pages and the full text with changes marked in some way).
  • (This might be pipe dream territory) A dynamically-generated (Java? DHTML?) overview of the tree or branches of the tree. I’m visualizing being able to start with a simple tree of one nuclear family. Lines leading away from members would indicate further information along the branch. Clicking on a member (parent, spouse, child, etc.) would “slide” the display to that member’s nuclear family. “Zoom out” would allow more branches to be viewed (and would need a “Zoom in” control to return to a single-family view. “Detail” links on each member would lead to the individual member’s page (which would have a “View tree” link to switch to the dynamic tree view).
  • Possibly more as I come up with it.

If I had the time, I’d start diving heavily into PHP (or Perl, or Python)/MySQL and start attempting to build this myself. However, I don’t have the time, and something tells me that this might be complex enough to be fairly overwhelming as a first project.

If this software existed, I’d gladly pay for it (hopefully it would be within my price range, of course). At the moment, if anyone feels up to attempting to code it together, I’d gladly beta test!

So how crazy am I? How does this feature wish list sound? Is there already something out there on the ‘net that might cover some or all of this (aside from Wiki, which I’m already exploring) that I haven’t found yet?

Questions, comments, and words of wisdom are, as always, appreciated.

Update: Hot damn — PhpGedView just might be it!

Wanted: advice concerning Wikis

by

I’ve got a project running around in my head that I believe a Wiki would be a good solution for, but I’ve not done much to play with/experiment with Wikis in the past. I’d like to start playing around with this project soon after I get home, so if there’s anyone out there who might be able to give some advice or recommendations, I’d appreciate some “expert assistance”…

For a while now, I’ve been hosting The Hanscom Family Website. While the original intention was for it to be a collaborative weblog for the entire Hanscom family, so far it’s been acting primarily as my dad’s weblog (and there’s certainly nothing wrong with that!). Hopefully we’ll be gaining more authors soon, though, as I’ll be sending a “how to” tutorial to Susan, Eric, and possibly Doug and Pam also once I’m home.

One of the original ideas I wanted to include on the website (and actually was started on an earlier incarnation, but lost in a server mishap) was a genealogical record of the family. As I don’t know of a really good way to do a web-based family tree, my idea was for each person to have a single page listing important dates (birth, death, marriage, etc.), contact info (if desired), and biographical information. Each page would also have a set of links to immediate family members (parents, children, siblings) that would allow the user to navigate their way through the family tree. We could then, over time, create a genealogical database (of sorts) of the family.

One of the big reasons I’ve wanted to do this (and this was brought up in a major way during a conversation with my mom last night) was the number of stories that are scattered among all the various family members — some written, but many only currently locked in the vaults of memory.

The difficulty I had in the first implementation was that each person’s page was just a static HTML page, and if there were to be any changes to it, they’d have to be done myself. I’d need to have information and stories sent to me, at which point I’d make the changes to the static pages and save them to the server. It’d work, but it would be slow and somewhat kludgy, especially as it would rely on my own time constraints in order to get any additions actually incorporated into the pages.

Last night as mom and I were talking, though, it occurred to me that a Wiki could be a perfect solution to this problem. The page structure and layout would be essentially the same, but it would allow any of our family members to click an “Edit This Page” link on any one of the pages and add whatever they wanted, be it more biographical information about themselves, memories of other relatives, stories that have been passed down in family lore about ancestors, or other such things. In theory, at the very least, this could work very well.

My limitations (and worries) are simply that I’m by far the most technologically- and web-literate of my family members, and I need to do everything I can to make sure that the interface is as simple and easy to use as possible. I also want to ensure that the site is not publicly editable, so there would need to be some sort of account registration system so that I could grant global edit rights to family members, but prevent random passers-by from making unwelcome changes. I also want to have the system be as resource-friendly as possible, as it will be running on a 350Mhz G3 that is already hosting three websites, two of which use the MovableType weblogging system (which I love, but I also realize that Perl can be a major resource hog as sites grow, and my webserver only has so much firepower at the moment).

I did a quick web search and found the Wiki Wiki Web’s list of Wiki engines, but truth to tell, it’s a little daunting, as there are so many different engines available. Even if I narrow it down to the two languages that I’m sure my system can easily run (Perl and PHP) there are still a large number of possible choices, and I’m not entirely sure which scripting language would be the better choice as far as conserving system resources and ensuring that response time for serving/editing/saving pages is fairly reasonable.

So, to sum up, here’s what I’m looking for:

  • A Wiki (or similar) engine to allow for collaborative decentralized editing of a set of web pages.
  • User accounts or some form of access control and management.
  • As simple and ‘idiot-proof’ of an editing interface as possible.
  • Low (or as low as possible) system resource overhead.
  • The host webserver is a 350Mhz G3-based Mac running OS X 10.2 (i.e., the Apache webserver, Perl and PHP supported, UNIX-based).

Any ideas? Recommendations? Questions, comments, words of wisdom? Any and all would be appreciated!