SocketTube currently allows multiple sequential read subscriber, but always uses the same internal subscription, which represents how the SocketTube itself is subscribed to the socket.

In case of error, it makes it difficult to track if the error has been forwarded to the old subscriber, and whether/how it should be forwarded to the new one.

There may be a race condition were the readScheduler is already stopped (or is in the process of being stopped) by the time the new subscriber is in the process of subscribing.

The current behavior should be reexamined to make sure the new subscriber will always get the error in that particular case.