Mastodon API verification isn't working. Use post verification instead?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Mastodon verification isn't working. This is likely because Mastodon has removed the entrypoint for verifying Keybase. On purpose. It would be nice if instead verification can be completed using a post (like on Twitter).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the existing Mastodon verification flow and comparing it with the post-based verification used for Twitter; done means Mastodon ownership can be verified through a post after the current API entry point is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100