keybase / keybase/keybase-issues
Proof of ownership of a Wordpress blog
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I thought I'd see if I can use Keybase to help me prove ownership of my blog (hosted on Wordpress). So I created an ownership proof, intending to publish it as a page on my blog at https://altmode.wordpress.com/keybase.txt .
Unfortunately, Wordpress won't let me put a "." character in a page's pathname; the best it will let me do is https://altmode.wordpress.com/keybase-txt
Now it's very possible that my ownership of the site isn't direct enough, and it was the Right Thing for my proof to have failed. But claiming ownership of a blog is a potentially interesting thing to do, so you might consider adding that. It might be as simple as additionally looking for the file at /keybase or /keybase-txt
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing Keybase website-ownership proof verification flow; the issue does not name a source file or test. Compare the failing /keybase.txt URL with the WordPress-compatible /keybase-txt page and determine the expected verification behavior before adding coverage for the accepted path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wordpress
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100