Sulake browses this section. Let's not give them any ideas.
Perhaps they've got a reason, but for now, shhhhhhh.
IPad isn't a good idea for retros. At least for my scenario. An Ipad 2 costs like $500 here in Brazil. All the cool and spoiled kids that actually can pay for it can also pay for habbo credits. Not worth developing any further IMO.
If you think smart you will realize why Habbo does that. Habbo has over 100 places where they put the ip.. So what if that IP changes? They just modify the DNS record and all done.. Same way as I do it. Pritty dumb to use IP-addresses these days while you can do it much smarter.
Haha it's pritty smart if you use DNS records instead of IP's. So yeah, thats actually the reason why.
Also you can do these things with DNS records and build almost 20 proxy servers for your retro:
Very nice. Prefer not to announce the IP's on forum. You can however do the nslookup yourself to my domain. And this works excellent. I'm using iptables to forward it to the right server on all the 3 ips listed above.Code:noc mvdworp # nslookup game.habbnet.nl Server: 217.117.***.*** Address: 217.117.***.*** Non-authoritative answer: Name: game.habbnet.nl Address: 217.117.***.*** Name: game.habbnet.nl Address: 217.117.***.*** Name: game.habbnet.nl Address: 217.117.***.***
If the IP changes they could lunch an App Update. Anyway, ain't the best option, if they want to fix something up, they fix something up, not make jerry-rig with that, using IP address, if they want to fix it, they could simply fix it, but I'm getting to the conclusion they are lazy btw
Perfect point. I've been thinking about it, but how does iPad apps chance headers? Should it have some sort of http request that returns the header list? Or the app itself have some sort of calculator, since its differenrent from habbo, even if we decrypt it for getting the (possible) algorithm, the browser version would be intact.
I have serious doubts about this.
Awesome work!! !""#@!!!!
Thank you, very much.
There is definitely an algorithm which would change the headers in each release.
I mean, it would impractical to change them each release manually. However, I don't think you would get the chance to find that algorithm, as I wouldn't believe its something they have embedded into the client, I believe it would be applied before the release goes live.
- - - Updated - - -
Wow. Dumb question, please excuse my stupidity. Of course, I don't know why I didn't think of that. ^_^
I suspect it may be a algorithm, based on the fact that the release header appears to be a constant value.
Based on that very fact, I believe there is a possibility it's reversible or able to be predicted, because why would they need to have the header value a constant value, why wouldn't it change? So, there is a reason why that is, that's why I suspect it may be reversible or predicted.
However, that also being said, that is a very far fetched theory, and one that is potentially unlikely.