fix numbering

This commit is contained in:
humanacollaborator 2021-03-06 15:31:41 -05:00
parent 0b0a02875e
commit c73c897d47

View File

@ -65,8 +65,9 @@ freedoms. Yet gitlab.com's walled garden is so restricted that Tor
users are not even permitted to clone a project: 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) ![](https://infosec.exchange/system/media_attachments/files/105/764/904/002/819/754/original/38832d4b9ffc75fa.png)
consequently [FSF criteria C3][fsfCriteria] is unmet. consequently [FSF criteria C3][fsfCriteria] is unmet.
1. Gitlab.com treats Tor users trying to register with hostility. 8. Gitlab.com treats Tor users trying to register with hostility.
Access is inconvenient in some cases (e.g. GUI users), while access Access is inconvenient in some cases (e.g. GUI users), while access
is outright denied to other Tor users (e.g. terminal users with is outright denied to other Tor users (e.g. terminal users with
non-GUI browsers, browsers without javascript capability, and users non-GUI browsers, browsers without javascript capability, and users
@ -113,9 +114,9 @@ of CAPTCHAs:
well after the CAPTCHA puzzle is solved and intercept user well after the CAPTCHA puzzle is solved and intercept user
information and actions. They could even pull an eBay move and information and actions. They could even pull an eBay move and
[scan your LAN ports][ebay]. [scan your LAN ports][ebay].
1. GUI CAPTCHAs fail to meet [WCAG standards][wcag] and thus 1. GUI CAPTCHAs fail to meet [WCAG standards][wcag] and thus
discriminate against impaired people, ultimately blocking discriminate against impaired people, ultimately blocking
satisfaction of [FSF criteria C2][fsfCriteria]: satisfaction of [FSF criteria C2][fsfCriteria]:
<details> <details>
<summary>(rationale)</summary> <summary>(rationale)</summary>
<table> <table>
@ -165,7 +166,6 @@ of CAPTCHAs:
thus violating [FSF criteria C0.0][fsfCriteria]. 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 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 CAPTCHAs are often broken. This amounts to a denial of service:
[//]: # (<!--I solved the hCAPTCHA, got a green checkmark, and then it looped back to an empty checkbox and I was forced to solve the hCAPTCHA for a 2nd time. And both times I had to solve 2 windows (4 windows in total [36 images]). After solving the 2nd hCAPTCHA gitlab.com brought me to a 404 error. So after all the hard work I was still blocked.-->)
* E.g.1: the CAPTCHA server itself refuses to give the puzzle saying there is too much activity. * 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: <table> * 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: <table>
<thead> <thead>
@ -181,15 +181,17 @@ of CAPTCHAs:
</tr> </tr>
</tbody> </tbody>
</table> </table>
1. The CAPTCHAs are often unsolvable. 1. The CAPTCHAs are often unsolvable.
* E.g.1: the CAPTCHA puzzle is broken by ambiguity (is one pixel in a grid cell of a pole holding a street sign considered a street sign?) * E.g.1: the CAPTCHA puzzle is broken by ambiguity (is one pixel in a grid cell of a pole holding a street sign considered a street sign?)
* E.g.2: the puzzle is expressed in a language the viewer doesn't understand. * E.g.2: the puzzle is expressed in a language the viewer doesn't understand.
1. Network neutrality abuse: at moments when Google reCAPTCHA is 1. Network neutrality abuse: at moments when Google reCAPTCHA is
used, there is an access inequality whereby users logged into used, there is an access inequality whereby users logged into
Google accounts are given Google accounts are given
[more favorable treatment][netneutrality] by the CAPTCHA (but then [more favorable treatment][netneutrality] by the CAPTCHA (but then
they take on more privacy abuse). Tor users are given extra harsh they take on more privacy abuse). Tor users are given extra harsh
treatment. treatment.
[//]: # (I solved the hCAPTCHA, got a green checkmark, and then it looped back to an empty checkbox and I was forced to solve the hCAPTCHA for a 2nd time. And both times I had to solve 2 windows (4 windows in total [36 images]). After solving the 2nd hCAPTCHA gitlab.com brought me to a 404 error. So after all the hard work I was still blocked.)
[sexism]: https://web.archive.org/web/20200309145121/https://www.theregister.co.uk/2020/02/06/gitlab_sales_women [sexism]: https://web.archive.org/web/20200309145121/https://www.theregister.co.uk/2020/02/06/gitlab_sales_women
[sanctions]: https://en.wikipedia.org/wiki/GitLab#cite_note-30 [sanctions]: https://en.wikipedia.org/wiki/GitLab#cite_note-30