2008-12-08
post/63734285
Kind of self-explanatory. And before you ask, no, I don’t have any Ffffound invites. Ssssorry.
Someone seems to have taken the idea behind my ffffound mirroring scripts, added the ability to download the actual images (which is, admittedly, really handy), and wrapped them in a website (which is even more handy). Nice job. Shame about the slightly iffy anti-aliasing on the logo, but I really shouldn’t even mention that.
(No, I don’t have any invites either.)
Edit OK, now I’ve used it and have the zipfile, which is just a collection of the raw images, with an arbitrary timestamp (boo) and no index. Perhaps I’ll twiddle my script to generate some nice HTML so you can actually manage that folder of images more usefully. Still, it’s good to have an archive.
2008-05-11
ffffound_mirror.rb
Today’s half-finished code hack will scrape ffffound, downloading the original image URL and site along with the ffffound id, URL, image and related IDs, and various metadata, and then put them into a big JSON file.
Known bugs:
- posts newer than about two days don’t get a date. Will try chronic later
- dates may not be completely accurate: I’m not sure which TZ ffffound uses
To do:
populate database not JSONsee update below- argument driven
- re-run-able (incremental running; abort when matches ID)
- determine post vs found (cleverly or by brute force - see ‘type’)
Harder
- something like flickrtouchr?
- delish style UI
Question
- Does the presence of javascript:FoundAPI in the page source mean anything?
Update OK, I hacked in a database. Create it with ffffound_create_db and back up to it with ffffound_mirror_db. It handles interrupts gracelessly; use the sqlite command line tool to ‘delete images’ for now.
