Merged
Conversation
Epicpkmn11
reviewed
Feb 8, 2026
Co-authored-by: Pk11 <pk11@outlook.jp>
|
👀👀👀👀👀👀 we made it chat. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
As you are well aware, hbchat was a disaster.
Though I don't have evidence, at least not evidence I can give away that the doxxing happened, no matter what truly happened on that night, security on hbchat was flawed, terribly flawed.
Forward a month or two, a user called @mii-man created an app called "aurorachat", it was not even functional at that point, but I decided to help him out and gave him a template that worked as @cool-guy-awesome worked on a server for him.
Even though I had other projects I was working on, I decided to gradually increase my time working on the project until I became Lead Developer. Now I've worked out the major flaws of hbchat by rewriting any and all code that was a part of it. We just released version 0.0.4, which contains a rewrite of all the code and a switch to HTTPS instead of raw TCP sockets, which are very insecure.
If you want to, feel free to check out the code.
Also, since this is only my second PR, I might've messed up the unique ID field, but hopefully I didn't.