Fibreglass is terrible at all of the things you just listed and we use it for all kinds of things. It just has to be coated with a thin protective layer.

Apple is also a trademark, so they are not allowed to use that in advertising either.

I'm not familiar with Mexican law either but these laws are pretty well unified by international treaties. You cannot use another company's trademark in your advertising material unless you have permission. Any carrier who sells the iPhone to customers would have permission to use the trademark, so this tells me the carrier does not sell iPhones and therefore has no business using iPhone in their ads.

This is one of many reasons why I like Safari -you have to jump into the command line settings to *enable* backspace-to-go-back.

It's definitely the best browser available, in terms of getting little things like this right.

Darwin is open source too, so you can fork it and install whatever apps you want.

The fact is most people stick with the official release. Your platform is not "open" if your official release if third party extensions aren't allowed.

It's worth mentioning the (non-mobile) version of Safari does allow arbitrary third party extensions. There are some warnings to the user that it might be malware, but they don't block installation.

A server cannot ask for encryption.

Unless the client establishes a secure connection in the first place, the server has no way of knowing if the client is actually who they claim to be. If the client attempts to establish a secure connection and the server responds with "I can't give you a secure connection" then the client needs to assume there is a man in the middle attack going on and refuse to communicate with the server.

There is no way around it, security needs to be initiated on the client and the server cannot be allowed to refuse a secure connection.

HSTS is a partial solution for this problem (http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)

I don't think HTTP has any problems with security. All the real world problems with HTTP security are caused by:

  * dismally slow roll out of dnssec. It should have been finished years ago, but it has barely even started.
  * the high price of acquiring an SSL certificate (it's just bits!).
  * slow rollout of IPv6 (SSL certificates generally require a unique IP and we don't have enough to give every domain name a unique IP).
  * arguments in the industry about how to revoke a compromised SSL certificate, which has lead to revocation being almost useless.
  * SSL doesn't really work when there are thousands of certificate authorities, so some changes are needed to cope with the current situation (eg: dsnssec could be used to prevent two certificate authorities from signing the same domain name)

There shouldn't need to be a person in the car at all. I want my autonomous car to drop me off in the taxi zone outside work, then wander off by itself to find free parking. When I finish work I'll summon it via my phone, and it'll meet me on the street outside the office.

I have encountered the problem, and solved it for friends/family.

Since I'm an iOS developer, anybody who has any problem with their iPhone asks me how to fix it. And since I'm a tin-foil-hat-toting privacy advocate, I have studied various articles that reverse engineer how iMessage works. I know exactly what "delivered" means —it means some device somewhere decrypted the message. Apple's server cannot decrypt the message as they do not have the private key, so therefore they cannot possibly send a delivery confirmation.

Go ahead and try it out. Disable wifi and cellular data on an iPhone but leave the non-data cellular connection active, then send an iMessage to it.

The message will not change to "delivered" unless some other device is registered (and connected to the internet) to receive messages at that phone number. After some minutes, the blue message box on the sending device will change colour to green, signifying an SMS has been sent. Depending how good your cell carrier is, the SMS will be delivered instantly or after a few days (SMS is not a reliable messaging protocol...). This assumes you have not disabled SMS fallback on the sending device, which is the default.

I just did the test, and it proved my theory. Disconnecting my phone/ipad/mac caused a sending device to fail to show "delivered", and several minutes later my phone received an SMS message.

The system is overly complicated, mostly as a byproduct of Apple's end-to-end encryption system, which leads to a lot of customer confusion and miss-information when they try to diagnose one of the many things that can go wrong. But I know what I'm talking about, delivered means it was delivered to a device registered receive iMessages at that phone number.

You're wrong, I know from experience that sending an iMessage to someone outside cell network range causes it to fall back to sending an SMS.

Also, I had a friend who would constantly receive double messages, because she had poor cell network coverage in her home, phone/sms worked fine but data had huge packet loss. iMesasge couldn't reach her and would fallback to SMS 50% of the time. When she reads the SMS the phone would connect to wifi and she'd receive the iMessage while reading the SMS, hens the regular complaints about double messages.

The fallback to SMS is enabled by default. You must have turned it off.

Or just have high enough Karma that they'll let you turn the ads off for free.

I don't know about Sweden but in most countries any business can refuse to server any customer for whatever reason they want, so long as it isn't race or gender or something discriminatory.

Here in Australia shoplifting will probably just get you kicked out of the store and told never to come back. The reason is the person doing the shoplifting (often a kid) might simply tell the cops that they're innocent. From then on the store will have to either drop their accusation or take it to court, which involves sending many thousands of dollars to your legal team, for no gain at all. You already recovered the stolen merchandise, so are not eligible for any compensation.

Unless they're a repeat offender, a judge will probably let them off with a slap on the wrist. Sending some poor kid who doesn't no better into the prison system over a stolen CD is a bad idea —inevitably that will lead them to commit more serious crimes later in life.

Since $15 per month is apparently enough to cover a $180 fine, they must be going on the assumption fare dodgers will be caught less than once per year.

That's how it works. The "reasonable amount of time" is 5 minutes. And any message sent within those 5 minutes will automatically be re-sent as an SMS (which unfortunately means the recipient will receive the message twice... once the iMessage finally arrives).

And there can't be any bugs, because in order to acknowledge receipt of a message you have to decrypt the message, and the decryption keys cannot be copied off the device the message is being sent to. Part of it is stored in a dedicated corner of silicone, which cannot be read by software.

Apparently Apple knows less about their own products than I do as an Apple developer. You can't trust a random support employee to know how iMessage works, it's a complicated system.

It's very simple. If you send an SMS to a number registered as being an iPhone, it will be encrypted for that phone and sent over the internet. If the phone does not decrypt the message and send an acknowledgment within a few minutes, it will be sent as an SMS instead. Repeated delivery failures (2 or 3?) will automatically disable iMessage.

According to the article, the iMessage is sent and status immediately changes to "delivered". That means he has at least one device registered to receive iMessages at that phone number and it is turned on and received the message. His claim to have logged out of iMessage on all his devices is bullshit. He forgot one.