Regarding being "kicked out" or "banned" by Delicious during an extended Export…

According to Delicious' documentation, they should not ban our IP address as long as we don't send more than one request (one bookmark) per second.  When I looked at this a couple years ago, I found that we would be banned after 1000 bookmarks.  So we set our algorithm in Bookdog, and in BookMacster 1.0, to send a request every 1.2 seconds, up to 900 bookmarks, and then back off to once every 5.0 seconds, and that seemed to work.

However, based on my own experience recently, I agree with you that this no longer works.  Actually, in two tests I found that I get banned after about 5 minutes and 35 seconds when sending a request every 0.8 seconds (a little fast, but seen similar results at 1.2).  Also, instead of banning you with an HTTP 503 error, now they sending this undefined HTTP 999 error.  The good news, however, is that instead of banning your IP address for a couple hours, now it seems to be much less.  I've seen it as little as a few minutes, but up to 50 minutes if I kept hitting it once every five minutes.  Clearly, some group within Yahoo! (who does not know or chooses not to use HTTP protocol specifications) decided to make some unilateral adjustments, but I sure wish they would publish their actual policies so we wouldn't need to reverse-engineer.

BookMacster 1.1.1 Beta (just published on /beta path) addresses this issue with an improved algorithm which is adaptive and user-adjustable.  More details are in the Release Notes.  Also, of couse, it no longer crashes.

Now I successfully synced my bookmarks three times with delicious without a crash
But still it tries to sync unchanged bookmarks. Also the Log tells me there were 68 bookmarks deleted but I have exactly 68 bookmarks more in delicious than in BM. Maybe the uploading bookmarks are the one that should be deleted. As they can't be deleted it tries uploading them each time?

Btw: I just purchased a license. Not because the app is working without any problems but for your great user support and because I know you will make the best out of this application!

OK, I deleted the sql file and tried it again. When uploading was almost finished BM crashed again, so this didn't help. I needed to re-authenticate BM with delicious and received an error. So the problem is delicious. It just would be nice if the app could work better with those errors (e.g. No re-authentication, pause the upload when kicked out and resume later automatically).
Another thing I found: I have about 400 Bookmarks in all browsers. On delicious there are over 500. Any reason why the amount isn't the same, even I told to overwrite delicious (clean slate)?

Thanks Jerry
Of course I don't know how BookMacster works together with delicious. What I see is that there is a local sql file for delicious. Do you think it is worth deleting this and start from scratch? Or is it a general problem and deleting the sql file doesn't help?
What I do now is uploading the bookmarks, after a while aborting it and start over again a few minutes later. If timeout is the problem maybe this can help.
I just found that yesterday I successfully uploaded all bookmarks and today many changes are reuploaded again. I can't understand why as I didn't made any changes until then.
Can't wait to test the new version where BM won't crash

Chris

I don't think this is normal behavior but I try uploading (syncing) with delicious and each time the application crashes after a while. I first thought it is a special bookmark that can't be synced but as it seems deleting this bookmark didn't help. Also I have to re-authenticate delicious many times and it seems even many bookmarks are uploaded before the application crashes, BM syncs the same bookmarks Over again whenever I start a new sync (and not only changes). I tried to get it to work for hours now without any success. Would it help to send you the crash log? If this problem can't be fixed I can't find a reason to purchase the app - even I really would like to use it.