I wish the initial modal dialog was easier to close and that the current track ID was reflected in the URL bar, e.g. http://radiooooo.com/?track/df3115c7-4eea-4d26-aba9-3c190542...
I have this same experience almost every time my wife comes back from a record store, the library gift shop, or a thrift store.
Digital services like to talk about the tens of millions of songs and videos they have. They don't like to talk about the hundreds of millions of songs and videos they don't have. And probably never will.
Similar idea, no map, but supports community editing & many sort patterns & ratings.
There very few songs from my country though. Going to upload some.
My only issue is the Taxi dialog didn't seem to position correctly in Chrome on my Android, and I couldn't accept or dismiss it.
How did the author manage to keep playing music after forwarding me to the iTunes store? iframe or something?
Whoever Victor Kiswell is, sir, you have an amazing library of tunes and I'd love to speak to you.
African Jumbo by Abbass Mehrpouya (1976, Iran)...bonkers good, would love to own that.
* edit: it doesn't :p
Not sure if bug or missing feature, but the decade tabs at the bottom of the screen are unlabeled so I have to click around a bit to find the decade I want.
Firefox 74.0b7 on macOS 10.15.3.
have a good trip :
An up to date revision of the site is available at: https://radiooooo.app
Here's a little helper script to listen Radiooooo from the command line: https://github.com/vikbez/radiooooo-cli
One minor glitch -- user registration form wouldn't work for me.
It told me there was an error, therefore "my email must already be registered".
this site is pure awesome
(For fun see also https://en.m.wikipedia.org/wiki/Backmasking)
a) is a non-issue in 2020
b) not extending trust to 3rd party domains is literally why allowing mixed_content is a terrible idea
I work for Netflix on our CDN. I wrote much of the FreeBSD kernel TLS layer, and am working with several vendors on hardware TLS offload to eliminate this overhead. Hopefully your statement will be correct soon :)
At least for SaaS companies it's not really a technical hurdle that blocks anyone from running their service, except maybe for those who are already very large (Netflix obvioulsy) and have scaled and optimized so well that it makes sense for further reducing this additional cost. You're in a unique position I think and you are lucky to work on a cool project like this.
But I have not seen any places where this was at all an urgent on a clients or employers agenda. It is a budgeting issue (if you're buying) or pricing issue (if you're selling), but it's not an technical problem that needs to be solved in any place other than hyper-scaling companies/stacks.
Terminating TLS and (load-balancing it) is not really what prevents a cash strapped start-up from scaling, nor is it super high priority in large companies who are able to throw a little extra money at this problem. Those companies who still have skilled innovators around solves the problem like you do at Netflix, in older industries (banks come to mind) they just by OTS or have a consulting company implement some "bespoke solution".
It's a "problem" most SaaS businesses can carry with them for a long time, until they have room to address it.
obviously this sounds like a cool project to dive into but quite rare too! enjoy it, I know I would :)
It's a shame this isn't working in a secure way and out of the box on modern browsers.