`Instagram` ‧ `Community Guidelines` ‧ not tracked anymore

OTA-Bot commented 10 months ago

No version of the `Community Guidelines` of service `Instagram` is recorded anymore since 10 January 2024 at 12:32:50 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

request to https://transparency.fb.com/policies/community-standards/regulated-goods/ failed, reason:
request to https://transparency.fb.com/policies/community-standards/sexual-exploitation-adults/ failed, reason:

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-10T12:32:50Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-01-10T12:32: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 commented 10 months ago

Tracking resumed

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

OTA-Bot commented 10 months ago

No version of the `Community Guidelines` of service `Instagram` is recorded anymore since 16 January 2024 at 12:32:23 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

Received HTTP code 500 when trying to fetch 'https://transparency.fb.com/policies/community-standards/dangerous-individuals-organizations/'

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-16T12:32:23Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-01-16T12:32:23Z 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 9 months ago

No version of the `Community Guidelines` of service `Instagram` is recorded anymore since 6 February 2024 at 12:32: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

request to https://transparency.fb.com/policies/community-standards/restricted-goods-services/ failed, reason:

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-02-06T12:32:28Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-02-06T12:32: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 commented 7 months ago

No version of the `Community Guidelines` of service `Instagram` is recorded anymore since 17 April 2024 at 6:34:30 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":"#policy-details h4:first-child","endAfter":"#policy-details"}

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-17T06:34:30Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-04-17T06:34:30Z 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 `Instagram` is recorded anymore since 15 May 2024 at 0:34:21 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

Received HTTP code 500 when trying to fetch 'https://transparency.fb.com/policies/community-standards/spam/'
Received HTTP code 404 when trying to fetch 'https://transparency.fb.com/policies/community-standards/bullying-harassment/'
Received HTTP code 404 when trying to fetch 'https://transparency.fb.com/policies/community-standards/child-sexual-exploitation-abuse-nudity/'

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-15T00:34:21Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-05-15T00:34:21Z 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 `Instagram` is recorded anymore since 15 May 2024 at 6:34:26 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":"#policy-details h4:first-child","endAfter":"#policy-details"}

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

No version of the `Community Guidelines` of service `Instagram` is recorded anymore since 15 May 2024 at 12:34:36 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

request to https://transparency.meta.com/policies/community-standards/fraud-deception/ failed, reason:
request to https://transparency.meta.com/policies/community-standards/child-sexual-exploitation-abuse-nudity/ failed, reason:
request to https://transparency.meta.com/policies/community-standards/adult-nudity-sexual-activity/ failed, reason:

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

No version of the `Community Guidelines` of service `Instagram` is recorded anymore since 15 May 2024 at 18:31:54 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":"#policy-details h4:first-child","endAfter":"#policy-details"}

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-15T18:31:54Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-05-15T18:31:54Z 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 `Instagram` is recorded anymore since 30 June 2024 at 0:31:47 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: request to https://transparency.meta.com/policies/community-standards/dangerous-individuals-organizations/ failed, reason:

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-06-30T00:31:47Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-06-30T00:31:47Z 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 `Instagram` is recorded anymore since 30 June 2024 at 12:31:56 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 "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}

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-06-30T12:31:56Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-06-30T12:31:56Z 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 `Instagram` is recorded anymore since 4 July 2024 at 12:32:18 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: request to https://transparency.meta.com/policies/community-standards/inauthentic-behavior/ failed, reason:
Fetch failed: request to https://transparency.meta.com/policies/community-standards/regulated-goods/ failed, reason:
Fetch failed: request to https://transparency.meta.com/policies/community-standards/sexual-solicitation/ failed, reason:
Fetch failed: request to https://transparency.meta.com/policies/community-standards/child-sexual-exploitation-abuse-nudity/ failed, reason:
Fetch failed: request to https://transparency.meta.com/policies/community-standards/bullying-harassment/ failed, reason:
Fetch failed: request to https://transparency.meta.com/policies/community-standards/hate-speech/ failed, reason:
Fetch failed: request to https://transparency.meta.com/policies/community-standards/violent-graphic-content/ failed, reason:

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:32:18Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-07-04T12:32:18Z 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 `Instagram` is recorded anymore since 5 July 2024 at 0:31:50 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 "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}
Extract failed: The "start" selector has no match in document in: {"startBefore":"#policy-details h4:first-child","endAfter":"#policy-details"}

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

smmkolesnikov commented 2 months ago

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

OTA-Bot commented 1 month ago

No version of the `Community Guidelines` of service `Instagram` is recorded anymore since 25 September 2024 at 12:31:41 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 404 when trying to fetch 'https://transparency.fb.com/policies/community-standards/account-integrity-and-authentic-identity/'

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-25T12:31:41Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-09-25T12:31:41Z 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/365

OTA-Bot commented 1 month ago

No version of the `Community Guidelines` of service `Instagram` is recorded anymore since 16 October 2024 at 0:32:26 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: request to https://transparency.meta.com/policies/community-standards/restricted-goods-services/ failed, reason:

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-16T00:32:26Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-10-16T00:32: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 commented 1 month ago

Tracking resumed

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

OTA-Bot commented 1 week ago

No version of the `Community Guidelines` of service `Instagram` is recorded anymore since 13 November 2024 at 0:34:54 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 "[role=main]" has no match in the web page at 'https://help.instagram.com/477434105621119'

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

OpenTermsArchive / pga-declarations