A few ncdu 2.x releases

dat/ncdc/faq.md

@@ -76,12 +76,13 @@ The user list has three boolean flags: **O**perator, **P**assive, and whether th
 
 # Troubleshooting
 
-## Luadch: "(error-40) Invalid named parameter in inf: I4"
+## Active mode doesn't work!
 
-This error occurs when connecting to (some?) luadch hubs. The problem here is
-that IP address autodetection is broken on these hubs, and you can work around
-it by manually setting `active_ip` to your (public) IP address: `/set
-active_ip 1.3.3.7`.
+It's possible that you are still listed as passive in some hubs even if you
+have `/set active true`. This happens when the (NMDC) hub does not support IP
+autodetection or when it drops user info updates. You can work around this
+issue by manually setting your public IP address with `/set active_ip
+YOUR-IP-HERE`.
 
 ## The Alt- keys don't work!
 
@@ -91,12 +92,6 @@ press and release the 'Esc' key as a replacement for Alt-something. If you're
 on OS X, [this stackoverflow answer](http://stackoverflow.com/a/438892)
 may be helpful.
 
-## Ncdc crashes a lot!
-
-Ncdc 1.22.1 has no known bugs that may cause a crash. If you're running an older
-version of ncdc, please upgrade. If your ncdc is up to date and you still have
-a crash, please report a bug.
-
 ## Ncdc uses too much disk space!
 
 First, look where this disk space goes to (hint: use [ncdu](/ncdu)). If it's
@@ -118,6 +113,14 @@ simple script that runs from a cron. For an example of the latter option,
 [this is the script I use](http://p.blicky.net/s7132), which is run as a
 monthly cron job.
 
+## "TLS error: Key usage violation in certificate has been detected."
+
+Some hub operators don't know how to generate proper TLS certificates and other
+DC clients tend to be even more lax about validating certificates than ncdc. To
+work around this error, add the `%COMPAT` flag to your `tls_priority`, for
+example: `/set tls_priority NORMAL:%COMPAT`.
+
+
 # Can ncdc...
 
 ## Can ncdc run in the background / as a daemon?