colours 0.8.12 → 0.9.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7890a598377b5da4d185aad49c279af02cd4165ab3ef8ee349c93389edda6cce
-  data.tar.gz: e4020cb05be8585b9960987da9a0fea3099e8cfd16129e18074c837d624984ad
+  metadata.gz: 35cc5fe7d897ad1c870955b796a339e75827c322ecee636ed2f65a4b4c8c3711
+  data.tar.gz: 96552f6ac64de2c238009d96097381da0b37604b0a8cc69272b6fc283edd9548
 SHA512:
-  metadata.gz: 5c1e968dd5790cbbe555dbb1f8b5d20002a00e155ecb595813d5079993e42717b055a8dc1f86ddea6bd54539215f49e56dbca49d9c98b0d6e3d44329c5721089
-  data.tar.gz: 4034814234079288ca4ef93cbb556122a604d19b4bc2003b0f6fa9e111c7482412d3bef5434aded717589933769cc5fc8f071ad0e4a929eb5c10148f4c8c35c0
+  metadata.gz: 6a8a4ee2eb2464e3a5da09656c73ba2194db8ddcd7f2d92681edd5426113446a1f23d73d6356dcf89ebfd58d671b9891c7e4073585995e9c7fa87b92890d9495
+  data.tar.gz: 69103940a21be3b6ff40f46e1ad07f0a110ab7c512b0552a734c036b2b3ffedde4624696aeb032ca615ff2442d8cf2088151ffd75779b80e54e399ecb6771e12

data/README.md

