@Kirkburn- the safari rendering system is safari exlusive. The other browsers on iOS have to use the same, horrible, rendering engines not designed for web browser specific apps.
@Princess no it's not a safari wrapper. Anything that lets you access the web on an ios device that isn't safari used the slower webviewcontroller IIRC (either way, it doesn't use what safari uses). This means two things:
1) Other browsers on iOS are technically speaking slower, with no real way around it 2) Because of how webViewController can be used, other browsers can have weird screen sizes that mess up things.
IMHO, going afk is a lot harder than it seems. I tried doing a scaled down version of chathacks a while back that just had /me and afk and it was a HUGE pain to get it to work. I don't think I ever finished it. Honestly, I think that you'd be best asking Monch to give a scaled down version of chathacks
Don't do what math did (no offense) about using @font-face for GOOGLE WEBFONTS ONLY. Google does browser sniffing so each browser sees diffent css. Instead, use an @import to URL it gives you. Use @font-face for everything else
That's hard to make because you'd have to either hardcode phrases so that even if someone says hi instead of hello, if hi isn't harcoded, there will be no response. The other way, which is a complete pain to do, is creating a neural network which understands the questions being asked for responses. Not impossible, but very hard.