From 55b655cb7ebd09fc416c777801d8ef4156c5a8fa Mon Sep 17 00:00:00 2001 From: Yarmo Mackenbach Date: Fri, 3 Jul 2020 16:40:18 +0200 Subject: [PATCH] Add TLDR to post --- content/blog/2020/07/2020-07-03--keybase-website.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/blog/2020/07/2020-07-03--keybase-website.md b/content/blog/2020/07/2020-07-03--keybase-website.md index d53fbde..dc071c5 100644 --- a/content/blog/2020/07/2020-07-03--keybase-website.md +++ b/content/blog/2020/07/2020-07-03--keybase-website.md @@ -14,6 +14,10 @@ discussion: Two days ago, I launched [Keyoxide.org](https://keyoxide.org) which provides a few similar functions as [Keybase.io](https://keybase.io) but in an Open Source package. I've been wanting to write this post for a while but felt it could be perceived as disingenuous if posted before making my own project public. Therefore, I post this now. +## TLDR + +The Keybase.io website uses non-optimized resources resulting in a slow pageload and 5+ year old versions of libraries with known and public security vulnerabilities. + ## The Keybase.io website I have opinions about the Keybase service, but this post is not about that. This is about the facts behind their website, [Keybase.io](https://keybase.io) and more specifically their [encrypt](https://keybase.io/encrypt) page, the one you use to **encrypt private and confidential messages**.