@@ -2,7 +2,7 @@
 [![forthebadge](https://forthebadge.com/images/badges/made-with-ruby.svg)](https://www.ruby-lang.org/en/)
 [![Gem Version](https://badge.fury.io/rb/colours.svg)](https://badge.fury.io/rb/colours)
 
-This gem was <b>last updated</b> on the <span style="color: darkblue; font-weight: bold">29.10.2023</span> (dd.mm.yyyy notation), at <span style="color: steelblue; font-weight: bold">21:19:53</span> o'clock.
+This gem was <b>last updated</b> on the <span style="color: darkblue; font-weight: bold">04.12.2023</span> (dd.mm.yyyy notation), at <span style="color: steelblue; font-weight: bold">03:39:43</span> o'clock.
 
 # The Colours project
 
@@ -10,52 +10,69 @@ Making colours great again! \o/
 
 ## Goals, Scope and the History of the colours project
 
-The Colours project originated from a requirement to have to support **colours**
-on the commandline. Colours can be immensely helpful, so it makes sense
-to make use of them on the commandline. The modern www also makes use of
-colours - just look at any random webpage; you may find lots of
-different colours in use there.
+The Colours project originated from a distinct requirement to have to support
+<b>colours</b> on the commandline, such as for commandline-oriented
+scripts.
 
-If you do happen to take a look on the projects offered on rubygems.org then
-you may be able to find **lots** of different colour-related projects, written
+Colours can be immensely helpful for use in computer programs, so it appears
+to be a logical conclusion to make use of them on the commandline as well.
+The modern www also makes use of colours - just look at any random webpage;
+you may find lots of different colours in use there, for various reasons
+and purposes.
+
+If you do happen to take a look on different projects offered on <b>rubygems.org</b>
+then you may be able to find **lots** of different colour-related projects, written
 in ruby. The primary reason as to why I created a new colour-centric project
-was because I needed certain functionality that was not provided by any of
-the other projects; at the least not in a way as I thought it should be
-available (and used in downstream projects). For example, some terminals
-support **RGB values** and other terminals do not. I did not want to have
-to spend time thinking about this much at all, so I wanted to have a
-colours-related project that could abstract this away for me.
+was because I needed certain functionality made available that was not provided by
+any of the other projects; at the least not in a way as I thought it should be
+available (and used in downstream projects).
+
+For example, some terminals support **RGB values** and other terminals do not.
+I did not want to have to spend time thinking about this much at all, so I wanted
+to have a <b>colours-related project</b> that could abstract this away for me.
+That way I can focus on other problems, and delegate the colour-specific issues
+to this gem here.
+
+Let's next show how this may then look on the commandline:
 
-![alt text][screenshot1]
-[screenshot1]: https://i.imgur.com/F6kac8W.png
+<img src="https://i.imgur.com/F6kac8W.png" style="margin: 1em">
 
-The **main goal** of the **colours project** is to collect colour-related
+The <b>main goal</b> of the **colours project** is to collect colour-related
 code and make this code available to other projects, so that these projects
-can benefit from colour support.
+can benefit from colour support via one project: the <b>colours gem</b>.
+
+The primary goal herein lies on **commandline applications**, but there
+are some <b>HTML components</b> as part of this project that could be used
+as well, such as for when you wish to make use of **HTML colours** (slateblue,
+royalblue, teal, tomato, steelblue and names such as these) in a webpage.
+
+Elements such as:
 
-The primary goal herein is for **commandline applications**, but there
-are some HTML components as part of this project that could be used,
-such as for when you wish to make use of **HTML colours** (slateblue,
-royalblue, teal, tomato, steelblue and names such as these). The
-partial screenshot above indicates this, on a black **KDE konsole**
-background. (I tend to prefer dark backgrounds for my terminals.)
+    <span class="dodgerblue">This is in dodgerblue.</span>
 
-Note that many **terminals** support the **display of HTML colours**, via
+The partial screenshot that was shown above indicates this situation, on a
+black <b>KDE konsole</b> background. (I tend to prefer dark backgrounds
+for my terminals.)
+
+Note that many **terminals** support the <b>display of HTML colours</b>, via
 their **corresponding RGB values**. Since I wanted to use good terminals,
 such as the **KDE konsole**, the colours project also had to support
-these names (such as **slateblue** or **royalblue**) directly. This is
-why method calls such as **Colours.royalblue()** will also work - see
-for a later subsection how to customize (and control) this.
-
-The **Colours gem** has other, older projects, such as AnsiColours,
-ColourE, AliasE and several other smaller sub-projects that I have
-used over the years, integrated. It is thus a **bundled project**. This
-is specifically mentioned in the event that you may wish to look at
-the code, and wonder a little why it is structured the way it is.
+these names directly, as method calls as well - names such as <b>slateblue</b>
+or <b>royalblue</b>). This is the reason why method calls such as 
+<b>Colours.royalblue()</b> or <b>Colours.darkgreen</b> will also work - see
+for a later subsection how to customize (and control) this behaviour.
+
+Historically the **Colours gem** was inspired by other, older projects, such
+as <b>AnsiColours</b>, ColourE, AliasE and several other smaller sub-projects
+that I have used over the years. These projects were eventually integrated
+into one namespace - <b>module Colours</b>. This gem is thus a <b>bundled
+project</b>. This is specifically mentioned in the event that you may wish
+to peek at the code, and wonder a little why it is structured the way it
+is.
 
 ## Requiring the colours project
 
-To require the colours project, do:
+To require the colours project, simply do:
 
     require 'colours'
 
@@ -66,13 +83,144 @@ You can also **autoinclude** this module into your project, at
 
 This will make the **Colours namespace** and the
 **Colours::HtmlColours namespace** available, via 
-**include Colours** ultimately.
+<b>include Colours</b> ultimately.
 
 If you need more control over the include-action then you should
 just use the first variant, require 'colours', and then do the
 include action specifically onto whatever class/module you need
 that functionality.
 
+The project was partially rewritten in November 2023. If you
+want to autoinclude the project still then I recommend you
+use this:
+
+    require 'colours/html_colours'
+
+After that methods such as <b>Colours.steelblue()</b> will
+work.
+
+## ASCII Escape Characters
+
+The code in the colours gem makes use of elements such as \033 or
+\x1b. These are basically the same ASCII escape characters, as the
+following table shows:
+
+|-------------|------------|
+| octal       | \033       |
+|-------------|------------|
+| hexadecimal | \x1b       |
+|-------------|------------|
+| Unicode     | \u1b, \U1b |
+|-------------|------------|
+| literal     | \e, \E     |
+|-------------|------------|
+
+The last variant can often be found in <b>Bash scripts</b>.
+
+The semicolon <b>;</b> serves as the delimiter if multiple instructions
+are given.
+
+The 8 actual colours defined by the ANSI standard are as follows:
+
+    0  black
+    1  red
+    2  green
+    3  yellow
+    4  blue
+    5  magenta
+    6  cyan
+    7  white
+
+## Linux terminals and colour support
+
+The general syntax rules for colours is in the form of <b>fg_bg</b> values,
+where a value of <b>38</b> stands for the foreground, and <b>48</b> stands
+for the background.
+
+For instance, the ANSI colour for red is 196 and the ANSI colour for
+black is 0.
+
+To use the colour red, you could issue this command in Bash:
+
+    printf "\e[38;5;196m Hello world in red\n"
+
+To use the colour black as background, you could issue this command:
+
+    printf "\e[48;5;0m Hello world in black\n"
+
+Do note that the same can be accomplished via RGB values rather than
+ANSI color codes, as long as the terminal supports this (KDE Konsole
+does).
+
+Depending on whether you want to apply the colour to the foreground
+or to the background, use an **fg_bg** value of <b>38</b> or <b>48</b>
+(respectively).
+
+Examples for this:
+
+    # printf "\e[<fg_bg>;2;<R>;<G>;<B>m" # General syntax example.
+    printf "\e[38;2;255;0;0m Foreground color: red\n"
+    printf "\e[48;2;0;0;0m Background color: black\n"
+    printf "\033[91m\033[107mThis is red text on a white background\033[0m" # As this example shows, \e is the same as \033.
+
+This may be the better variant altogether, as it is quite easy to convert
+into (and from) **RGB values**, but your mileage may vary.
+
+Of course you can use this in plain ruby just as well - let's show this
+via puts:
+
+    puts "\e[38;2;#{222};#{131};#{141}m Hello world!"
+    puts "\e[38;2;#{122};#{56};#{141}m Hello world!"
+    puts "\e[38;2;122;156;141m Hello world!"
+    puts "\x1b[3mHello world!\x1b[0m"
+    puts "\e[38;3mHello world!\x1b[0m"
+
+In bash the ESC code can be either of the following:
+
+    \e
+    \033 (octal)
+    \x1B (hexadecimal)
+
+The "\e[0m" sequence removes all attributes, including formatting and colors.
+It may be useful to add it to the end of each colour text - and this is
+what the **Colours** project is essentially doing.
+
+To see which colours are supported/supportable, for each terminal,
+have a look at the following **link**:
+
+https://misc.flogisoft.com/bash/tip_colors_and_formatting#terminals_compatibility
+
+To set both the foreground and background colours at once, you can use:
+
+    printf "\e[S;FG;BGm"
+    echo -e "\e[S;FG;BGm"
+
+For example, bold white foreground on a red background:
+
+    printf "\e[1;97;41mHello world!"
+    printf "\e[1;97;41mHello world!\n"
+
+Thus, if you would like to use red colour on black background,
+you could do this:
+
+    printf '\e[38;5;196m;\e[48;5;0m Hello world!\n'
+
+Specifically, the background colours are:
+
+    40  black
+    41  red
+    42  green
+    43  yellow
+    44  blue
+    45  magenta
+    46  cyan
+    47  white
+
+The following command will use red background:
+
+    echo -e '\e[0;41m'
+    echo -e '\e[0;41m hello world\n\n ok\e[0;m'
+
 ## Introduction and Overview
 
 The toplevel module name is **Colours** and you can include
@@ -165,93 +313,17 @@ my opinion.
 In general, the html component can be used to convert the trivial
 <b>html colours</b> into <b>corresponding R,G,B values</b>.
 
-## Linux terminals and colour support
-
-The general syntax rules for colours is in the form of **fg_bg** values,
-where a value of 38 stands for the foreground, and 48 stands for
-the background.
-
-The ANSI colour for red is 196 and the ANSI colour for black is
-0.
-
-To use the colour red, you could issue this command:
-
-    printf "\e[38;5;196m Hello world in red\n"
-
-To use the colour black as background, you could issue this command:
-
-    printf "\e[48;5;0m Hello world in black\n"
-
-Do note that the same can be accomplished via RGB values rather than
-ANSI color codes, as long as the terminal supports this (KDE Konsole
-does).
-
-Depending on whether you want to apply the color to the foreground or
-to the background, use an **fg_bg** value of 38 or 48 (respectively).
-
-Example:
-
-    printf "\e[<fg_bg>;2;<R>;<G>;<B>m"
-    printf "\e[38;2;255;0;0m Foreground color: red\n"
-    printf "\e[48;2;0;0;0m Background color: black\n"
-
-This may be the better variant altogether, as it is quite easy to convert
-into (and from) **RGB values**, but your mileage may vary.
-
-Of course you can use this in plain ruby just as well - let's show this
-via puts:
-
-    puts "\e[38;2;#{222};#{131};#{141}m Hello world!"
-    puts "\e[38;2;#{122};#{56};#{141}m Hello world!"
-    puts "\e[38;2;122;156;141m Hello world!"
-    puts "\x1b[3mHello world!\x1b[0m"
-    puts "\e[38;3mHello world!\x1b[0m"
-
-In bash the ESC code can be either of the following:
-
-    \e
-    \033 (octal)
-    \x1B (hexadecimal)
+Note that in November 2023 I rewrote parts of the gem. This also
+led to a re-evaluation of methods such as sdir() or sfancy().
 
-The "\e[0m" sequence removes all attributes, including formatting and colors.
-It may be useful to add it to the end of each colour text - and this is
-what the **Colours** project is essentially doing.
-
-To see which colours are supported/supportable, for each terminal,
-have a look at the following **link**:
-
-https://misc.flogisoft.com/bash/tip_colors_and_formatting#terminals_compatibility
-
-To set both the foreground and background colours at once, you can use:
-
-    printf "\e[S;FG;BGm"
-    echo -e "\e[S;FG;BGm"
-
-For example, bold white foreground on a red background:
-
-    printf "\e[1;97;41mHello world!"
-    printf "\e[1;97;41mHello world!\n"
-
-Thus, if you would like to use red colour on black background,
-you could do this:
-
-    printf '\e[38;5;196m;\e[48;5;0m Hello world!\n'
-
-Specifically, the background colours are:
-
-    40  black
-    41  red
-    42  green
-    43  yellow
-    44  blue
-    45  magenta
-    46  cyan
-    47  white
-
-The following command will use red background:
-
-    echo -e '\e[0;41m'
-    echo -e '\e[0;41m hello world\n\n ok\e[0;m'
+I use sfile(), sdir() and sfancy() a lot. I also use simp(),
+as abbreviation for simportant(), sometimes. However had, other
+methods, such as ssymlink(), I rarely use; and I never used
+sarguments(), yet the project still carried code that supported
+such a use case. During the partial rewrite in November 2023
+I decided to deprecate and remove sarguments() aka Colours.sarguments().
+I also deprecated snormal(), aka Colours.snormal(), as I also have
+not ever used that method actually.
 
 ## Obtain all available HTML colours
 
@@ -351,45 +423,6 @@ Use code similar to the following variant for this:
     class Foobar < Colours::Base # Or whatever the name of your class is
     end
 
-## KDE Konsole support
-
-The **Colours gem** used to have a submodule called **Konsole**,
-in particular the <b>KDE Konsole</b>. In May 2019 this submodule
-was removed; the functionality is now available in the form of
-an autogenerated .rb file instead.
-
-You can **use RGB colours** in the KDE konsole (but also in
-other terminal-types such as vte-based ones, like
-**mate-terminal**).
-
-For an example, have a look at the file **bin/colours**
-that is distributed with this gem here (the colours gem). That file
-will output all the HTML colour variants (via their RGB values).
-Best shown on a black background in your terminal.
-
-To **view all RGB colours** based on their HTML names, such
-as <b>palegreen</b> or <b>slateblue</b>, do this:
-
-    colours
-
-Also note that since as of **May 2018**, you can invoke the
-HTML colours on the Konsole namespace directly, including
-text-output, via code like this:
-
-    Colours.edarkgreen 'yo there'
-    Colours.eslateblue 'yo there'
-    Colours.eroyalblue 'yo there'
-    Colours.edarkgreen 'Hello world!'
-
-The leading 'e' of these methods stands for "echo", aka
-puts-related output. In other words, to print the text
-that comes afterwards.
-
-To print something in bold, you can use **Colours.bold()**
-like in this way:
-
-    Colours.bold
-
 ## Showing the colour palette on the commandline
 
 You can show the "classical" ASCII colours on the commandline by
@@ -605,11 +638,11 @@ then you can require the module, and include it into your class.
 
 Example for this:
 
-    require 'new_colours/autogenerated/support_for_256_colours.rb'
+    require 'colours/autogenerated/support_for_256_colours.rb'
 
     class Foobar
 
-      include NewColours::SupportFor256Colours
+      include Colours::SupportFor256Colours
 
       def initialize
         puts darkturquoise('HELLO ')+
@@ -1037,28 +1070,28 @@ Here is example code that shows this functionality:
 
 ## Colours.new
 
-Since as of November 2022 <b>Colours.new</b> can be used to
-build up a String that should be colourized.
+Since as of <b>November 2022</b>, <b>Colours.new</b> can be used
+to build up a String that should be colourized.
 
 This will internally delegate towards:
 
     ::Colours::Colours.new(i)
 
-This may need some modifications in the future; the code is
-also a bit confusing right now.
+This may need some modifications in the future; the code is also
+a bit confusing right now.
   
 ## Licence
 
 The colours project used to be under the **GPL-2.0 licence** (no later clause),
-until **August 2019** (**26.08.2019**, in dd.mm.yyyy notation).
+until **August 2019** (**26.08.2019**, in <b>dd.mm.yyyy notation</b>).
 
 However had, I have changed my mind for various reasons (including the
 situation that different projects, with different licenses, may make
 use of the **colours gem**) and thus re-published the colours
 project under the less stringent **MIT licence**. Both licences, GPL and
-MIT, are perfectly fine licences, but I feel that for the basic building
-blocks, such as the colours gem, a less stringent licence makes a lot
-more sense.
+MIT, are perfectly fine licences, but I feel that for the <b>basic building
+blocks</b>, such as the colours gem, a less stringent licence makes a
+lot more sense.
 
 See the file **LICENCE.md** for this licence, or just have look at
 the following URL here:
@@ -1085,12 +1118,14 @@ on something IF the no-warranty clause would not be mentioned).
 https://ss64.com/nt/syntax-ansi.html
 
 https://www.lihaoyi.com/post/BuildyourownCommandLinewithANSIescapecodes.html
-^^^ This one shows how to build a progress-indicator in python. The equivalent
-ruby code is very similar.
+
+^^^ This webpage one shows how to build a progress-indicator in python. The
+equivalent ruby code is very similar.
 
 ## Commandline executables for individual colours
 
-In March 2023 I decided to add files such as bin/orange.
+In <b>March 2023</b> I decided to add files such as 
+<b>bin/orange</b>.
 
 The idea here is that you can chain this via a pipe, such as:
 
@@ -1101,13 +1136,94 @@ Or simply:
     orange Hello world!
     orange foobar.md # This variant should read the file, and read its content.
 
-My idea is to add this for each HTML colour. However had, I am not yet
-certain whether this should be done. So for now, I may add single 
-individual files. Perhaps in the future all HTML colours will have a
-corresponding bin/ executable file.
+The idea here is to add this for each HTML colour. However had, I am not yet
+certain whether this should be done, as it would lead to many more files
+added to the colours gem. So for now, I may add single individual files
+but probably not all HTML colours, as executables. Perhaps in the future
+all HTML colours will have a corresponding bin/ executable file or I may
+add the option to autogenerate these files - we'll see.
 
+## KDE Konsole support
 
-## Contact information and mandatory 2FA coming up in 2022
+The **Colours gem** used to have a submodule called **Konsole**,
+in particular the <b>KDE Konsole</b>. In <b>May 2019</b> this submodule
+was removed; the functionality is now available in the form of
+an autogenerated .rb file instead.
+
+You can **use RGB colours** in the KDE konsole (but also in
+other terminal-types such as vte-based ones, like
+<b>mate-terminal</b>). gnome-terminal also supports true
+24 bit colours, which means that 16 millions colours are supported.
+
+For an example, have a look at the file **bin/colours**
+that is distributed with this gem here (the colours gem). That file
+will output all the HTML colour variants (via their RGB values).
+Best shown on a black background in your terminal though.
+
+To **view all RGB colours** based on their HTML names, such
+as <b>palegreen</b> or <b>slateblue</b>, do this:
+
+    colours
+
+Also note that since as of **May 2018**, you can invoke the
+HTML colours on the Konsole namespace directly, including
+text-output, via <b>code like this</b>:
+
+    Colours.edarkgreen 'yo there'
+    Colours.eslateblue 'yo there'
+    Colours.eroyalblue 'yo there'
+    Colours.edarkgreen 'Hello world!'
+
+The leading 'e' of these methods stands for "echo", aka
+<b>puts-related output</b> (display onto the commandline).
+In other words, <b>to print the text that comes afterwards</b>.
+
+To print something in bold, you can use **Colours.bold()**
+like in this way:
+
+    Colours.bold
+
+How to use this in raw KDE konsole, if ruby is not available?
+
+You need to make use of the corresponding R, G and B
+values.
+
+Example for this:
+
+    printf "\e[38;2;100;200;200mTesting this output\e[0m\n"
+
+## class Colours::ReplaceTokensWithColourCode
+
+class Colours::ReplaceTokensWithColourCode can be used to
+replace HTML-like tokens, such as <one>, in a given String.
+
+The use case for this is to be able to easily colourize
+words on the commandline, as well as sentences, in different
+colours. The studium-gem makes use of this, for instance,
+where exam-questions are colourized based on the more important
+parts of the question at hand.
+
+## Colours::HtmlColoursMethods
+
+class Colours::HtmlColoursMethods will hold code for making
+use of HTML-colours as method names, such as:
+
+    Colours.royalblue()
+    Colours.royalblue('Hello World!')
+
+To require this file do:
+
+    require 'colours/autogenerated/html_colours_methods.rb'
+
+Note that depending on how you require the colours gem,
+this may also be automatically pulled in if you do:
+
+    include Colours
+
+And then use methods such as Colours.sfancy().
+
+
+## Contact information and mandatory 2FA (no longer) coming up in 2022 / 2023
 
 If your creative mind has ideas and specific suggestions to make this gem
 more useful in general, feel free to drop me an email at any time, via:
@@ -1117,36 +1233,51 @@ more useful in general, feel free to drop me an email at any time, via:
 Before that email I used an email account at Google gmail, but in **2021** I
 decided to slowly abandon gmail, for various reasons. In order to limit the
 explanation here, allow me to just briefly state that I do not feel as if I
-want to promote any Google service anymore when the user becomes the 
-product (such as via data collection by upstream services). I feel this is
-a hugely flawed business model.
-
-Do keep in mind that responding to emails may take some time, depending on
-the amount of work I may have at that moment.
-
-In <b>2022</b> rubygems.org, or rather the corporate overlords who control the
-rubygems.org infrastructure these days, decided to make 2FA mandatory for every
-gem owner eventually: see
+want to promote any Google service anymore when the user becomes the end
+product (such as via data collection by upstream services, including other
+proxy-services). My feeling is that this is a hugely flawed business model
+to begin with, and I no longer wish to support this in any way, even if
+only indirectly so, such as by using services of companies that try to
+promote this flawed model.
+
+In regards to responding to emails: please keep in mind that responding 
+may take some time, depending on the amount of work I may have at that
+moment. So it is not that emails are ignored; it is more that I have not
+(yet) found the time to read and reply. This means there may be a delay
+of days, weeks and in some instances also months. There is, unfortunately,
+not much I can do when I need to prioritise my time investment, but I try
+to consider <b>all</b> feedback as an opportunity to improve my projects
+nonetheless.
+
+In <b>2022</b> rubygems.org decided to make 2FA mandatory for every
+gem owner eventually:
+
+see
 https://blog.rubygems.org/2022/06/13/making-packages-more-secure.html
 
 Mandatory 2FA will eventually be extended to all rubygems.org developers and
 maintainers. As I can not use 2FA, for reasons I will skip explaining here,
-this means that my projects will eventually be taken over by shopify (or,
-correspondingly, whoever effectively controls the rubygems.org ecosystem).
+this means that my projects will eventually be removed, as I no longer
+have any control over my projects hosted on rubygems.org (because I
+can not use 2FA).
+
 At that point, I no longer have any control what is done to my projects
-since shopify (respectively those controlling the gems ecosystem) took away
-control here. Not sure at which point ruby became corporate-controlled -
-that was not the case several years ago.
+since whoever is controlling the gems ecosystem took away our control
+here. I am not sure at which point ruby became corporate-controlled -
+that was not the case several years ago, so something has
+changed.
 
 Ruby also only allows 2FA users to participate on the issue tracker these
 days:
 
   https://bugs.ruby-lang.org/issues/18800
 
-(Note that this was changed a few months ago, so the last part is no
-longer valid - it is possible to register again without mandating 
-2FA. I will retain the above notice for a bit longer, though, as I feel
-we should not restrict communication via mandatory authentification
-in general. Fighting spam is a noble goal, but when it also means you
-lock out real human people then this is definitely NOT good.)
+But this has been reverted some months ago, so it is no longer applicable.
+Suffice to say that I do not think that we should only be allowed to
+interact on the world wide web when some 'authority' authenticated us,
+such as via mandatory 2FA, so I hope this won't come back again.
+
+Fighting spam is a noble goal, but when it also means you lock out
+real human people then this is definitely NOT a good situation
+to be had.