From e0018aade4049ac39c67ea06c5d73c20e1858baf Mon Sep 17 00:00:00 2001 From: humanacollaborator Date: Sat, 6 Mar 2021 15:33:49 -0500 Subject: [PATCH] fix more numbering breaks --- gitlab-dot-com.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/gitlab-dot-com.md b/gitlab-dot-com.md index 98152e2..f6edef1 100644 --- a/gitlab-dot-com.md +++ b/gitlab-dot-com.md @@ -67,6 +67,7 @@ users are not even permitted to clone a project: ![](https://infosec.exchange/system/media_attachments/files/105/764/904/002/819/754/original/38832d4b9ffc75fa.png) consequently [FSF criteria C3][fsfCriteria] is unmet. + 8. Gitlab.com treats Tor users trying to register with hostility. Access is inconvenient in some cases (e.g. GUI users), while access is outright denied to other Tor users (e.g. terminal users with @@ -162,10 +163,10 @@ of CAPTCHAs: -1. Users are forced to execute [non-free javascript][nonfreejs], +1. Users are forced to execute [non-free javascript][nonfreejs], thus violating [FSF criteria C0.0][fsfCriteria]. -1. The CAPTCHA requires a GUI, thus denying service to users of text-based clients including the `git` command. -1. The CAPTCHAs are often broken. This amounts to a denial of service: +1. The CAPTCHA requires a GUI, thus denying service to users of text-based clients including the `git` command. +1. The CAPTCHAs are often broken. This amounts to a denial of service: * E.g.1: the CAPTCHA server itself refuses to give the puzzle saying there is too much activity. * E.g.2: gitlab.com has switched back and forth between Google's reCAPTCHA and hCAPTCHA (by *Intuition Machines, Inc.*) but at the moment they've settled on hCAPTCHA. Both have broken and both default to access denial in that event: