e are thinking about a hand crafted solution for GPS backgrounding.
We're all well aware of the behaviors which make browsers adopt such
defensive measures. Are we looking at enough use-cases to think about some
sort of general authorization for background resource consumption, rather than
continuing the point solution approach?
$0.02,
Andy Valencia
ng page, but UX pushes strongly
where the 99.999% case is not the one which should require the extra
click. I'll certainly have the canonical link specified, and hope
for the best. Perhaps even, as you say, submit a ticket to a
browser or two.
Thanks again,
Andy Valencia
s served under HTTP, I guess a lame ISP could insert themselves.
Possibly recommend ignoring the value from non-HTTPS pages? That
certainly aligns with Mozilla's stated intentions for future
features.
Thanks,
Andy Valencia
I've become aware of quite a bit more metadata support in the world
of web browsers; please consider my old proposal withdrawn.
=== Reporting
> Only "artist" and "title" are required for royalties reporting for
> internet radio.
I'm sorry for a bit of topic drift on this list, and I'm sure requir
Thank you for the helpful comments.
wrote:
> http://www.smackfu.com/stuff/programming/shoutcast.html isn't detailed
> enough to get interoperable implementations, in particular the metadata
> keys would have to be defined.
Note that mp3, flag, ogg, and wav all have entirely open ended
container
What follows is a first pass at addressing a missing ability
when dealing with Internet streams, usually radio ones.
Comments and suggestions are quite welcome; as my first
attempt--ever--at submitting to this group, apologies if
I've made any mistakes in how I've proceeded.
Thanks,
And