WizzyGeek

Could this be published?

Reconnection loop could be fixed by a lock in connect method or by awaiting it. Graceful closing. Wait until bot is ready and then over ride the loop's signal handlers...

A very basic implementation (of closing) https://github.com/PythonistaGuild/Wavelink/commit/90e296b27acad2deda0888fda4b08f005710de66

Maybe add a `close()` method which complements `_connect()`, so that node doesn't have to get into websocket's internals to close the web socket.

## Legal Switch to ~~GNU GPL V3~~ LGPL or any license that prevents proprietary development.

Well, we wouldn't want any improvements or better forks to be closed source. But people don't seem to like the idea. So I am fine with MIT.

Another thing, will rewrite support resuming? This is particularly useful for me since I have minor disconnects every hour.

I am interested on working on this issue, is there somewhere I can get in touch with the maintainers to work on this issue?