9/17/2023 0 Comments Tumblr login with facebook![]() The wait is over! We are thrilled to unveil two new repositories on our GitHub page which can be the gateway to the Tumblr API in your Go project. You’ve been asking for an official Golang wrapper for the Tumblr API. If you’re interested in exploring the Tumblr API, but don’t have a particular project in mind yet, it’s a great way to get your feet wet. We dusted it off and decided to give it its own repository. If you don’t know, that’s basically a command-line console that you can use to make API requests and examine the responses. When we were updating the API client, we were pleasantly suprised to discover a REPL in the codebase. We’re linting in addition to running mocha tests on pull requests.Ĭheck it out on GitHub and/or npm and star it, if you feel so inclined. Linting! We’ve been using eslint internally for a while, so we decided to go for it here too.Regular callbacks are still supported too. data64 support, which is handy for those times when you have a base64-encoded image just lying around and you want to post it to Tumblr.We use this internally when we’re testing new API features during development, and it’s super convenient. For example, blogInfo and blogPosts and blogFollowers rather than blogInfo and posts and followers. Method names on the API are named more consistently.We didn’t make too much of a fuss when we released a bigger update in May, but here’s a quick run-down of the bigger updates you may have missed if you haven’t looked at the JS client in a while: We just published v1.1.0 of the tumblr.js API client. Happy hacking! tumblr api tumblr engineering oauth2 We might harden it with PKCE someday, though. Although we do support client-side OAuth 2 flow, we can’t recommend using it unless absolutely required.Follow this blog to learn firsthand when this happens. We’ll be adding support for OAuth 2 to our API clients in the coming months.There’s only one catch: this exchange will invalidate the original access token, so you should be using only the OAuth 2 Bearer authentication for any subsequent requests. Instead, you can keep the old sign-up / log-in flow working, and exchange OAuth 1 access token to OAuth 2 tokens on the fly. What’s more, if you wish to adopt OAuth 2 in your app, given its superior simplicity, you don’t have to migrate entirely to OAuth 2 at once. But be sure to keep an eye on this blog just in case anything new pops up that would prevent us from serving OAuth 1 requests. If you’re familiar with OAuth 2, register an application and check out our API documentation (specifically the section on OAuth 2) to get up and running. To exchange authorization codes and refresh tokens, you’ll need to use /v2/oauth2/token.For authorization requests, you should use /oauth2/authorize.OAuth 2 flow requires you to know two key URIs: Starting today, you have another option: we’re officially opening up OAuth 2 support for the Tumblr API! Get started Yet here we are, still asking people to use outdated protocols for their new fancy Tumblr apps. Today, it wouldn’t make much sense to adopt OAuth 1 as inconvenient as it is. ![]() Time went by, and here we are in 2021, with hardly any popular website not shielded with HTTPS ( including your own blog!). ![]() One solution was OAuth 1, conceived by the IETF, later adopted by Tumblr in 2011. It is hard to believe that HTTPS was essentially opt-in, if available at all! Back then, people also had to get creative when inventing means to delegate access to someone else. Ten years ago HTTPS wasn’t as nearly as widespread as today. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |