Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TruthSocial ‧ Privacy Policy ‧ not tracked anymore #328

Closed
1 task
OTA-Bot opened this issue Jun 29, 2024 · 28 comments
Closed
1 task

TruthSocial ‧ Privacy Policy ‧ not tracked anymore #328

OTA-Bot opened this issue Jun 29, 2024 · 28 comments
Labels
timeout Fetching fails with a timeout error [managed by OTA]

Comments

@OTA-Bot
Copy link
Contributor

OTA-Bot commented Jun 29, 2024

No version of the Privacy Policy of service Truth Social is recorded anymore since 29 June 2024 at 0:34: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

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-29T00:34:55Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-06-29T00:34: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 OTA-Bot added the 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] label Jun 29, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jun 29, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Jun 29, 2024
@OTA-Bot OTA-Bot reopened this Jul 1, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jul 2, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Jul 2, 2024
@OTA-Bot OTA-Bot reopened this Jul 3, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jul 4, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Jul 4, 2024
@OTA-Bot OTA-Bot reopened this Jul 5, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jul 5, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Jul 5, 2024
@OTA-Bot OTA-Bot reopened this Jul 6, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jul 6, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Jul 6, 2024
@OTA-Bot OTA-Bot reopened this Jul 8, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jul 8, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Jul 8, 2024
@OTA-Bot OTA-Bot reopened this Jul 9, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jul 10, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Jul 10, 2024
@OTA-Bot OTA-Bot reopened this Jul 25, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jul 25, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Jul 25, 2024
@OTA-Bot OTA-Bot reopened this Jul 27, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jul 27, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Jul 27, 2024
@OTA-Bot OTA-Bot reopened this Jul 28, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jul 28, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Jul 28, 2024
@OTA-Bot OTA-Bot closed this as completed Aug 24, 2024
@OTA-Bot OTA-Bot reopened this Aug 25, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Aug 25, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Aug 25, 2024
@OTA-Bot OTA-Bot reopened this Aug 27, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Aug 28, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Aug 28, 2024
@OTA-Bot OTA-Bot reopened this Aug 29, 2024
@OTA-Bot OTA-Bot reopened this Aug 31, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Sep 1, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Sep 1, 2024
@OTA-Bot OTA-Bot reopened this Sep 2, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Sep 3, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Sep 3, 2024
@OTA-Bot OTA-Bot reopened this Sep 4, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Sep 4, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Sep 4, 2024
@OTA-Bot OTA-Bot reopened this Sep 5, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Sep 5, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Sep 5, 2024
@smmkolesnikov smmkolesnikov reopened this Sep 5, 2024
@smmkolesnikov
Copy link
Collaborator

Fixed here: #359

@OTA-Bot OTA-Bot reopened this Jan 19, 2025
@OTA-Bot OTA-Bot added timeout Fetching fails with a timeout error [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Jan 19, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 19, 2025

No version of the Privacy Policy of service Truth Social is recorded anymore since 19 January 2025 at 12:38:11 UTC

The source document has not been recorded in a snapshot, thus no version can be extracted.

What went wrong

How to resume tracking

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

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2025-01-19T12:38:11Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-19T12:38: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
Copy link
Contributor Author

OTA-Bot commented Jan 20, 2025

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
timeout Fetching fails with a timeout error [managed by OTA]
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smmkolesnikov @OTA-Bot