Quote:
Originally posted by puzzlebird@Jul 19 2006, 08:51
Well, I have to agree that I also peeked into the source code the same way as tester did, but the purpose is to get more knowledge of CO packets.
The issue is how can we share knowledge while still be acknowledged. I once cracked an encrypted network protocol for a IM, and eventually decided to GPL the code. For me, this is the way to get a better community. Now there are always quite a few applications based the cracked encryption algorithm.
Without the access to QOProxy, Etain may take longer to develop its code. The same is for the community. For the good of a "good" community, open source it. Of couse, I do not think noobs are the target here.
|
Need some help in that aspect? I've been developing my QOProxy for over a month now. It has many features and abilities that some people in you're group might like to get a hold on. As well as some simple fixes and an overall improvement from the original. I have a great knowledge of the proxy, even though I'm a messy coder like Q, I can develop any controllable packet into it. Just msg me if you're interested, or some others in you're group.