CrowCamCleanup.sh doesn't delete videos from crowcam-videodata

[tfabris]

I had the following happen:

• I took one of the newer streaming videos on the new CrowCam channel and put it in the Crowcam Archives playlist.
• I finished all of my code changes that were supposed to fix up CrowCamCleanup.sh and it all seemed to work.
• I tweaked the deletion time so that it would want to delete that new video.
• I ran it and it did indeed delete that new video as expected.
• It seemed to delete it from the playlist as well. At least no errors happened when it sent the playlist removal command, and when I surf to the playlist on YouTube, it's not in the list any more.
• However the file crowcam-videodata which was written out to disk, that file still had the deleted video in its list. My web site still lists the video, but if you follow the link, the video is gone.

TO DO:

• Find out what the weakness is in my code which fails to remove the video from the data.
• SUSPICION: I retrieve the JSON at the top of the code to analyze the playlist contents, then delete the video and the item out of the playlist on YouTube, but I don't re-retrieve the JSON and reprocess it, nor do I try to remove the item from the existing JSON that's in memory.
• If my suspicion is true, then running the script a second time should re-retrieve the JSON and finish cleaning up the leftover video. I never noticed it before because originally it always ran the script every half hour and I never saw the dangling videos on the web page. (Tested: Indeed it was cleaned out on the next program run.)

[tfabris]

This is low priority for now because:

• It only affects my side project where I print the video list to my web page.
• It fixes itself every half hour. The issue, when it occurs, gets erased on the next run. So when the issue happens, it fixes itself pretty soon.
• When the issue occurs, the problem is very minor: My web page has one dead link for 30 minutes and then it corrects itself.

Note: I had some ideas of how to fix it when I was working on issue #72 - However there were problems with that one and I had to close that one without going any further. Read that issue for more details.