`X` ‧ `Community Guidelines` ‧ not tracked anymore

OTA-Bot commented 5 months ago

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

Timed out after 30 seconds when trying to fetch 'https://help.twitter.com/en/rules-and-policies/x-rules'
Timed out after 30 seconds when trying to fetch 'https://help.x.com/en/rules-and-policies/violent-entities'
Timed out after 30 seconds when trying to fetch 'https://help.twitter.com/en/rules-and-policies/glorifying-self-harm'
Timed out after 30 seconds when trying to fetch 'https://help.twitter.com/en/rules-and-policies/media-policy'
Timed out after 30 seconds when trying to fetch 'https://help.twitter.com/en/rules-and-policies/personal-information'
Timed out after 30 seconds when trying to fetch 'https://help.twitter.com/en/rules-and-policies/x-trademark-policy'

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 commented 5 months ago

Tracking resumed

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

OTA-Bot commented 3 months ago

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 commented 2 months ago

Tracking resumed

A new version has been recorded.

OTA-Bot commented 1 month ago

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

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/child-safety'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/abusive-behavior'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/perpetrators-of-violent-attacks'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/personal-information'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/glorifying-self-harm'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/regulated-goods-services'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/adult-content'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/hateful-conduct-policy'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/x-rules'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/intimate-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/election-integrity-policy'
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/financial-scam'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/violent-entities'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/violent-content'
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/x-username-squatting'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/copypasta-duplicate-content'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/automated-claims-policy'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/financial-scam'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/x-trademark-policy'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/abusive-profile'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/x-reach-limited'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/counterfeit-goods-policy'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/public-interest'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/x-moments-guidelines-and-principles'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/enforcement-options'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/fair-use-policy'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/enforcement-philosophy'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/x-limits'
Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/copyright-policy'

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 commented 1 month ago

Fixed here: https://github.com/OpenTermsArchive/pga-declarations/pull/340

OTA-Bot commented 1 month ago

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 commented 1 week ago

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 commented 6 days ago

It's very similar to https://github.com/OpenTermsArchive/pga-declarations/issues/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 ?

OpenTermsArchive / pga-declarations