Adademic website verification fails.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Hello everyone, I'm https://keybase.io/fabriziogenovese on keybase. I'd like to verify my academic webpage as mine. Precisely, my university gives me a personal webspace, and verifying it would be a good way to actually prove that one's keybase account is owned by a person working in that university.
The problem is that said university webspace is in the form universitydomain/myusername/. So I am allowed to put the keybase file in universitydomain/myusername/keybasefile but not directly in universitydomain/keybasefile as the website says. Is there a way to implement this feature/solve this issue?
Cheers,
Fab
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
Start by locating the Keybase client’s academic website verification flow and reviewing how it handles keybase files at a domain root. Define how a user-directory path such as universitydomain/myusername/ should be represented and verified, then add coverage for that case; done means the described university webspace can be verified.
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
- Needs clarification
- Newbie friendliness
- 25/100