Closed GoogleCodeExporter closed 8 years ago
The filenames Photograbber creates are determined by the Photo's unique ID
(from the Facebook API) to avoid duplicates. It's not clear whether the
filenames for the photos as they appear on the actual Facebook website could
ever change. I figure that the API's identifier is less likely to change
compared to the filename returned on the website.
I can see where it would be annoying if you have manually downloaded pictures
along with Photograbber automated download pictures - but there are some things
to consider before making a change:
1) review the Facebook API to ensure that the photo's filename never changes
(if it could change than that filename should not be used)
2) in order to keep Photograbber backwards compatible I would have to add this
on as an option for the user to specify (which would add clutter to the UI)
Original comment by tommy.mu...@gmail.com
on 20 Sep 2010 at 7:20
I also strongly recommend this feature be implemented. I've archived facebook
photos for several years now and having the original filename would be
immensely useful identifying duplicates and replacing untagged photos with the
newly tagged photos. While you potentially could just re-archive with the
program and go along with its filenaming scheme, it would be difficult to
discern which photos which were archived before but are no longer online. And I
think this centers on the principle of archiving photos is to preserve them
since they may one day be deleted or unavailable. Also, the filename also
offers a way to manually relocate the original link for the photo (if it hasn't
been removed) as well as the original uploader's facebook ID.
As for the photo filenames, I'm very confident they don't change. Photos that
have been uploaded even as far as five years ago still have the same filename.
I've never encountered an instance where photo filenames have changed.
Original comment by closei...@gmail.com
on 2 Nov 2010 at 12:31
r98 addresses this issue and keeps the facebook cdn filename for files. This
'breaks' compatibility with data saved by a previous version of photograbber in
that duplicate files will be created, however the new version of the file may
be a higher resolution (see r96). Directions/explanation of this may be needed
for existing users that upgrade.
Original comment by to...@ourbunny.com
on 2 May 2012 at 2:29
fix included in r99 binary, now available for download
Original comment by to...@ourbunny.com
on 4 Jun 2012 at 1:38
Original issue reported on code.google.com by
Supreme1...@gmail.com
on 8 Sep 2010 at 7:59