Git Product home page Git Product logo

Comments (8)

michelson avatar michelson commented on May 28, 2024

same error here, did you find a solution?

from ueberauth_twitter.

benvp avatar benvp commented on May 28, 2024

This is because you are probably using the clientId and clientSecret which is provided by twitter. This lib expects the consumer_key and consumer_secret.

Also make sure that you have "Elevated Access" with your Twitter API (by requesting it), so that you can Sign In via OAuth1.

from ueberauth_twitter.

michelson avatar michelson commented on May 28, 2024

I've created a Twitter implementation for the v2.0, it uses the oauth2 package:
https://github.com/rauversion/rauversion-phx/tree/main/lib/rauversion/ueberauth/twitter
It lives on a repo right now but I guess it could be extracted to a new package. What do you think?

from ueberauth_twitter.

yordis avatar yordis commented on May 28, 2024

Maybe create a PR @michelson I am not too familiar with the twitter details so help is much appreciate here

from ueberauth_twitter.

michelson avatar michelson commented on May 28, 2024

how should this PR be designed in order to support both versions? maybe a TwitterV2 module? twitter_v2/folder?
maybe it would make more sense to create a new package?
let me know.

from ueberauth_twitter.

yordis avatar yordis commented on May 28, 2024

ideally avoid breaking changes, is this because of two different APIs? In that case, yeah, probably create a different module until we can deprecate the old one.

Any idea about the deprecation from Twitter? What is the EOL of it?

from ueberauth_twitter.

michelson avatar michelson commented on May 28, 2024

ideally avoid breaking changes. Is this because of two different APIs? In that case, yeah, probably create a separate module until we can deprecate the old one.

Any idea about the deprecation from Twitter? What is the EOL of it?

The V1 will not be deprecated AFAIK, so that a different module will be needed.

from ueberauth_twitter.

benvp avatar benvp commented on May 28, 2024

ideally avoid breaking changes. Is this because of two different APIs? In that case, yeah, probably create a separate module until we can deprecate the old one.

Any idea about the deprecation from Twitter? What is the EOL of it?

The V1 will not be deprecated AFAIK, so that a different module will be needed.

Exactly. Quite a few endpoints are still v1 only (e.g update_profile) so a v2 package is preferable I think.

from ueberauth_twitter.

Related Issues (13)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.