`X` ‧ `Deceased Users` ‧ not tracked anymore

OTA-Bot commented 3 months ago

No version of the `Deceased Users` of service `X` is recorded anymore since 6 August 2024 at 0:35:52 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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:52Z 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:52Z 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/340

OTA-Bot commented 3 weeks ago

No version of the `Deceased Users` of service `X` is recorded anymore since 9 November 2024 at 0:37:26 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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

Tracking resumed

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

OTA-Bot commented 3 weeks ago

No version of the `Deceased Users` of service `X` is recorded anymore since 10 November 2024 at 0:39:17 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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

Tracking resumed

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

OTA-Bot commented 3 weeks ago

No version of the `Deceased Users` of service `X` is recorded anymore since 11 November 2024 at 0:37:40 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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

Tracking resumed

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

OTA-Bot commented 3 weeks ago

No version of the `Deceased Users` of service `X` is recorded anymore since 12 November 2024 at 0:39:16 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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

Tracking resumed

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

OTA-Bot commented 2 weeks ago

No version of the `Deceased Users` of service `X` is recorded anymore since 13 November 2024 at 0:40:09 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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

Tracking resumed

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

OTA-Bot commented 2 weeks ago

No version of the `Deceased Users` of service `X` is recorded anymore since 14 November 2024 at 0:38:02 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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

Tracking resumed

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

OTA-Bot commented 2 weeks ago

No version of the `Deceased Users` of service `X` is recorded anymore since 17 November 2024 at 0:39:11 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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

Tracking resumed

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

OTA-Bot commented 2 weeks ago

No version of the `Deceased Users` of service `X` is recorded anymore since 18 November 2024 at 0:39:45 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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

If none of the above works

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

References

OTA-Bot commented 2 weeks ago

Tracking resumed

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

OTA-Bot commented 2 weeks ago

No version of the `Deceased Users` of service `X` is recorded anymore since 19 November 2024 at 0:38:47 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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-19T00:38:47Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-19T00:38: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 1 week 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 `Deceased Users` of service `X` is recorded anymore since 20 November 2024 at 0:37:55 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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-20T00:37:55Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-20T00:37:55Z 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 week 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 `Deceased Users` of service `X` is recorded anymore since 22 November 2024 at 0:39:17 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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-22T00:39:17Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-22T00:39:17Z 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 week 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 `Deceased Users` of service `X` is recorded anymore since 23 November 2024 at 0:39:41 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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

OTA-Bot commented 1 week 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 `Deceased Users` of service `X` is recorded anymore since 24 November 2024 at 0:39:24 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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-24T00:39:24Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-24T00:39:24Z 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 week 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 `Deceased Users` of service `X` is recorded anymore since 26 November 2024 at 0:39:44 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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-26T00:39:44Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-26T00:39: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 6 days ago

Tracking resumed

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

OTA-Bot commented 6 days ago

No version of the `Deceased Users` of service `X` is recorded anymore since 27 November 2024 at 0:39:56 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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-27T00:39:56Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-27T00:39: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 5 days ago

Tracking resumed

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

OTA-Bot commented 5 days ago

No version of the `Deceased Users` of service `X` is recorded anymore since 28 November 2024 at 0:39:47 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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

Tracking resumed

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

OTA-Bot commented 4 days ago

No version of the `Deceased Users` of service `X` is recorded anymore since 29 November 2024 at 0:40:10 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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-29T00:40:10Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-29T00:40: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 commented 3 days ago

Tracking resumed

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

OTA-Bot commented 3 days ago

No version of the `Deceased Users` of service `X` is recorded anymore since 30 November 2024 at 0:39:33 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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-30T00:39:33Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-11-30T00:39: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 2 days ago

Tracking resumed

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

OTA-Bot commented 2 days ago

No version of the `Deceased Users` of service `X` is recorded anymore since 1 December 2024 at 0:39:23 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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-12-01T00:39:23Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-12-01T00:39: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 1 day ago

Tracking resumed

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

OTA-Bot commented 1 day ago

No version of the `Deceased Users` of service `X` is recorded anymore since 2 December 2024 at 0:37:55 UTC

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

What went wrong

Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account'

How to resume tracking

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

[ ] https://help.x.com/en/rules-and-policies/contact-twitter-about-media-on-a-deceased-family-members-account

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-12-02T00:37:55Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-12-02T00:37:55Z 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 19 hours ago

Tracking resumed

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

OpenTermsArchive / pga-declarations