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.

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

Guid-enabled fast-follow share links should use hash in a key=value pattern #316

Open
dascritch opened this issue Nov 23, 2021 · 3 comments

Comments

@dascritch
Copy link

dascritch commented Nov 23, 2021

In the podcast namespace document, “chapter on GUID”, you provide a clever solution to indicate a podcast source across platforms.

But you're using the whole hash parameters, that may be an issue if you add a partial url hash as in a Media Fragment Standard. By example, using a time indication on a named audio element in a web page (personal example with #sound&t=10m)

I recommend to use instead a notation as follow :

The format of the link is https://(a podcast website link)#fastfollow-(type)=(a podcast guid)

In case of a fragmented hash with media fragment support, it would become : https://(page)#t=10&fastfollow-podcast=(guid)

Comma , can be used in the values part of the fragment for separating more elements. It may be fastfollow-podcast=(guid),(hostname)

@dascritch
Copy link
Author

Please note the key=value hash-fragment notation is used in some traffic analysis : I see some <url>#xtor=<mediaid>. This kind of use case is relevant as you don't want to pollute your query string, and as those parameters are only relevant in the client browser page.

@daveajones
Copy link
Contributor

Good info. Thank you!

@dascritch
Copy link
Author

dascritch commented Nov 24, 2021

The is a BIG ERROR i've just noticed : the separator between fragments is & and not #. I'm sorry for this mistake in copy-paste rush

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants