chore: Improve permalinks - Issue #167 #168
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
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.
#167
The problem was solely related to the telegram application on macbooks downloaded from the App store. The decision took a lot more effort than I expected. In the end, I figured out what the problem was, in this case, telegram very selectively allows you to insert links with base64 encoding, so standard methods like btoa() and encodeURIComponent() will not work here. The LZString library came to the rescue with its compressToEncodedURIComponent method, the encoding of which allows you to correctly insert links both in telegram on windows and in telegram on macbooks.
I also added DebugMode to the links, there was no difficulty with that.