I'm putting together some high level information on how the weather.com/retro site was engineered but I'm also happy to field any questions here and naturally receive your feedback. Thanks for the kind words on the other thread.
When Netlify and I agreed to work together on their 10 million developers activation, Netlify Capsules, I knew I wanted to take the opportunity to learn some new technology and challenge myself. I consider every client project an educational opportunity and try to push myself out of my comfort zone in order to always come away with new learnings. How could I incorporate AI in the development of this project? Were there new features of the Netlify platform worth integrating? What would it be like to collaborate with nearly every department of Netlify? I was excited to answer these questions.
Earlier this month, OpenAI announced that Spotify could now join your ChatGPT conversations. Having just written about the state of the Spotify Web API, I was curious to see what this integration was capable of. In this latest newsletter, I decided to examine the authentication permissions to see what account access is being agreed to and what capabilities are actually being utilized, and in what form. Turns out, you're agreeing to a little more access than the current functionality you're receiving. This raises questions about future plans, privacy implications, and what your data might be used for down the line.
A lot has changed on the Spotify Web API in the past year: deprecated features, increased security, and steep new criteria for extended access, which alienates indie apps. Rather than complain about it, I've put together a report to understand these new restrictions and find practical alternatives. If you have developed with the Web API in the past or are considering building with it in the future, this is a must read.