impossible to verify a wordpress.com website (gratis hosting)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Currently, the requirement to verify a Wordpress.com website is to add a keybase.txt file at xxx.wordpress.com/.well-known/keybase.txt or xxx.wordpress.com/keybase.txt.
When using the gratis hosting formula, it is not possible to do so, as there is no access to the filesystem, the file uploader does not allow for .txt format, and creating a "keybase.txt" page through the web interface corrects the url to xxx.wordpress.com/keybase-txt.
Would it be possible to additionally check for xxx.wordpress.com/keybase-txt, or even a simple xxx.wordpress.com/keybase for users maintaining a gratis Wordpress.com website?
One issue could be that HTML tags are added by default to the text when a page is created via the web interface's visual editor.
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 or tests are named. Start by locating the existing website-verification handling and its checks for keybase.txt, then inspect how fetched WordPress.com page content is interpreted. Done means gratis WordPress.com sites can be verified through the proposed keybase-txt or keybase URL while accounting for HTML added by the visual editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, wordpress
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100