The nice thing about having a hobby #rstats you've been working on off and on for literally ten years now is that you get to be in a forever-refactor and it's never done.

Yanked out #httr and replaced it with #httr2 successfully(ish) though, so that's nice.

Finally managed to fully migrate an API-wrapping #rstats to #httr2 and I like it a lot, particularly for the easy caching.
Only issue is that I'm using a semi-homebrewed device flow which I don't know how to make work on GitHub actions, where providing $PKG_KEY isn't enough to authenticate

Any #RStats #httr2 users out there that might be able to help? I’ve a package that downloads files but seems to fail for some people and not others, https://github.com/adamhsparks/read.abares. It works for me on every computer I’ve tried physically, Mac or Windows, but not GitHub Actions. It also fails for @obrl_soil. Note that @obrl_soil is able to access and download the files using a browser but not the R package. Here’s a package check log https://github.com/ropensci/software-review/issues/667#issuecomment-2703398914.

Melissa Van Bussel: “ My latest video is all about how to use R to interact with APIs, using the httr2 package. No background knowledge about APIs is necessary Check it out here: https://youtu.be/8tilyqp4bZY?si=9DqhrOfSCbrqUfIt “
Uses #OpenAI and #GitLab APIs

@rstats

TIL the @trakt API does not fully conform with RFC 8628, which expects the device token request to have the field "device_code", but the trakt.tv API expects a field named "code".
This is as far as I can tell the one and only reason I can't take the off-the-shelf #httr2 OAuth implementation and probably will have to kajigger the token stuff manually, which I hate
(Or I just keep my old #httr version which is "good enough" I guess)
#RStats