/warclight

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: TimeTravel API is unreliable and should not be used #58

Closed
ruebot opened this Issue Jan 15, 2019 · 6 comments

Comments

Assignees

@greebie greebie

@lintool lintool

@ianmilligan1 ianmilligan1

@SamFritz SamFritz

Labels
None yet
Projects
None yet
Milestone
No milestone
6 participants
@ruebot @anjackson @greebie @lintool @ianmilligan1 @SamFritz
@ruebot
Copy link
Member

ruebot commented Jan 15, 2019

The TimeTravel API which is used in this method to create a reply URL link is unreliable.

This thread on the Memento Development list, started in November 2018, raised the issue initially. The recent TravisCI test runs have identified that the issue has now cascaded to our project, which has been raised in the mailing list thread.

So far I believe that we have two options:

  1. Remove the functionality until the problem is fixed.
  2. Use another service, which ultimately means running and maintaining our own service for this functionality.

@ruebot ruebot assigned greebie, lintool, ianmilligan1 and SamFritz Jan 15, 2019

@ruebot

This comment has been minimized.

Sign in to view
Copy link
Member

ruebot commented Jan 28, 2019

Still getting hit with this a lot. Not in the test anymore. I imagine that is a specific removal from their caching system. However, the warclight demo site seems to really suffer a lot from it. We get lots of false positives for reply urls pointing to the UKWA's PyWb instance (👋 @anjackson).

This entire collection comes from sites crawled from a few of the WAHR projects, and playback is all provided via the York University OpenWayback instance.

Looking at slide #25 of Martin's presentation, I wonder if that is because of the large number of false positives coming from the York instance which is an out-of-the-box OpenWayback instance, we some UI modifications.

smart-routing-of-memento-requests-25-638

I wonder if Martin on GitHub?
@ruebot

This comment has been minimized.

Sign in to view
Copy link
Member

ruebot commented Jan 28, 2019

Here are a couple examples:

screenshot_2019-01-28 oli daneault on twitter who the hell came up with elxn2015 elxn42 when fed2015 was right there yes

screenshot_2019-01-28 ukwa pywb access system

screenshot_2019-01-28 blanchlb on twitter duel electoral al canada entre la dreta i els liberals http t co v2ed40cpxk via

screenshot_2019-01-28 ukwa pywb access system 1
@anjackson

This comment has been minimized.

Sign in to view
Copy link

anjackson commented Jan 30, 2019

Unfortunately, this does seem to be a problem with the UKWA pywb installation. The TimeGate isn't behaving correctly as it seems to have been broken by the customisations we have in place: ukwa/ukwa-pywb#37
@ruebot

This comment has been minimized.

Sign in to view
Copy link
Member

ruebot commented Jan 31, 2019

So, if I'm understanding it correctly now, it's not actually the fault of the Time-Travel API? The finger pointing moves again, and I feel silly? 🤕
@anjackson

This comment has been minimized.

Sign in to view
Copy link

anjackson commented Feb 1, 2019

Not as silly as I feel, as it turns out to be our fault.
@ruebot

This comment has been minimized.

Sign in to view
Copy link
Member

ruebot commented Feb 1, 2019

Well, I'll close this, and stand in solidarity of silliness with you 😄

@ruebot ruebot closed this Feb 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment