Fantastic. Here's another niftly radio app: http://radio.garden/
Radiooooo – The Music Time Machine
21–30 of 81 posts
Re: Radiooooo – The Music Time Machine
#22UPDATE of the new radiooo for testing here: https://radiooooo.app :))
Maybe the link of this post itself should be updated
Re: Radiooooo – The Music Time Machine
#23Nice! I collect tropical, good to see something like this do well. Can I ask about the motivation / team behind it?
Re: Radiooooo – The Music Time Machine
#24how nice is it, it is just the Big data and AI should doing!
Re: Radiooooo – The Music Time Machine
#25Wow, 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 found some great tracks from around Africa but can't find them on Spotify.
Re: Radiooooo – The Music Time Machine
#26Earlier quoted context omitted.
that's a no thanks for me. allowing mixed_content isn't something I can live with.
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.
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.
Re: Radiooooo – The Music Time Machine
#27Earlier quoted context omitted.
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.
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 literally why allowing mixed_content is a terrible idea
Re: Radiooooo – The Music Time Machine
#28How's the song upload feature in terms of copyright?
Re: Radiooooo – The Music Time Machine
#29Very cool. Listened to some French and African 70s stuff.. Thanks for posting this. 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".
use this new adress: https://radiooooo.app it fix a lot of bugs !
thanks, this actually works and solves the mixed content issues. fantastic app
Re: Radiooooo – The Music Time Machine
#30Earlier quoted context omitted.
"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.
use this new adress: https://radiooooo.app it fix a lot of bugs !
works like a charm, thanks
this site is pure awesome