Hm. Bookmarks: The question is, what do you want them around for? If you're an er33t bl0gg4r type (something few are, really), then yes, your bookmarks can be entirely replaced by RSS feeds, I guess.

If, however, you're a regular peon, or a general-purpose type, it comes down to what you want to do. If it's DEAR GOD I NEED THE JUMPER SETTINGS FOR THIS MAGNETO-OPTICAL DRIVE THAT FUJITSU IS TRYING TO DISOWN BUT HALLELUJAH THEY LEFT THE INFO ONLINE ON THE CANADIAN SITE, then saving the whole damn page is the best idea. You don't want a pointer, because you know it might die.

On the other hand, if it's just something to scribble down... bookmark. And if it's live content (you care more about "the site" than "the particular pointer"), then RSS might be some sort of answer, I guess.

I guess you could argue that the browser interface makes *all* these tasks inconvenient... but on the other hand, it ain't that bad. Make a bookmark to file://where-I-save-my-sites, and things are sort of integrated, I guess. As to RSS.. well, hell if I know.

Storage... is a mess. I'm always amused by people with the corporatetastic outlook on things- before we even fuck with things like WebDAV, shouldn't we, say, settle on some sort of lingua-franca for removable media? I know I'm a luddite, but dear god, UDF was supposed to be the holy grail here, yet... good luck finding support for it, and double good luck finding support for it on Zips/MOs/any sane form of removable backup media.

Let's add a big "jesus christ it's 2002 and it's harder than ever to make backups" to that. Or at least, randomly-accessible backups. Obviously, if you're part of a corporate hive, you're using some sort of centralized SAN NAS RAID HUAGHL that gets backed onto DLT or whatever the fuck and then everyone crosses their fingers that the emulsion doesn't flake off the tape and really how reliable is that shit anyway? ... but if you're a home user, or a small-office user, or whatever... it's still impressively retarded if you just want to save some important files for posterity, and you're still stuck to weird, halfassed filesystems that lock you into whatever system you're using, and on and on and on. (I mean, sure you can rig up a Linux box, or an OpenBSD box, or whatever as a backup server, but this shit is STILL going to dump your data onto your tapes in ext2 or FFS or FAT or god knows what, and then two years down the line everyone'll be using ext3 or Reiser or whatever and you'll go through hell.)

Identity's already been argued here.

Um... and "jesus christ it's 2002 and the best we can do is blogging?" I'm going to go the route of a personal Wiki, but Wikis seem to have the concept right but the implementation unnecessarily brain damaged. What we really need is something like Chandler for "the web"... but, uh, it seems like Chandler will be built for "the web," so it might be the thing to wait for.

Still, it sounds like it'll be freakin' monolithic, so writing something vaguely similar in Ruby that just uses the filesystem and so forth might be cool.

Um I guess... regular websites were hypermesses or hierarchial (is that a word?), Blogs add chronological organization, and are nifty for certain types of shit.. but we still need the whole orgy that XML and prevalent databases and all that were supposed to give us. Something like a relational Gopher, I guess. OR just a content-management system that doesn't totally suck.

It seems the world is slowly rediscovering multicast or at least multicast-like bandwidth-multiplication for actual broadcasting and not just taking down Yahoo! so hallelujah on that point.