Oh, that's even trickier to figure out, then. Honestly, I haven't received these reports from any other site, so maybe it's something to do with this particular version. When I put out another public update maybe (hopefully!) the problem will go away.