* Add Setup Guides to README.md
Seriously, I setup all of the telegram thing wrong because the guide isn't in the readme :\
* Reverting changes from before, updating installation
* remove extra lines
They were blank.
* remove extra space
holy crap
Currently, Slack is supported by the codebase, but support for it is not
indicated in the README.
Help future readers by adding it to the readme as an officially
supported service.
I know there is a note about the default communication method not actually checking the certificate which is why libcurl is recommended. However, I just tested this without curl and it doesn't send anything without ca-certificates installed.
I followed your model of making examples use `aptitude` however, I might consider changing that in the future to `apt-get` just so newcomers don't sit there wondering what `aptitude` is ;)
The appropriate *_proxy environment variables aren't always detected properly
by libcurl. This allows manually setting the proxy when this happens, and
disabling SSL certificate verification if the proxy requires it.
Loading as a user module will require either the webadmin or
controlpanel module, as ZNC Push will retain the current behavior
of loading as a network module by default.
Fixes#79
When compiling with USE_CURL defined, znc push will use libcurl for
making http requests instead of ZNC's builtin CSocket library. This
enables some advanced features, such as supporting HTTP proxies for
outbound requests.
Currently, building with curl support requires running the following:
make curl=yes clean install
libcurl must already be installed and accessible by default. Otherwise,
it is up to the user to populate CXXFLAGS with the appropriate values so
that znc-buildmod can appropriately find and link libcurl to the module.