Adding strict hostmask isn't the only option, you can use wildcards and
the most used wildcards are now explained.
* any nick with specific ident (*!ident@host)
* server which doesn't have bots, but has multiple users
* anything with specific host (*!*@host)
* cloaks/vhosts
...to identify to Services.
Did this get a little too verbose? I think that this did, but I need
help making this a little less verbose and CertFP requires verbosity.
* mention that .rpm package is also available
* note that Windows users should run global installation commands with
Administrator rights and also remove `sudo` from beginnings of lines.
* note that pip should be upgraded if it fails to do any of the
installation commands when git is installed.
h curl
curl is more often installed than pastebinit and is widely used and
might be installed by default on some systems (I believe Fedora 20 is
one of these).
With help from \#supybot I understood that telling user to add `sudo` in
front of every command isn't very user-friendly.
If someone has root and is logged in as root, they know to remove the
`sudo` part and if they don't, but they have `sudo` installed,
everything works directly and `sudo` doesn't even ask for password.
* Update config variables
* add favicon
* host is nowadays known as hosts4
* add hosts6
* move keepalive above port as that is how it appears in the bot too
* specify that HTTPd might require port change, not HTTP
* HTTPd might not work if port is too low = port is under 1024
* Apache is in front of Supybot's HTTPd, not behind.
* There is no umode +E at freenode, it's +R.
* Limnoria does support proxies.
* Our issue tracker is at GitHub and even Supybot moved away from SF.
* Plugins might be case-sensitive.
* remove references to editing the config file by hand
* update `config list supybot` from Limnoria
* mention `config setdefault` instead of nesting `config default`
* update config search op
* comment `Editing the Configuration Values by Hand`
