Slack deprecating APIs[0] and the replacements requiring to fetch the replies for each message individually, realizing that last week's dump silently missed the replies and that the slack library I'm using is no longer maintained ... minutes before sending the newsletter If only there was a forum about the future of coding where I could go and complain 😛 [0] https://api.slack.com/changelog/2020-01-deprecating-antecedents-to-the-conversations-api [1] https://github.com/os/slacker/#this-repository-is-archived-and-will-not-receive-any-updates

And that slack API changelog page doesn't render correctly on iPhone. It's almost like they don't want us to use their service for our community. * ducks *

my cynical part tells me that they are trying to make it harder to do bulk archival? still not that hard though

Does this API change leave you up a creek? Or does it just require a little bit of rewriting?

I changed it yesterday, requires some extra work and an extra request per message, which I was afraid it would quickly get rate limited but it doesn't for this week's messages at least

3D animators be like, "I paid $50,000 for the Mac Pro so that preview renders take 1s instead of 2s" Web programmers be like, "I put

sleep 1

in the loop so that I don't hit rate limits" 🙃

life: "time is money", web: "money is time"