`Twitch` ‧ `Community Guidelines` ‧ not tracked anymore

OTA-Bot commented 7 months ago

No version of the `Community Guidelines` of service `Twitch` is recorded anymore since 18 April 2024 at 12:40:07 UTC

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

What went wrong

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-04-18T12:40:07Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-04-18T12:40:07Z 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 6 months ago

No version of the `Community Guidelines` of service `Twitch` is recorded anymore since 26 May 2024 at 18:35:42 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 provided selector ".tsc-subtopic" has no match in the web page at 'https://safety.twitch.tv/s/article/Community-Guidelines?language=en_US'

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-26T18:35:42Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-05-26T18:35:42Z 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 6 months ago

No version of the `Community Guidelines` of service `Twitch` is recorded anymore since 27 May 2024 at 0:38:33 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

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-05-27T00:38:33Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-05-27T00:38:33Z 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

No version of the `Community Guidelines` of service `Twitch` is recorded anymore since 4 July 2024 at 0:35:44 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

Extract failed: The provided selector ".tsc-subtopic" has no match in the web page at 'https://safety.twitch.tv/s/article/Prohibited-Games?language=en_US'
Extract failed: The provided selector ".tsc-subtopic" has no match in the web page at 'https://safety.twitch.tv/s/article/Content-Classification-Guidelines?language=en_US'
Extract failed: The provided selector ".tsc-subtopic" has no match in the web page at 'https://safety.twitch.tv/s/article/Tags-Guidelines?language=en_US'
Extract failed: The provided selector ".tsc-subtopic" has no match in the web page at 'https://safety.twitch.tv/s/article/Usernames?language=en_US'

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-04T00:35:44Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-07-04T00:35:44Z 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

No version of the `Community Guidelines` of service `Twitch` is recorded anymore since 4 July 2024 at 12:36:07 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

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-04T12:36:07Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-07-04T12:36:07Z 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 4 months ago

No version of the `Community Guidelines` of service `Twitch` is recorded anymore since 1 August 2024 at 0:35:46 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

Extract failed: The provided selector ".tsc-subtopic" has no match in the web page at 'https://safety.twitch.tv/s/article/Community-Guidelines?language=en_US'
Extract failed: The provided selector ".tsc-subtopic" has no match in the web page at 'https://safety.twitch.tv/s/article/Emote-Policy?language=en_US'
Extract failed: The provided selector ".tsc-subtopic" has no match in the web page at 'https://safety.twitch.tv/s/article/Tags-Guidelines?language=en_US'
Extract failed: The provided selector ".tsc-subtopic" has no match in the web page at 'https://safety.twitch.tv/s/article/Usernames?language=en_US'

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-01T00:35:46Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-08-01T00:35:46Z 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 4 months ago

No version of the `Community Guidelines` of service `Twitch` is recorded anymore since 1 August 2024 at 12:35:28 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

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-01T12:35:28Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-08-01T12:35: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

smmkolesnikov commented 3 months ago

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

OTA-Bot commented 3 months ago

No version of the `Community Guidelines` of service `Twitch` is recorded anymore since 26 August 2024 at 0:36:08 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

Extract failed: The provided selector ".tsc-subtopic-content" has no match in the web page at 'https://safety.twitch.tv/s/article/Emote-Policy?language=en_US'
Extract failed: The provided selector ".tsc-subtopic-content" has no match in the web page at 'https://safety.twitch.tv/s/article/Tags-Guidelines?language=en_US'
Extract failed: The provided selector ".tsc-subtopic-content" has no match in the web page at 'https://safety.twitch.tv/s/article/Usernames?language=en_US'

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-26T00:36:08Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-08-26T00:36: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 commented 3 months ago

No version of the `Community Guidelines` of service `Twitch` is recorded anymore since 26 August 2024 at 12:36:25 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

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-26T12:36:25Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-08-26T12:36:25Z 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 3 months ago

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

smmkolesnikov commented 3 months ago

Hi @OpenTermsArchive/core! Need your assistance with this one.

Just learned that the engine didn't record any snapshots of any of the Twitch policies for 1-2 weeks. The links are valid, locally I also managed to record shapshots as usual. This is some sort of issue I didn't see before. What could be causing it?

clementbiron commented 2 months ago

You're right, the last snapshot of the Twitch Community Guidelines was recorded on 26 August. I've also managed to record snapshots locally so for some reason the documents aren't accessible from the PGA server (Fetch failed: Navigation timeout of 30000 ms exceeded). @MattiSG do you have any ideas or other explanations?

smmkolesnikov commented 1 month ago

Hi @OpenTermsArchive/core! Are there any news on the timeout issues that we registered in Twitch, X and Reddit CGs?

MattiSG commented 1 month ago

Unfortunately I don't have any better idea than thinking your server has been blocked by the service providers 😕 you might regain tracking by changing your outgoing IP address.

OpenTermsArchive / pga-declarations