Radiooooo – The Music Time Machine
61–70 of 81 posts
Re: Radiooooo – The Music Time Machine
#62Re: Radiooooo – The Music Time Machine
#63* edit: it doesn't :p
Re: Radiooooo – The Music Time Machine
#64Re: Radiooooo – The Music Time Machine
#65Earlier quoted context omitted.
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 :)
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 :)
Re: Radiooooo – The Music Time Machine
#66Re: Radiooooo – The Music Time Machine
#67Wow, 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...
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.
Re: Radiooooo – The Music Time Machine
#68Nice! I collect tropical, good to see something like this do well. Can I ask about the motivation / team behind it?
It's a French collective curating rare and exotic nostalgia tunes since 2013 ( https://www.newyorker.com/culture/culture-desk/radiooooo-the... ). It was co-created by a member of the Polo & Pan duo ( https://www.discogs.com/artist/4106352 ). 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/radio…
Re: Radiooooo – The Music Time Machine
#69Whoever 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.
Re: Radiooooo – The Music Time Machine
#70the UPDATE of radiooooo is here for testing: https://radiooooo.app :)