To your points.

I've intentionally left out the delete function, nothing lasts longer than a week without manual intervention. Despite using the service daily, I can't think of any cases outside of me manually messing with data as tests that I've missed having a delete.

This is a great idea, and I'll definitely be making a new initial login "landing" page!

There's something odd in my Apache setup, as the slowness looks like it's from load, but there's not that much strain on the box. The other issue, which I've tried to optimize as much as possible, is that it loads a LOT of JS when you click the bookmarklet, and it doesn't show the message until it's all done. I need really should pare that down some more, thanks for the push!

no probs - and quick response. That instantly gives you a huge edge over del.icio.us (INTEGRATE AMIGO!)

Well, what's the user story that you see for delicious? Pushing bookmarks to delicious before they expire? That's the only scenario I can see being worthwhile, but as someone who swore of delicious long, long ago, I'm definitely open to ideas here!

hmm, a good point actually. Forgot you remove stories after a week. I currently tag my delicious stories that I need to read later with "readlater" -- if I could import those direct to your site that'd be cool. Not sure if I could get thru them all in a week though!

Importing to me seems like an odd workflow though. Bookmark with delicious, import to markitforlater, read from there, links expire (or not depending on what you do), but are still hanging out in delicious. Again, the only net-positive workflow I could see would be: bookmark with markitforlater, decide you want to keep it around "permanently" so you push it to delicious. As a delicious user, does that sort of thing have any appeal to you?

yes, that makes far more sense! ignore my previous delicious ranting.

oh and EXTRA MASSIVE KUDOS for not requiring an email.