feat: Performance Improvements and Accurate UI #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now shows your current tier whilst also pulling your current usage maximums, allowing implementation of known disconnect reasoning, i.e. will not connect free or supporter tiers who have exceeded maximums and will be thrown by server.
Also improves connection times:
Resulting in an average 3s connection time, on unix machines this can possibly be reduced. The base time requirement is the reseda connection, which depends heavily on the distance to the connecting server- i.e. at a 200ms ping-to-server, the connection takes 800ms to propagate and 200ms of computing time, thus 1000ms. The windows service startup is a standard time restraint that cannot be mitigated under the current implementation but should be amendable using a different method.