Make hosters choose between Twitter API vs Nitter
Openopened 1 year ago by yarmo · 0 comments
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
enhancementlabel 1 year ago
yarmo added this to the Feature development project 1 year ago
Reference in new issue
There is no content yet.
Delete Branch '%!s(MISSING)'
Deleting a branch is permanent. It CANNOT be undone. Continue?