`Skynet` ‧ `Terms of Service` ‧ not tracked anymore

tosdr-bot commented 1 month ago

No version of the `Terms of Service` of service `Skynet` is recorded anymore since 22 July 2024 at 11:11:53 UTC

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

What went wrong

Fetch failed: request to https://siasky.net/terms.pdf failed, reason: write EPROTO 807C8F53347F0000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL alert number 80

How to resume tracking

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

[ ] https://siasky.net/terms.pdf

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

tosdr-bot commented 1 month ago

No version of the `Terms of Service` of service `Skynet` is recorded anymore since 25 July 2024 at 5:14:29 UTC

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

What went wrong

Fetch failed: Timed out after 30 seconds when trying to fetch 'https://siasky.net/terms.pdf'

How to resume tracking

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

[ ] https://siasky.net/terms.pdf

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

tosdr-bot commented 1 month ago

No version of the `Terms of Service` of service `Skynet` is recorded anymore since 28 July 2024 at 9:53:58 UTC

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

What went wrong

Fetch failed: request to https://siasky.net/terms.pdf failed, reason: write EPROTO 807C8F53347F0000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL alert number 80

How to resume tracking

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

[ ] https://siasky.net/terms.pdf

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

tosdr-bot commented 1 month ago

No version of the `Terms of Service` of service `Skynet` is recorded anymore since 1 August 2024 at 2:38:54 UTC

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

What went wrong

Fetch failed: Timed out after 30 seconds when trying to fetch 'https://siasky.net/terms.pdf'

How to resume tracking

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

[ ] https://siasky.net/terms.pdf

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

tosdr / tosdr-declarations