Agreed; this is restoration in progress
I have resolved to edit my posts where I uploaded attachments and retarget them back to my domain. I am hesitant to edit the incurred typos because this can be corrected through a couple paths, namely:
- Restoration from backup with proper character translation
- Development of substitution scripts
It’s not rocket science; I do this pretty often as part of my normal gig. Sadly I am standing on the sidelines watching the imagined drama unfold and unable to help because the technology that I know and use is incompatible with the host and environment.
Think about it: This began on Feb 28th and now we’re a week later and there are still problems. This tells me a lot about the ES as an application. I don’t think it is much of a stretch to guess that the part that is missing is a rock-solid daily backup & restoration plan with a reliable host.
Now it could be that the host was targeted and the files corrupted, but that shouldn’t affect the previous day or two or twelve if the content is burned off to BR; kinda hard to corrupt a history of physical data. But this gets into supposition, though difficult to ignore given the state of today and the evidence at hand.
Regardless, my modus operandi is changed henceforth, and all future resources will derive from my servers.
O’ cruel is the world,
KF