Read on Twitter
I'm explaining how HTTP works to App Review.
How's your day going?
How's your day going?
We're now at the point where I'm giving HEAD to Legal. 34,510 times, in fact.
Not kidding.
Not kidding.
So here's what happened yesterday: our @TriodeApp update got flagged in review for Guideline 5.2.3: "your app provides potentially unauthorized access to third-party audio".
Which is totally reasonable if you don't know how things work. Triode _is_ playing copyrighted audio.
Which is totally reasonable if you don't know how things work. Triode _is_ playing copyrighted audio.
I explained how HTTP HLS works - it's just like accessing a web page except you get an audio stream, not text and images.
I also explained that we're using a public domain database for URLs ( https://www.radio-browser.info ). It's like the iTunes podcast directory: lots of app use it.
I also explained that we're using a public domain database for URLs ( https://www.radio-browser.info ). It's like the iTunes podcast directory: lots of app use it.
But what Apple _really_ needs is documentation for Legal.
So that's why I did 35,410 HEAD requests - to generate a 3,100 page report proving that I had access to each URL in the database.
Information that can be filed away in case of a legal challenge.
So that's why I did 35,410 HEAD requests - to generate a 3,100 page report proving that I had access to each URL in the database.
Information that can be filed away in case of a legal challenge.
I've heard of other apps (like @stroughtonsmith's Broadcasts app) getting this legal rejection.
I can also see this logic being applied to podcast apps, RSS readers, or anything else that accesses a collection of content URLs.
Keep this thread in mind if it happens to you.
I can also see this logic being applied to podcast apps, RSS readers, or anything else that accesses a collection of content URLs.
Keep this thread in mind if it happens to you.
