The lists are cool, the “…” don’t look good on the iPhone due to word wrap, and should have a hard nonbreaking space at the beginning, so it end ends up looking like
To be able to use such unicode wonders, you should go system configuration -> keyboard -> input sources -> show input menu in menu bar.
You will now have a new doodad up in the menu bar that can launch this apple gadget called “character viewer”. You can tear apart any font with this thing and see every single damn glyph like this:
čȒâẔȲ, ŤḤȓéȆ ⓀĩⓃⅅȘ ộⓕ ℭốⓜℳÄs
one of them is hard nonbreaking space
or you can copy and paste the space here:
Wherein the reader will learn a thing or two about the device in his pocket, and how to tell a good developer from a pretender.
Apple gets a lot of ignorant hate, and a lot of ignorant reverence. Let me give some informed reverence for one area where they kick so much ass: accessibility.
We trekked out to the wilds north of Eglinton to the CNIB, dropping in on the iDevice User Group. This is a group where blind people teach each other how to get around in the world, using iOS applications as their helpers. We were the only sighted people present, there to talk to this particular subset of Pocket Rocket‘s users.
We I simply gawped when one blind woman pulled out an iPhone then snapped a perfect shot, guided by the built-in Camera app.
Eventually a common theme became apparent: Apple’s applications — Calendar, Messages, Mail, iPhoto, even Maps and most surprisingly Camera — are completely usable by blind people. These applications aren’t using any kind of secret API sauce. They’re using the same UIAccessibility framework you and I have access to.
There’s no excuse for nearly every third-party application to suck when it comes to accessibility, and yet they do.
Every third-party application examined by these users was worthy of criticism ranging from “this one thing is annoying” to “the whole thing is completely unusable.”
Consider our National Newspaper’s app: if you read a story in VoiceOver, the middle half of the story is read first, then the headline, then more story, then the start of the story. It’s crazy. Did the Globe’s iOS team even test it? Of course they didn’t. If it even occurred to them to test accessibility, then they clearly decided to ignore all the bugs and hope nobody noticed.
Here, then, lies the answer to how to tell whether some developer you’ve just met (or are interviewing) is serious about their craft in five seconds flat: borrow their device, and triple-click the home button. If you don’t hear “VoiceOver on”, or get prompted about VoiceOver, consider that −3 points on the Steve Test.1
If you’d like to get those 3 points on the Steve Test, here’s what to do.
Go into Settings app, start at the top, then tap General, then Accessibility.
At the bottom of the screen is a setting that lets you make a home key triple-click turn on VoiceOver. Turn it on.
Go into the VoiceOver panel, and turn it on. Your phone will now say “VoiceOver on” and become extremely annoying to use if you’re not used to it. A “VoiceOver Practice” button will appear.
Your mission, should you choose to accept it, is to ‘tap’ on that VoiceOver Practice button and go practice some moves. Hints:
You can drag one finger around the screen to browse until you find the button that does what you want, then put down a second finger to activate it (some call this a tap-and-a-half; the proper term is a split tap).
Use two fingers flicking down to have the entire screen read to you. This is great for news or email: your device can read a piece to you while your hands are busy driving a car or feeding your baby.
To get your mind blown, fire up Camera and point the camera at a nearby face, preferably a cute infant.
You might end up asking yourself why Apple went to such effort to let a blind person take a picture. The only answer I can give is they not only care about making accessible applications: they also actually put in the effort.
1 Special exemption for people with children, who are obliged to turn off multitasking and accessibility gestures on their iPad because the device will come back seriously messed up with ten fingers flailing away randomly at it.
Barracuda has a new product that is clearly selling well: I am unable to send email to an increasing number of people.
I am one of those people who doesn’t instinctively trust all my data to Google; I run my own email rig. That rig is a machine parked in a good colocation facility, which accepts email submitted via SMTP-AUTH and routes it out for me. There’s an SPF record and everything.
Barracuda’s product implements the clever trick of looking at the Received: header to see where my mail server got the email from. They can see the email is originating from a home DSL IP before going to my colo, which surely means I’m a member of a botnet. They have also banned most of the Rogers/Fido wireless network, so email off my iPhone is rejected even though it follows a similar route.
The difference between my email and spam email is that it goes through a system which has a good reputation, which has an SPF record to authenticate its right to send email on behalf of people in my domain name. This is clear from the Received headers, and and the fact Barracuda is getting a connection from that machine.
This bug can be worked around by using gmail or presumably any other vaguely reputable email hosting service. Even though gmail discloses my home IP address in headers as well, Barracuda have seen fit to give webmail services an exception.
Fix your stupid software, Barracuda. You’re ruining email.
Headers below. Scenario: 184.108.40.206 spooled email onto jane.tinyplanet.ca via SMTP, which has spooled up the email for delivery to someone @demandmedia.com, which is using Barracuda Reputation. jane is permitted, via my SPF, to route mail out for @tinyplanet.ca.
host mail.demandmedia.com [220.127.116.11]: 554 Service unavailable; Client host [jane.tinyplanet.ca] blocked using Barracuda Reputation; http://bbl.barracudacentral.com/q.cgi?ip=18.104.22.168
------ This is a copy of the message, including all the headers. ------
Received: from 75-119-229-140.dsl.teksavvy.com ([22.214.171.124] helo=[10.0.1.3]) by mail.tinyplanet.ca with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.76) (envelope-from ) id 1QZieP-0000y6-CK for firstname.lastname@example.org; Thu, 23 Jun 2011 08:04:49 -0400
From: Stephen van Egmond <email@example.com>
Date: Thu, 23 Jun 2011 08:05:07 -0400
X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED,BAYES_00,
TVD_RCVD_IP autolearn=ham version=3.3.1