appledash / lunabot

lunabot's Issues

Log what's going on with the attempting of different TLS versions

Handlers might try to send messages after the connection starts going down

Say that during the handling of one line, Luna decides she should disconnect and sends QUIT. It is possible for a later handler (or a handler for a subsequent line) to attempt to send a further message, by which time the IRC server may already be tearing down the TLS and TCP connections.

Possible solutions:

• Make Connection.send_raw() raise an exception if this happens
  • Every handler that sends a message would have to handle that exception, though.
• Make the Connection.send_*()s return True or False to indicate whether the message was actually sent
  • This just feels wrong.
• Drop messages silently during disconnects
  • No way. This would make the API unreliable.

Any other ideas?

Detect changes to allowed TLS versions in between connection attempts and act accordingly

Detect when IPv4 or IPv6 connectivity is broken and fall back to the other one

We have no documentation and no tests

A good project should have docs and tests, right? Right? >.>

The way TLS versions are serialized is hacky and bad

Connection.connect(): actually handle exceptions raised by socket.getaddrinfo()

Give the Connection class a `status` attribute instead of just a boolean `connected` attribute

Actually load plugins, somehow

Handle password-protected client certificates

Provide hooks for plugins to request IRC CAPs

Notify the user if TLS certificate verification fails

Make IP version preference a config option

The default configuration containers are mutable

Since Python doesn't have a frozendict or anything, maybe we should roll our own?

Connection.connect(): handle the case where none of the calls to socket.getaddrinfo() return anything

The configuration lock isn't a readers-writers lock

Make Connection not a subclass of Thread

Or at least explain why the heck it is a subclass of Thread in the first place.

Read lines from the socket properly

Reading one character at a time is very much improper.