Difference between revisions of "Picplz"
Megalanya1 (talk | contribs) m (MOTHERFUCKER ! ! !) |
Megalanya1 (talk | contribs) m (MOTHERFUCKER ! ! !) |
||
| Line 11: | Line 11: | ||
'''Picplz''' was a photo sharing service that died on July 3, 2012. | '''Picplz''' was a photo sharing service that died on July 3, 2012. | ||
== '''MOTHERFUCKER ! ! !''' == | |||
== '''MOTHERFUCKER ! ! !''' == | |||
== '''MOTHERFUCKER ! ! !''' == | == '''MOTHERFUCKER ! ! !''' == | ||
Revision as of 11:37, 17 January 2017
| Picplz | |
| |
| |
| URL | http://picplz.com/[IA•Wcite•.today•MemWeb] |
| Status | Offline |
| Archiving status | Saved! – Find a user |
| Archiving type | Unknown |
| Project source | https://github.com/ArchiveTeam/picplz-grab |
| Project tracker | http://picplz.heroku.com/ |
| IRC channel | #archiveteam-bs (on hackint) |
Picplz was a photo sharing service that died on July 3, 2012.
MOTHERFUCKER ! ! !
MOTHERFUCKER ! ! !
MOTHERFUCKER ! ! !
MOTHERFUCKER ! ! !
MOTHERFUCKER ! ! !
MOTHERFUCKER ! ! !
MOTHERFUCKER ! ! !
Rescue effort
We got it:
The following sections are kept from the early archiving effort for historic interest.
API
Picplz has an API that returns data if you give it (incremental!) numerical ids.
https://sites.google.com/site/picplzapi/
http://api.picplz.com/api/v2/pic.json?ids=11183559 http://api.picplz.com/api/v2/user.json?id=1515537
Image formats: the API has several image formats available. We may or may not want all of them. The web interface uses the following formats: 56s,64s,100s,400r,640r,1024r (1024r being the largest version the API provides), so we might want to get those.
Download scripts
A first version of a download script is available in the GitHub repository. When given a numerical user ID the script uses the API to download all data and images of that user.
Something to decide: we can get all the information from the API, but what else should we save? Should the WARC file include any of the web pages, even though that doesn't provide extra information? At the moment the script downloads the user's homepage and the page of every picture.
The infinite scrolling of the user page poses a problem. The JavaScript functions add a _ parameter with a timestamp to their API request. We can't really archive the timestamps: the resurrected page will request URLs that aren't archived. The download script therefore archives the API urls without a timestamp: remove the timestamp parameter from the JavaScript to fix the archived page.