Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing GitHub Pages vs Keybase, the Slant community recommends GitHub Pages for most people. In the question“What are the best website hosting providers?” GitHub Pages is ranked 1st while Keybase is ranked 26th. The most important reason people chose GitHub Pages is:
One of GitHub's features is a very powerful web editor which helps users edit or even create files right from the web browser, once the file is saved it's the same as a commit. Coupled with pages, this tool becomes even more powerful, giving users a free CMS that is easy to use and create.
Question Ranking
Pros
Pro The ability to create and edit files on the web UI gives GitHub pages the same power as a small CMS
One of GitHub's features is a very powerful web editor which helps users edit or even create files right from the web browser, once the file is saved it's the same as a commit. Coupled with pages, this tool becomes even more powerful, giving users a free CMS that is easy to use and create.
Pro Supports Jekyll
A simple, blog-aware static site generator, Jekyll makes it easy to create site-wide headers and footers without having to copy them across every page. It also offers some other advanced templating features.
Pro Supports custom domains
A custom domain can be added by creating a CNAME file with the necessary domain in the root of the repository and adding/changing corresponding DNS entries.
Pro Free tier
Static websites can be hosted on GitHub Pages for free as long as the repository is public. Private repositories start at $7/mo.
Pro Allows for all the git features when building your site, too
Pro E2E encrypted
Completely end-to-end encrypted.
Pro Identity verification
Users can publish proofs of identity (PGP public key, Twitter, Facebook, etc).
Pro FOSS
Free (as in beer) and Open Source Software.
Pro Encrypted file sharing
Securely share files.
Pro Public encrypted filesystem
For sharing files publicly.
Pro 250GB of free team file storage
250GB of free storage for encrypted files in a team.
Pro Public teams
Teams can be public with open access or admin-approved access. Opt-in to list public teams.
Pro Private teams
Teams can be completely private (access granted via admin-approval only, not publicly listed).
Pro Encrypted Git
Encrypted private or team Git repositories with automatic commit signatures.
Pro Blockchain technology
Based on blockchain technology.
Pro Sigchain verification
View/verify the cryptographic signature history of any user.
Pro PGP/GPG support
Encrypt/decrypt any PGP message or file with minimal effort.
Pro Public key encryption
Supports public key encryption.
Pro Private encrypted filesystem
Securely store personal files that only you can access.
Pro Shared private encrypted filesystem
Share files securely and privately with other users, a group of users, or a team.
Pro 250GB of free private file storage
250GB of free storage for privately-encrypted files.
Pro Free static site hosting
Host a public static website for free. Sites are automatically viewable via keybase.pub if an index.html or index.md exist in your public files.
Pro Emoji reactions to limit excessive posts and notifications
Pro E2E encrypted team chat
Teams are E2E encrypted, unlike Slack and other services.
Cons
Con Unable to set cache expiry, must accept GitHub defaults (which are short)
Low cache expires - GitHub sets the cache-control: max-age header to 600 seconds, or ten minutes. Normally, you would set this value to a year so that it stays cached, and then use fingerprinting on your assets. Instead of serving style.css, you would serve something like style-62c887ea7cf54e743ecf3ce6c62a4ed6.css. As it stands now, assets are rarely going to be cached on repeat visits.
This will give a low score on https://developers.google.com/speed/pagespeed/insights with a 'should fix' recommendation around 'Leverage browser caching'.
For a high traffic site this may have implications
