On Wed, Jan 2, 2013 at 4:30 PM, wp mirror wpmirrordev@gmail.com wrote:
Happy New Year, and thanks for your e-mail of 2012-12-31.
You too!
- ADMINISTRATIVE
I fixed the capitalization of "Wikimedia" in both documentation and home page. I am now subscribed to this list and have read the last two years of postings.
I think I saw it was already fixed a few days ago. Thanks.
- METALINK
[...]
I still need to read more about metalink but I think it squarely falls in the "we'll support it if someone does the work to make it happen" category. (In case that wasn't clear before, you're welcome to do that work yourself if you like.)
- SPDY
WP-MIRROR 0.5 and prior versions, obtains image files from http://upload.wikimedia.org/. SPDY would reduce latency. WP-MIRROR 0.6 (not yet released) uses HTTP/1.1 persistent connections. WP-MIRROR 0.6 has built-in profiling, and the image downloading process now uses 64% less (wall clock) time. Therefore SPDY may not provide much advantage. Thanks also for informing me of the image tarballs.
Conclusion: I will not pursue SPDY, for lack of a requirement. Action Item: WP-MIRROR 0.6 will make use of image tarballs.
- RSYNC
Thanks for letting me know that dumps and tarballs are available using rsync. I much prefer rsync over http and ftp. I mirror the Debian archive, and recently switched from apt-mirror which uses wget, to ftpsync which uses rsync; and am very happy with the results.
Action Item: WP-MIRROR 0.6 will make use of rsync.
Are you in any of the Debian mirror rotations? (in DNS. or maybe it's an internal mirror?) If you can handle the load / storage then you could become a Wikimedia mirror as well. Actually I'm typing this message on a squeeze box right now. :)
btw, for image tarballs: I'm not sure offhand if they exist for all wikis? I think maybe some larger wikis don't have them. rsync is also available for the images individually. (1 file per file)
-Jeremy