For the 100th episode, Doug and Kirk discuss how they listen to music today, and how their music listening has changed in the two years they’ve been producing this podcast.
Listen to The Next Track: Episode #100 – How We Listen to Music Today.
Find out more, and subscribe to the podcast, at The Next Track website. You can follow The Next Track on Twitter at @NextTrackCast, to keep up to date with new episodes, and new articles from the website.
Using Safari I am refused access to your Next Track site. I think you have to update “something”.
Using Safari I am refused access to your Next Track site. I think you have to update “something”.
I play music CDs on 5-CD changers. I have 3 of them, one of each in home office (main system), basement and bedroom. I listen to albums from start to finish, and a changer lets me add/remove discs without stopping the music steam. (Pardon the pun.) I don’t listen to via streaming services, never tried; they don’t interest me for my listening habit and pattern and the systems that I have. I do rip music CDs to Apple Lossless, thinking someday I may change my listening habit.
I play music CDs on 5-CD changers. I have 3 of them, one of each in home office (main system), basement and bedroom. I listen to albums from start to finish, and a changer lets me add/remove discs without stopping the music steam. (Pardon the pun.) I don’t listen to via streaming services, never tried; they don’t interest me for my listening habit and pattern and the systems that I have. I do rip music CDs to Apple Lossless, thinking someday I may change my listening habit.
I get this message when I click on the link:- This Connection is Not Private This website may be impersonating “www.thenexttrack.com” to steal your personal or financial information. You should go back to the previous page.
I get this message when I click on the link:- This Connection is Not Private This website may be impersonating “www.thenexttrack.com” to steal your personal or financial information. You should go back to the previous page.
There was a problem when we moved the site from its previous host to a new host. The SSL certificate that we had cannot be used with the new host, who has their own certificates for all the sites they host.
As such, I think that Safari caches the certificate information, and reacts because it finds that the site is using a new certificate. Go through the Safari dialogue and authorize it to view the site, and all will be fine.
There was a problem when we moved the site from its previous host to a new host. The SSL certificate that we had cannot be used with the new host, who has their own certificates for all the sites they host.
As such, I think that Safari caches the certificate information, and reacts because it finds that the site is using a new certificate. Go through the Safari dialogue and authorize it to view the site, and all will be fine.