All battle numbers below 700 million now auto-redirect to Replays.
(All expired battles will redirect to Replays, the auto-redirect just
means the client doesn't need to ask the server if a battle is expired
and wait for an answer before redirecting.)
Chrome peer-pressuring us by locking Notification behind HTTPS... they
also lock plenty of other things behind HTTPS and the trade-off seems
worth-it now.
Ideally, I'd still like to direct people to the landing page of
pokemonshowdown.com, but I no longer think that blocking search
engine access to play.pokemonshowdown.com is the best approach to
achieving that.
This is the search index build script from the Gen 6 Learnsets
repository, slightly rewritten for the PS client environment. It
expects a checkout of the server respository in
`data/Pokemon-Showdown`.
It didn't seem to be helping with the problems the user with weird
header rewriting had, so it didn't serve its intended purpose.
Removing the header saves a negligible amount of bandwidth and
more importantly suppresses an error message in Chrome which
doesn't support it.
There apparently exist very bad security software that MitMs HTTPS
connections to set X-Frame-Options when I didn't want that at all
and actually crossprotocol.html is intended for embedding in an
iframe.
Hopefully this header will allow aforementioned software to take
the hint.
A cache issue prevented Font Awesome from working correctly on third
party servers. CloudFlare's 'purge cache' button didn't work, so this
is kind of a last resort.
Previously, PS would automatically redirect to a replay if linked
to a nonexistent battle room. This has been replaced with a
pop-up message linking to the replay.
Very old battles are still redirected to the replay.
