# Make Discourse play nice with the Wayback Machine

**URL:** <https://meta.discourse.org/t/make-discourse-play-nice-with-the-wayback-machine/34579>\
**Category:** Feature\
**Created:** [October 16, 2015, 2:39am UTC](https://meta.discourse.org/t/make-discourse-play-nice-with-the-wayback-machine/34579 "2015-10-16T02:39:46Z")\
**Posts on this page:** 1\
**Showing post:** 50

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [May 14, 2020, 1:14am UTC](https://meta.discourse.org/t/make-discourse-play-nice-with-the-wayback-machine/34579/50 "2020-05-14T01:14:29Z")

</div>

Replay is currently broken, the JS runs and the Ember Router breaks due to the pathname change.

Thanks to the improved browser detection from @david, there is an extremely ugly but also tempting fix to get new captures to render properly: just patch browser-detect so it detects the replay and yanks out the `noscript` version.

[https://github.com/riking/discourse/commit/6a83c83bd3acab37f7a3e24f6aa4a14081bb2249](https://github.com/riking/discourse/commit/6a83c83bd3acab37f7a3e24f6aa4a14081bb2249)

The problem is, if we start serving that script, and by some miracle the JS starts being able to run, all the old archived pages are forced into the no-js view.

~~Now that I write that out, you know, that’s probably not too bad of a price to pay for getting working archive playbacks _today_. ([Draft PR](https://github.com/discourse/discourse/pull/9775))~~ I have been talked out of actually doing this.

---

_[View the full topic](https://meta.discourse.org/t/make-discourse-play-nice-with-the-wayback-machine/34579)._