Massmirror revealed on their blog 5 days back that the reason for the continual problems with their system is due to their moving the entirety of their operations to a new service. They claim no data will be lost but also state that "The site will have random errors and downtime until this redesign is complete". No timetable is given for how long one can expect to be dealing with the fallout from this. This is obviously an untenable situation for us and has provoked much behind the scenes discussion of where we go from here. Aside from Sharebee, which we used initially but whose upload function no longer supports macs, there exist two other file spreading services that I'm aware of: Xirror and Fileberry. Fileberry is much too new on the market for me to have any real confidence in them, though xirror's been around for about as long as massmirror. I (Eric) have made the decision to opt for using Xirror's service, as reflected in today's posts. Jim, understandably feeling burnt after our unfortunate experiences with both Sharebee and Massmirror, has decided to take a wait-and-see approach to Xirror for now and so, for the time being at least will revert to using Rapidshare for his posts. You'll notice from today's posts that Xirror, aside from the inclusion of Rapidshare, offers a different set of hosts that it farms it's links out to (in their case, Filefactory, Netload.in and Uploaded.to). It is perhaps a less immediately appealing array that that offered by either Massmirror or Sharebee, but it's what we'll have to work with currently. Hope it proves to be both stable and acceptable to everyone here. In the meantime, being understandably dubious about Massmirror's assurances that no data will be lost, I'm taking no chances and am culling together all the Rapidshare links from the hundreds of Massmirror post I've made, to safeguard against the possibility of their network permanently going down. This is one situation where I'd definitely rather be safe than sorry.