For the last 6 to 7 weeks the Wayback Machine has had a lot of problems which have NOT been acknowledged on their website. From my observations as a user, the Wayback Machine appears to consist to two categories of memory: short-term and long-term. During the period of difficulties parts of the short-term memory would completely disappear, for periods spanning several day, from the “Browse History” display page which provides a graphic view of the Archive. Then very slowly, sometimes spanning 7 days, the missing content was restored, a task for which I give the Archive high marks. We tend to forget that with the Wayback Machine now operating in near real-time, it was not too many years ago that the update latency was 6 months and not 6 seconds.
When using the Wayback Machine, there are things I can do with Epic which I can’t do with any other browser such as running several dozen page archives in parallel. This may also explain how I shot myself in the foot if one of these tasks didn’t terminate properly. In keeping with Epic’s commitment to Internet Freedom, there are some interesting synergies between Epic and the Wayback Machine which I will discuss in another post in the product enhancements section.
How may parallel tasks can Epic support? The Wayback Machine can be used as web-proxy browser and I could launch a very large number of tasks if I put my mind to it.
]]>I don't think you should have to uninstall Epic.
Let us know if anything works!
]]>Sorry for inconvenience, did you check other sites are loading properly.
I have tested from our end, archive.org loading fine for me.