You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
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 :
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 befastfollow-podcast=(guid),(hostname)
The text was updated successfully, but these errors were encountered: