-- Connecting before identifying to NickServ (or whilst services are unavailable
- due to a netsplit or maintenance) will show your uncloaked IP/hostname
- connecting via SASL can help a little here, as authentication is done much
- earlier in the connection)
-- Connecting via a gateway (for instance, the webchat) will override
- unaffiliated cloaks (see the "gateway cloaks" section above)
-- Due to the nature of IRC services, there are some tricks which can cause
- services to reveal a cloaked user's IP/hostname.
-- Accepting a DCC chat/file transfer session, or clicking a link someone sends
- you could reveal your IP to them
+ - Connecting before identifying to NickServ (or whilst services are
+ unavailable due to a netsplit or maintenance) will show your uncloaked
+ IP/hostname. [Authenticating with SASL](/kb/answer/sasl) avoids this if
+ configured to abort the connection on authentication failure.
+ - Connecting via a gateway (for instance, the webchat) will override
+ unaffiliated cloaks (see the "gateway cloaks" section above)
+ - Due to the nature of IRC services, there are some tricks which can cause
+ services to reveal a cloaked user's IP/hostname.
+ - Accepting a DCC chat/file transfer session, or clicking a link someone sends
+ you could reveal your IP to them