leemartin

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.

you can change the unit in settings, just click the gear on countdown page

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.

How would you approach adding physics to the shreds? Someone asked me for cross-cutting.

Oh shit, I didn't even know about shorthand notation. That saves me a line break in my Medium writeup. THANK YOU. Thanks for the in-depth critique! I'd be worried if you saw the code I wrote for a living.

Yeh, for sure. This was a quick little hack and I suspect my original thought was that I would animate each piece, hence the individual elements.

I should also note that the location consent was (in most cases) initiated by the HTML5 Geolocation prompt. Now a lot of companies use this technology to reposition something like a Google Map on their website. We did the same thing but positioned a static map and made it part of a video composition.

Yeh, I hear you. Users consented to sharing their location as one of the variables required to enter the contest. It was a ticket giveaway so knowing their location allowed us to figure out which show they might go to. Again, the videos themselves were emailed directly to users and while sharing them publicly was encouraged, it was not something we did ourselves.

It's like... you gave me an email address so naturally I'm going to email you. You gave me a location so (unnaturally) I'm going to make a video for you.

Out of curiosity (since we are on Hacker News) - what would have been your next logical step on trying to connect those videos to their actual fans?

Agreed. Thanks for the nudge

Haha. That's like saying Google Maps can leak the locations of people. There's nothing to tie the users to the videos but I've gone ahead and turned off that S3 because you gave me a small heart attack.

1) Got lucky: http://leemart.in/origin 2) Worked really hard and stayed as curious as possible 3) Add 15 years

Competition is still ongoing. It's tied into a larger campaign.

The videos were sent directly to users as part of an email confirmation of their contest entry. We did not use the videos for marketing. It was up to the user to actually share the video.

Cheers man, check this out:

https://twitter.com/leemartin/status/907308086184087552

YES. Wow. This is what I referenced when pitching the project.

Check this out:

https://twitter.com/Mapbox/status/908100445754859521

You nailed it Paul. That campaign really inspired me early on as a developer (and I think a lot of devs in music would say the same) and I've used similar tricks of geo-nostalgia in other projects.

If we're counting luck, this campaign was a god damn fluke.

Well it's probably not going to be as bad as my S3 bill but I'm not looking forward to it.

In addition, we contacted a few online store customers since we knew their mailing address. I believe the Manson camp also mailed some of those folks post cards with a similar theme.

Cheers man. I would usually do something like this server side but didn't have much time to test the pros and cons of rendering via something like FFMPEG vs. After Effects. I was pretty excited to try out the DataClay plugin as well.

We really wanted to mail the attachment because most folks would receive this via mobile and you can't download a link (easily, to my knowledge) to your mobile file system or photo library. By putting the attachment in their inbox, it's a one-click process which gets them one step closer to sharing.

Used on http://omgig.com

Here's a link to all the tech used: http://wiki.musichackday.org/index.php?title=OMGIG Including a new Javascript library for pulling Webm videos from YouTube: https://github.com/endlesshack/youtube-video