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

XCommunity Guidelines ‧ not tracked anymore #260

Open
19 tasks
OTA-Bot opened this issue Mar 25, 2024 · 80 comments
Open
19 tasks

XCommunity Guidelines ‧ not tracked anymore #260

OTA-Bot opened this issue Mar 25, 2024 · 80 comments
Labels
to clarify Default failure label [managed by OTA]

Comments

@OTA-Bot
Copy link
Contributor

OTA-Bot commented Mar 25, 2024

No version of the Community Guidelines of service X is recorded anymore since 25 March 2024 at 6:37:09 UTC

The source documents have been recorded in snapshots, 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-03-25T06:37:09Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-03-25T06:37:09Z 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
Contributor Author

OTA-Bot commented Mar 25, 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 Mar 25, 2024
@OTA-Bot OTA-Bot added selectors Extraction selectors are outdated [managed by OTA] and removed timeout labels May 22, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented May 22, 2024

No version of the Community Guidelines of service X is recorded anymore since 22 May 2024 at 0:39:16 UTC

The source documents have been recorded in snapshots, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

  • The "start" selector has no match in document in: {"startBefore":"h1","endAfter":"[class*="rich-text-v"]"}

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-05-22T00:39:16Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-05-22T00:39: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
Copy link
Contributor Author

OTA-Bot commented Jun 27, 2024

Tracking resumed

A new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Jun 27, 2024
@OTA-Bot OTA-Bot reopened this Aug 6, 2024
@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 Aug 6, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Aug 6, 2024

No version of the Community Guidelines of service X is recorded anymore since 6 August 2024 at 0:35:53 UTC

The source documents have been recorded in snapshots, 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-06T00:35:53Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-08-06T00:35:53Z 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

@smmkolesnikov
Copy link
Collaborator

Fixed here: #340

@OTA-Bot OTA-Bot reopened this Aug 16, 2024
@OTA-Bot OTA-Bot added to clarify Default failure label [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
Contributor Author

OTA-Bot commented Aug 16, 2024

No version of the Community Guidelines of service X is recorded anymore since 16 August 2024 at 0:37:34 UTC

The source documents have been recorded in snapshots, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded

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-16T00:37:34Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-08-16T00:37:34Z 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

@smmkolesnikov
Copy link
Collaborator

Hi @OpenTermsArchive/core!

Something odd is going on here with X CG. No snapshots were recorded for 2 months, yet locally it works correctly. Just did a check-up here with a test pull request, and it also returned no errors. Tried to switch client scripts and change selectors, but to no avail.

What could be the potential reason for that?

@clementbiron clementbiron added the timeout Fetching fails with a timeout error [managed by OTA] label Sep 10, 2024
@clementbiron
Copy link
Member

It's very similar to #296, here too, for some reason, the server can't complete the requests.

I suggest that we try to increase the maximum time allowed for a request by changing the value (from 30000 by default to 60000) of navigationTimeout in the fetcher module in the production configuration file. @MattiSG what do you think ?

@OTA-Bot OTA-Bot added 503 Fetching fails with a 503 (service unavailable) HTTP code [managed by OTA] and removed to clarify Default failure label [managed by OTA] timeout Fetching fails with a timeout error [managed by OTA] labels Oct 16, 2024
@OTA-Bot OTA-Bot added 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] and removed to clarify Default failure label [managed by OTA] labels Jan 10, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 10, 2025

No version of the Community Guidelines of service X is recorded anymore since 10 January 2025 at 0:39:14 UTC

The source documents have not been recorded in snapshots, thus no version can be extracted.

What went wrong

  • Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/twitter-impersonation-and-deceptive-identities-policy'
  • Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/manipulated-media'
  • Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/platform-manipulation'
  • Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/copypasta-duplicate-content'
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded

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-10T00:39:14Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-10T00:39:14Z 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 to clarify Default failure label [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Jan 10, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 10, 2025

No version of the Community Guidelines of service X is recorded anymore since 10 January 2025 at 12:38:32 UTC

The source documents have not been recorded in snapshots, thus no version can be extracted.

What went wrong

  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded

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-10T12:38:32Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-10T12:38:32Z 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 to clarify Default failure label [managed by OTA] labels Jan 12, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 12, 2025

No version of the Community Guidelines of service X is recorded anymore since 12 January 2025 at 12:38:49 UTC

The source documents have not been recorded in snapshots, thus no version can be extracted.

What went wrong

  • Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/twitter-impersonation-and-deceptive-identities-policy'
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded

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-12T12:38:49Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-12T12:38: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 OTA-Bot added to clarify Default failure label [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Jan 13, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 13, 2025

No version of the Community Guidelines of service X is recorded anymore since 13 January 2025 at 0:38:22 UTC

The source documents have not been recorded in snapshots, thus no version can be extracted.

What went wrong

  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded

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-13T00:38:22Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-13T00:38:22Z 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 to clarify Default failure label [managed by OTA] labels Jan 18, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 18, 2025

No version of the Community Guidelines of service X is recorded anymore since 18 January 2025 at 0:38:40 UTC

The source documents have not been recorded in snapshots, thus no version can be extracted.

What went wrong

  • Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/twitter-impersonation-and-deceptive-identities-policy'
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded

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-18T00:38:40Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-18T00:38:40Z 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 to clarify Default failure label [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Jan 18, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 18, 2025

No version of the Community Guidelines of service X is recorded anymore since 18 January 2025 at 12:39:10 UTC

The source documents have not been recorded in snapshots, thus no version can be extracted.

What went wrong

  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded

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-18T12:39:10Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-18T12:39:10Z 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 to clarify Default failure label [managed by OTA] labels Jan 24, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 24, 2025

No version of the Community Guidelines of service X is recorded anymore since 24 January 2025 at 0:38:26 UTC

The source documents have not been recorded in snapshots, thus no version can be extracted.

What went wrong

  • Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/financial-scam'
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded

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-24T00:38:26Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-24T00:38:26Z 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 to clarify Default failure label [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Jan 24, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 24, 2025

No version of the Community Guidelines of service X is recorded anymore since 24 January 2025 at 12:39:34 UTC

The source documents have not been recorded in snapshots, thus no version can be extracted.

What went wrong

  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded

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-24T12:39:34Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-24T12:39:34Z 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 to clarify Default failure label [managed by OTA] labels Jan 25, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 25, 2025

No version of the Community Guidelines of service X is recorded anymore since 25 January 2025 at 0:38:31 UTC

The source documents have not been recorded in snapshots, thus no version can be extracted.

What went wrong

  • Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/platform-manipulation'
  • Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/twitter-impersonation-and-deceptive-identities-policy'
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded

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-25T00:38:31Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-25T00:38: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 to clarify Default failure label [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Jan 25, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 25, 2025

No version of the Community Guidelines of service X is recorded anymore since 25 January 2025 at 12:38:53 UTC

The source documents have not been recorded in snapshots, thus no version can be extracted.

What went wrong

  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded
  • Fetch failed: Navigation timeout of 30000 ms exceeded

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-25T12:38:53Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-25T12:38:53Z 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
to clarify Default failure label [managed by OTA]
Projects
None yet
Development

No branches or pull requests

3 participants