Do not use HTTP protocol for URLs in podcast namespace tags #414
Conversation
This file contains hidden or 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
|
Thanks! Will review/merge today. |
|
I'd like to query the requirement here. It is best practice to use |
|
I saw this update from Brave Browser that covers a little bit about the complications of HTTPS default and some things to consider: https://brave.com/privacy-updates/22-https-by-default/ |
|
Unfortunately https seems to be the only way to go. As soon as you try to mix https and http all the browsers scream at you. For example many new TLDs (like .app which I'm using) is set to ONLY work on https. That is set by default. |
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 is to comply with the following in the podcast namespace specification: