Make hosters choose between Twitter API vs Nitter #69

Open
opened 1 year ago by yarmo · 0 comments
yarmo commented 1 year ago
Owner

Proposed change would be to disable Twitter verification by default and make the hoster consider which path to Twitter verification to use.

  • Twitter API -> requires dev account
  • Nitter instance -> requires trust in 3rd party + risk of downtime
Proposed change would be to disable Twitter verification by default and make the hoster consider which path to Twitter verification to use. - Twitter API -> requires dev account - Nitter instance -> requires trust in 3rd party + risk of downtime
yarmo added the
enhancement
label 1 year ago
yarmo added this to the Feature development project 1 year ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.