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.
Many of the songs can't even be ID'd by Shazam and are not on Apple Music.
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.
One clarification: The dates specify the date of release, right? I went to the site expecting to hear popular songs from that era/region, but I've never heard of any of the songs it plays.
I could see they are using three.js for a visual library, but I couldn't tell what they were using for audio. Maybe they are interacting with the web audio api directly, since they are only playing a single piece at a time. I didn't hear in fade in/out or more advanced functionality.
I love the creative design of this site/app! There are so many gems in here. I’m now trying your updated iOS app in TestFlight, kids are using the old version.
1. I recommend changing Fornication Island to Seduction Island and changing the picture from a behind in the water to something else. Kids love this app and it should be kid friendly.
2. The icon for the old version is a better design and more memorable. I suggest changing it back.
3. Making the map look more like a paper map would be a way cooler interface, though could be tough since you’d need one per decade. But it would REALLY make the app unique.
https://radiooooo.com/ doesn't work because it's trying to XHR the http version of the site which gets blocked. The other .app domain works fine though, like you said.
Nice. I've got serious thing for 60/70's middle eastern/north african jazz and prog, ranging geographically from Ethiopia to Turkey to Afghanistan. Back in 2004 to 2007 I used to have a late night radio show on UK local radio station that broadcast on a Friday night and mingled in many of these gems along with Caravan, Soft Machine, Pere Ubu and so much more.
Whoever Victor Kiswell is, sir, you have an amazing library of tunes and I'd love to speak to you.
Current tune:
African Jumbo by Abbass Mehrpouya (1976, Iran)...bonkers good, would love to own that.
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.
The new one added a breaking bug. With the old address I can option select the text with a mouse to copy/paste. It may not seem a big deal, but many of the strings for foreign songs are not ASCII so they are hard to type otherwise.
"It's not a bug, it's a feature" of most modern web browsers. A https page that includes content fetched using http is called a "mixed content" page. Radiooooo over https still fetches the songs via http requests, and so many browsers block these requests.
It’s for listening to clips of old music, not email or banking. It’s literally replicating data that is otherwise being publicly broadcast through the air unencrypted.
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 literally why allowing mixed_content is a terrible idea
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 :)
I agree that you have compute overhead which you need to account for.
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 :)
I get that. but how would you allow the mixed content on a per site basis? sure I could use another browser that ignores the security just for this one page. how else would you do it without editing about:config and then switching back, is there a extension or something that can do that on a per-site basis?
It's a shame this isn't working in a secure way and out of the box on modern browsers.
I have been wondering why it stopped working for me half the time about a year and a half ago, and you just now made that click in my head haha, cheers for that.
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.
