Difficulties to proof a website
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Hi friends. Thanks you for such an amazing free and open piece of software.
I wonder if you could help me understand what's the matter with this proof. It seems your server can't reach my proof, which is pretty online though... :-?
https://dragonstake.io/keybase.txt
User: dragonstake
Thanks in advance.
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 reproducing the website proof for https://dragonstake.io/keybase.txt using the Keybase user dragonstake. Trace the verification request and server reachability, then confirm the proof either verifies successfully or produces a clear explanation of the failure.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100