Switch Twitter link to some Nitter instance #489
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This kind of reverts 3f1c43e, since now we'll know if that link goes down. Twitter cannot be used, since like that commit mentions, Twitter now blocks automation (thanks to a certain Elongated Muskrat), which includes mdbook-linkcheck. The choice of Nitter instance is motivated by a few points. First, a list of instances is available from Nitter's GitHub wiki (https://github.com/zedeus/nitter/wiki/Instances). The first parameter in the choice is the region; there are three (3) "anycast" instances, which may (1) reduce latency for readers of Pan Docs, and (2) reduce the load of Pan Docs' link-checking itself (by distributing across several servers behind the anycast). I think, anyway. One of these instances is not updated, which is not a good sign for reliability either. Then, it turns out several instances block HTTP HEAD requests like Twitter (but not GET, suggesting it is intentional); of the remaining two, only the chosen one doesn't.
|
Right, I forgot to mention this: I also considered https://twiiit.com/, but unfortunately, some of the instances I got in my testing had badly configured TLS, and others blocked HEAD requests; hence picking a known-good one instead. |
|
What about Wayback machine ? |
avivace
requested changes
Jun 23, 2023
Co-authored-by: Antonio Vivace <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This kind of reverts 3f1c43e, since now we'll know if that link goes down. Twitter cannot be used, since like that commit mentions, Twitter now blocks automation (thanks to a certain Elongated Muskrat), which includes mdbook-linkcheck.
The choice of Nitter instance is motivated by a few points. First, a list of instances is available from Nitter's GitHub wiki (https://github.com/zedeus/nitter/wiki/Instances).
The first parameter in the choice is the region; there are three (3) "anycast" instances, which may (1) reduce latency for readers of Pan Docs, and (2) reduce the load of Pan Docs' link-checking itself (by distributing across several servers behind the anycast). I think, anyway.
One of these instances is not updated, which is not a good sign for reliability either.
Then, it turns out several instances block HTTP HEAD requests like Twitter (but not GET, suggesting it is intentional); of the remaining two, only the chosen one doesn't.