You're correct. And to complete it:

"Larger content (Concatenated SMS, multipart or segmented SMS or "long sms") can be sent using multiple messages, in which case each message will start with a user data header (UDH) containing segmentation information. Since UDH is inside the payload, the number of characters per segment is lower: 153 for 7-bit encoding, 134 for 8-bit encoding and 67 for 16-bit encoding." -- from Wikipedia

So, in this case it's 134 bytes and not 140 since the payload probably doesn't fit in a single 140 bytes.

SMS has a limit of 160 characters, not 140. Twitter has a 140-character limit because of its SMS-interface which leaves 20 characters for commands etc. in addition to the message.

Well, I think Google would rather not lose that 1% market share because users that can't figure out how to fix their network. Try explaining your grandmother that because of her IPv6 connectivity Google isn't working while she can go to CNN's site perfectly.

No; your DNS server resolves the domain names at Google, so technically they're correct (although it may be a bit confusing). The idea is that ISPs with proper IPv6 can register their DNS servers so that Google will give out AAAA records to those DNS servers. Google can't help a single user since there's no way for them to influence the DNS query.

I still think that it'd be great if maybe OpenDNS or a similar service would provide an option to get AAAA records for Google.

From Google:

Simply said, some networks may have borked IPv6 which would mean that users will be unable to access Google. I can understand that they're doing this before rolling it out to everyone. Maybe there could be something like OpenDNS for IPv6 so that more advanced users have a choice?