Skip to content
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

MSNTerms of Service ‧ not tracked anymore #1083

Closed
1 task
OTA-Bot opened this issue Oct 18, 2023 · 29 comments
Closed
1 task

MSNTerms of Service ‧ not tracked anymore #1083

OTA-Bot opened this issue Oct 18, 2023 · 29 comments
Labels
403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] good first issue Suitable for new contributors — welcome 😊

Comments

@OTA-Bot
Copy link
Collaborator

OTA-Bot commented Oct 18, 2023

No version of the Terms of Service of service MSN is recorded anymore since 18 October 2023 at 15:05:15 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2023-10-18T15:05:15Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2023-10-18T15:05:15Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot OTA-Bot added the selectors Extraction selectors are outdated [managed by OTA] label Oct 18, 2023
@Ndpnt Ndpnt added the good first issue Suitable for new contributors — welcome 😊 label Oct 18, 2023
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Oct 20, 2023

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Oct 20, 2023
@OTA-Bot OTA-Bot added 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] and removed selectors Extraction selectors are outdated [managed by OTA] labels Dec 4, 2023
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Dec 4, 2023

No version of the Terms of Service of service MSN is recorded anymore since 4 December 2023 at 7:12:16 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2023-12-04T07:12:16Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2023-12-04T07:12:16Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot OTA-Bot added timeout Fetching fails with a timeout error [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Jan 21, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jan 21, 2024

No version of the Terms of Service of service MSN is recorded anymore since 21 January 2024 at 12:39:20 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-01-21T12:39:20Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-01-21T12:39:20Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot OTA-Bot reopened this Jul 13, 2024
@OTA-Bot OTA-Bot added 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] and removed timeout Fetching fails with a timeout error [managed by OTA] labels Jul 13, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jul 13, 2024

No version of the Terms of Service of service MSN is recorded anymore since 13 July 2024 at 6:10:36 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-07-13T06:10:36Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-07-13T06:10:36Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jul 13, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Jul 13, 2024
@OTA-Bot OTA-Bot reopened this Aug 4, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Aug 5, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Aug 9, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Aug 9, 2024
@OTA-Bot OTA-Bot reopened this Aug 10, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Aug 11, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Aug 11, 2024
@OTA-Bot OTA-Bot reopened this Aug 16, 2024
@OTA-Bot OTA-Bot added timeout Fetching fails with a timeout error [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Aug 16, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Aug 16, 2024

No version of the Terms of Service of service MSN is recorded anymore since 16 August 2024 at 18:12:06 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-08-16T18:12:06Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-08-16T18:12:06Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot OTA-Bot added the 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] label Sep 7, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Sep 7, 2024

No version of the Terms of Service of service MSN is recorded anymore since 7 September 2024 at 6:11:08 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-09-07T06:11:08Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-09-07T06:11:08Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot OTA-Bot added timeout Fetching fails with a timeout error [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Sep 8, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Sep 8, 2024

No version of the Terms of Service of service MSN is recorded anymore since 8 September 2024 at 18:10:59 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-09-08T18:10:59Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-09-08T18:10:59Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Sep 9, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Sep 9, 2024
@OTA-Bot OTA-Bot reopened this Oct 29, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Oct 29, 2024

No version of the Terms of Service of service MSN is recorded anymore since 29 October 2024 at 18:10:15 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-10-29T18:10:15Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-10-29T18:10:15Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot OTA-Bot added 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] and removed timeout Fetching fails with a timeout error [managed by OTA] labels Nov 2, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Nov 2, 2024

No version of the Terms of Service of service MSN is recorded anymore since 2 November 2024 at 18:10:28 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-11-02T18:10:28Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-02T18:10:28Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot OTA-Bot added timeout Fetching fails with a timeout error [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Nov 3, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Nov 3, 2024

No version of the Terms of Service of service MSN is recorded anymore since 3 November 2024 at 18:11:50 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-11-03T18:11:50Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-03T18:11:50Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot OTA-Bot added 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] and removed timeout Fetching fails with a timeout error [managed by OTA] labels Nov 4, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Nov 4, 2024

No version of the Terms of Service of service MSN is recorded anymore since 4 November 2024 at 6:09:31 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-11-04T06:09:31Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-04T06:09:31Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot OTA-Bot added timeout Fetching fails with a timeout error [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Nov 4, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Nov 4, 2024

No version of the Terms of Service of service MSN is recorded anymore since 4 November 2024 at 18:11:45 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-11-04T18:11:45Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-04T18:11:45Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot OTA-Bot added 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] and removed timeout Fetching fails with a timeout error [managed by OTA] labels Nov 5, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Nov 5, 2024

No version of the Terms of Service of service MSN is recorded anymore since 5 November 2024 at 6:09:38 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-11-05T06:09:38Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-05T06:09:38Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Nov 6, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Nov 6, 2024
@OTA-Bot OTA-Bot reopened this Jan 1, 2025
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jan 1, 2025

No version of the Terms of Service of service MSN is recorded anymore since 1 January 2025 at 6:10:49 UTC

The source document has not been recorded in a snapshot, thus no version can be extracted.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2025-01-01T06:10:49Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-01T06:10:49Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jan 1, 2025

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] good first issue Suitable for new contributors — welcome 😊
Projects
None yet
Development

No branches or pull requests

2 participants