Live data from Hacker News

Radiooooo – The Music Time Machine

radiooooo.com

51–60 of 81 posts

Re: Radiooooo – The Music Time Machine

#51
post #11

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 :)

Thank you! radiooooo.com is blocked here at work but radiooooo.app isn't :)

Re: Radiooooo – The Music Time Machine

#52
It's interesting to see that the map reshapes as you move through the decades. Germany splits into two and then goes back to one, Africa and the Indian subcontinent get progressively decolonized, etc. It's not perfect, particularly in east Asia (Taiwan is always independent and Korea is always two countries, and neither are ever colonized by Japan), but what's there is fun to see.

Re: Radiooooo – The Music Time Machine

#59
post #58

It is inaccurate: For Mexico 1980 it actually showed "La Union" band which is actually Spanish.

It may not be if it's songs that were popular in that area during that time rather than songs FROM that place. I'm not sure if they differentiate which it is, I didn't see any at a glance.

Re: Radiooooo – The Music Time Machine

#60

Earlier 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…

TLS is anything but a non-issue. TLS accounts for roughly 40% of the CPU and 45% of the memory bandwidth on our CDN nodes.

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 :)

Post reply on HN