@semanticist: genius. @revdrdldavis, @somename, can you visit the link @semanticist posted from your browser to see if it works? If not, I have a feeling this is the problem. It explains why our staff can’t reproduce it. We will update our error message to reflect this.
I have confirmation from at least one user experiencing the specification error that this is not the problem. His browser was able to load https://www.amazonsha256.com/ and get the “Success” message but he still cannot load the specification error.
One user yesterday that reported this problem via email told me that deleting the cache in his browser fixed it. I’m not sure if this will work for any of you but if it does, please report back here.
I’m still actively investigating what is causing this problem. Stay tuned.
All, I pushed another update moments ago that I hope will fix this problem. Anyone that is still having this problem can you reload Hookpad and see if the problem persists (and report back here)? So sorry all of you have been struggling with this. It has been difficult to fix because we can’t reproduce the behavior you are seeing.
All, thank your for your patience with this bug and helping us debug it. This morning we finally figured out its cause and pushed a fix to production. Thank your for waiting it out. The fact that deleting your cache fixed it was very helpful in leading us to the solution.