Wow, this is awesome. Many of the songs can't even be ID'd by Shazam and are not on Apple Music. 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...
https://radiooooo.app is the beta test new version you should try :)
Radiooooo – The Music Time Machine
51–60 of 81 posts
Re: Radiooooo – The Music Time Machine
#52Re: Radiooooo – The Music Time Machine
#53Not 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.
Re: Radiooooo – The Music Time Machine
#54Re: Radiooooo – The Music Time Machine
#55Re: Radiooooo – The Music Time Machine
#56This is an incredible website thank you the creator!
Re: Radiooooo – The Music Time Machine
#57Re: Radiooooo – The Music Time Machine
#58Re: Radiooooo – The Music Time Machine
#59It is inaccurate: For Mexico 1980 it actually showed "La Union" band which is actually Spanish.
Re: Radiooooo – The Music Time Machine
#60Earlier quoted context omitted.
But his ISP might be injecting subliminal messages! (For fun see also https://en.m.wikipedia.org/wiki/Backmasking )
my ISP doesn't do this currently. reason is actually that I don't see any reason why the app should be using mixed_content to begin with. In the age of letsencrypt you can easily get certificates, so the only reasons I can think of are a) performance overhead due to TLS, b) storage of audio tracks done on 3rd party domains due to cost/limits. a) is a non-issue in 2020 b) not extending trust to 3rd party domains is li…
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 :)