You got it; one at a time. Grab a coffee and start clicking. You may as well know that you are only removing the image from your displayable photos; the file(s) still reside on the Zooomr server and are still accessible under the original static paths even after you do your delete.

No, no, it's a feature, not a bug.....

Bummer, I was doing this monster upload and had a problem in the middle, so I figure, I just do it again and delete the previous one after that...

It´s a pitty, there´s no tools do manage a bunch of pictures at once...

I just finished deleting around 3000 photos...
Get AutoHotKey (an dopen source macro editor/player) and set it to work :)

I discovered that there is no macro player app available for linux :(

Anyway, I think you're wrong (Brian) with regards to photos staying on the server - my photos stopped appearing wherever they were previously shown...

I didn't think I'd live to see it! Kosta, you're right: it seems pics aren't accessible any longer under their static URL when they're removed by the user. (Cf. http://beardedgit.com/?p=230, where the photo is gone as well at last.) That's great news.

(Of course we still don't know if photos indeed are deleted from the database or wether they have only been stopped from showing. And the message replacement is somewhat misleading. It's a BIG improvement nevertheless.)

That's a generic picture that will always be there if a bad image link was referenced.

Here's proof;
This is the image BeardedGit put in his post:
http://static.zooomr.com/images/3699895_5d7021d9f4.jpg

Change it to anything, say for example:
http://static.zooomr.com/images/120983209jfzlkjq9.jpg

That unavailable image will be returned when anything under static.zooomr.com is accessed that isn't valid.

Again, for example:
http://static.zooomr.com/lkjwer

Even /that/ will result in "Sorry, this photo is currently unavailable."

It's not a bug, and nothing needs to change here. Numerous websites use this as a mostly well-served 'catch all'.

Who said this was a bug? I just think the wording "currently unavailable" is misleading in this context. "Gone for good" would be an adequate phrase -- to make clear that it's not a timely glitch on Zooomr's side (of which we actually had many) and that the pic won't come back after a while.

All -- if the photo is deleted from Zooomr, it's gone. There are periods where some of our remote caching servers might not get updated in a timely fashion, but they are deleted from the root.

"Sorry, this photo is currently unavailable" is used because our storage layer is completely separate from the actual photo record database. There are times when a photo record is created, but our photo storage network is propagating photos out to cache servers -- there is no way for us to report a message if a photo is simply gone or currently being processed.

Likewise, other photo sharing sites (including Flickr) also display the same message in error. It's quite common:

http://l.yimg.com/www.flickr.com/images/photo_unavailable.gif

kristopher

All -- if the photo is deleted from Zooomr, it's gone. There are periods where some of our remote caching servers might not get updated in a timely fashion, but they are deleted from the root.

"Sorry, this photo is currently unavailable" is used because our storage layer is completely separate from the actual photo record database. There are times when a photo record is created, but our photo storage network is propagating photos out to cache servers -- there is no way for us to report a message if a photo is simply gone or currently being processed.

Likewise, other photo sharing sites (including Flickr) also display the same message in error. It's quite common:

http://l.yimg.com/www.flickr.com/images/photo_unavailable.gif

kristopher

Cool. That's good to know, Kristopher. But what about deleting a group, as per the original question? I know I'm new here, but I've been reading the help forum a fair bit and the common question is how to perform group actions like deleting, changing privacy, changing tags, etc. on a group of photos (set or manually selected should both be options, especially since I've been unable to make sets and it looks like I need to batch-delete and reload with different privacy settings to force the Smart Set function to work... another issue several of us have received no help with).