The Brave web browser is an interesting take on providing greater privacy while still rewarding content creators through ads, views, and tips. To explore it a bit more, I thought I would try to verify this GitHub Pages blog.

The verification process involves uploading a publicly visible text file to your site, which in this case is the GitHub repository. The issue I ran into was that GitHub builds this blog using the static site generator Jekyll, yet the Brave GitHub Website verification instructions ask you to turn off Jekyll:

It looks like you are using GitHub. As a GitHub user, you’ll need to add an empty file named ‘.nojekyll’ to the root of your repo first.

Instead, based on this GitHub issue comment, I included the .well-known directory containing the Brave verification text file brave-rewards-verification.txt in the Jekyll build by adding the following line to _config.yml:

include: [".well-known"]

The verification was then successful as the verification file is visible in its expected location. The full commit showing these changes can be seen here.

Share on:

This work by Derek Croote is licensed under CC BY-NC 4.0