Months ago I had an idea that I was planning to try in an attempt to bring "Cloak Mode"
aka Auto-Resume Session back. Time passed, due to how busy I've been lately, and recently I got some time to test it out. I've now completely finished testing my new method and it's met all of my expectations. I am able to keep my name in the room even if I've been booted (disconnected) by a flooder or buffer charge & release booter and can continue receiving chat packets (messages, joins and leaves) from the room as usual.
There is no packet loss with this method, meaning, you won't be missing chat messages in the room or user joins and leaves under normal conditions (this was a problem that I was able to fix with the old "Cloak Mode" that was discovered by another developer).
The only way that the name could be taken out of the room is if a new spoof-based exploit is found or similar to log the name out of chat or out of the chat network altogether (login-based exploit, chat join/leave/logout exploit etc).Aside from the above, the new auto-resume session method is 100% resistant to boot floods causing your name to be logged out of the chat room.
The method itself is fairly involved and will take a while for me to finish developing and implementing into YTK (remember, YTK isn't a chat client, it performs the duties of both the chat client and servers). This solution could last a very long time for all of us to use due to how it legitimately works (unlike the old "Cloak Mode" which was a bug that was exploited to keep the name in the room).
I'll share my discovery with my friends that are chat developers first (one of which I already have) so they can add it into their chat clients if they choose. At some point (soon) I'll release all the details and cover the entire method, step-by-step, so other programmers can benefit from it too.
I'm confident that I can also find an alternative way, possibly one that's less involved to implement, to accomplish the same goal. I'll be on the lookout for any additional ways this can possibly be done.
There's no ETA for this yet and chances are it won't be in the next build of YTK due to the implementation work involved, time for testing the code, and fine-tuning. Please be patient as there are many, many other priorities on the "To Do" list for up and coming YTK Enhanced builds that include bug fixes, improvements, and older features to be restored.
For any non-believers, forum PM me and I'll be happy to give you a demonstration. We can setup a date, time, and a chat room of your choosing. 
I'll keep everyone updated regarding any progress that is made toward adding this to YTK.
Home
Login
Register