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

Facebook ‧ Community Guidelines ‧ not tracked anymore #209

Open
25 tasks
OTA-Bot opened this issue Dec 15, 2023 · 13 comments
Open
25 tasks

Facebook ‧ Community Guidelines ‧ not tracked anymore #209

OTA-Bot opened this issue Dec 15, 2023 · 13 comments
Labels
selectors Extraction selectors are outdated [managed by OTA]

Comments

@OTA-Bot
Copy link
Contributor

OTA-Bot commented Dec 15, 2023

No version of the Community Guidelines of service Facebook is recorded anymore since 15 December 2023 at 12:30:03 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

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 2023-12-15T12:30:03Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2023-12-15T12:30:03Z 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 to clarify Default failure label [managed by OTA] label Dec 15, 2023
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Dec 15, 2023

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 Dec 15, 2023
@OTA-Bot OTA-Bot added 500 Fetching fails with a 500 (internal server error) HTTP code [managed by OTA] and removed to clarify Default failure label [managed by OTA] labels Jan 16, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 16, 2024

No version of the Community Guidelines of service Facebook is recorded anymore since 16 January 2024 at 12:30:55 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

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:30:55Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-01-16T12:30: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 selectors Extraction selectors are outdated [managed by OTA] and removed 500 Fetching fails with a 500 (internal server error) HTTP code [managed by OTA] labels Apr 17, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Apr 17, 2024

No version of the Community Guidelines of service Facebook is recorded anymore since 17 April 2024 at 6:32:52 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:32:52Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-04-17T06:32: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

@OTA-Bot OTA-Bot added location Fetch location is outdated [managed by OTA] and removed selectors Extraction selectors are outdated [managed by OTA] labels May 15, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented May 15, 2024

No version of the Community Guidelines of service Facebook is recorded anymore since 15 May 2024 at 0:33:04 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

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:33:04Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-05-15T00:33:04Z 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 selectors Extraction selectors are outdated [managed by OTA] and removed location Fetch location is outdated [managed by OTA] labels May 15, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented May 15, 2024

No version of the Community Guidelines of service Facebook is recorded anymore since 15 May 2024 at 6:33:01 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:33:01Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-05-15T06:33:01Z 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 to clarify Default failure label [managed by OTA] and removed selectors Extraction selectors are outdated [managed by OTA] labels May 24, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented May 24, 2024

No version of the Community Guidelines of service Facebook is recorded anymore since 24 May 2024 at 12:32:52 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

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-24T12:32:52Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-05-24T12:32: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

@OTA-Bot OTA-Bot added selectors Extraction selectors are outdated [managed by OTA] and removed to clarify Default failure label [managed by OTA] labels May 24, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented May 24, 2024

No version of the Community Guidelines of service Facebook is recorded anymore since 24 May 2024 at 18:30: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-05-24T18:30:30Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-05-24T18:30: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 OTA-Bot reopened this Jun 12, 2024
@smmkolesnikov
Copy link
Collaborator

Fixed here: #354

@OTA-Bot OTA-Bot reopened this Sep 13, 2024
@OTA-Bot OTA-Bot added to clarify Default failure label [managed by OTA] and removed selectors Extraction selectors are outdated [managed by OTA] labels Sep 13, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Sep 13, 2024

No version of the Community Guidelines of service Facebook is recorded anymore since 13 September 2024 at 12:30: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

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-13T12:30:21Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-09-13T12:30: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
Copy link
Contributor Author

OTA-Bot commented Sep 14, 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 14, 2024
@OTA-Bot OTA-Bot reopened this Sep 25, 2024
@OTA-Bot OTA-Bot added location Fetch location is outdated [managed by OTA] and removed to clarify Default failure label [managed by OTA] labels Sep 25, 2024
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Sep 25, 2024

No version of the Community Guidelines of service Facebook is recorded anymore since 25 September 2024 at 12:30:20 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

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:30:20Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-09-25T12:30:20Z 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
Copy link
Collaborator

Fixed here: #364

@OTA-Bot OTA-Bot reopened this Jan 7, 2025
@OTA-Bot OTA-Bot added selectors Extraction selectors are outdated [managed by OTA] and removed location Fetch location is outdated [managed by OTA] labels Jan 7, 2025
@OTA-Bot
Copy link
Contributor Author

OTA-Bot commented Jan 7, 2025

No version of the Community Guidelines of service Facebook is recorded anymore since 7 January 2025 at 12:30:40 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 "end" selector has no match in document in: {"startBefore":"h1","endBefore":"body > div > section:last-of-type h6"}

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-07T12:30:40Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2025-01-07T12:30: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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
selectors Extraction selectors are outdated [managed by OTA]
Projects
None yet
Milestone
No milestone
Development

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