Hacker News new | past | comments | ask | show | jobs | submit login

If you're in the UK don't bother downloading for the full experience, it still won't let you listen to anything outside of the UK.



Music rights are a bit of a mess across the Atlantic. PRS/PPL licences don't reciprocate with the American equivalents and vice versa. Either it's two sets of licences (and possibly legal entities) or you end up geo blocking. Though on the up side you can stream to parts of Europe and even Australia from the UK IIRC.

Licencing bodies are also fairly actively monitoring these things. I've had them try to chase me for royalties for services that have been shut down because they're still listed in public directories.


Came here to say that! It's a nice app and very innovative, but if I have fire up a f*** VPN every time I want to listen to stations outside the UK, forget it!

I don't think the developers care either: I've emailed numerous times without an answer, and even less-than-favourable reviews on the App Store failed to elicit a response. At least tell us the reason for the UK- hatred if you're not going to fix it?!


It’s a copyright issue.

https://en.m.wikipedia.org/wiki/Radio_Garden

“unfortunately the restriction must be extended for an indefinite period due to copyright and neighbouring rights related matters that require clarification. ”


(Edited from original comment): Found the actual cause of the problem: https://mediawrites.law/wp-content/uploads/2019/11/judgment....

Just like TuneIn, they are behaving like a broadcaster and aren't paying license fees, so I guess they are afraid of similar legal action


Not sure if it’s still true but you can disable the check very easily using devtools. No need for a VPN.


Do you happen to know, why are they not using TLS?


“Our original configuration was fully HTTPS-enabled; however, we had to adjust this when browser manufacturers started blocking HTTPS websites from loading HTTP streams.

Approximately 20% of the stations featured on Radio Garden are accessible via HTTP streams, which would become inaccessible if we switched entirely to HTTPS. Given the recent changes in Chrome's behavior towards forcing an HTTPS connection, we are considering moving back to an all-HTTPS setup in the near future.”

https://www.reddit.com/r/RadioGarden/s/0FByul10C0


Thanks! I wish they had a https site that had some mechanism (even manual instruction) to go around that issue.


Try Tor browser




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: