Unnecessary `reconnect` options.

[aqilc]

I am very sure these options only add clutter to the class. Anyone can just put a listener on the close event and just re-initialize anyways, so there is literally no point. I would like to see a use case if otherwise.

[aqilc]

I'm getting rid of this completely from the Streams API in the current pull request that I'm making.

[117]

Im all for passing reconnection onto the client user.

[aqilc]

what do you mean?

[aqilc]

Sorry, i was cleaning up the stream class xd

[aqilc]

so uh, big mistake of me forgetting authentication. I'm trying to figure out how to fix.

[117]

Sorry again that im not able to merge or review these yet. On a long drive today.

[aqilc]

Ohhhh, thats kewl. Have fun :D

[aqilc]

I don't even know if you'll be able to use this but I started the documentation kind of.

[aqilc]

[aqilc]

I think this deserves a big version upgrade called 0.2.0 if you do use any of this.

[aqilc]

I don't even know why I am working so much on this, but part of it's definitely that I will have to use this in the future to make bots and I would rather have it be extremely smooth and user-friendly.

[aqilc]

@117 How did you authenticate users before? I don't spot anything special or anything valid.

[117]

Sends an ‘authentication’ message to the websocket server with key and secret.

[aqilc]

How did you get it before? I didn't spot any Client parameter or key option.

[aqilc]

Sorry for the late response, I took a shower and did some chores xd

[117]

How did you get it before? I didn't spot any Client parameter or key option.

The client is passed in the Stream constructor.

[aqilc]

oh

[aqilc]

I don't get why this error is happening: Do you happen to have any clue? I am not assigning the connection to anything else anywhere.

[aqilc]

Ok, fixed it... everything should be done now :D

[aqilc]

Fixed in a new commit, so this should be closed.