Having two phones went out of style in China a few years ago because most phones for the Chinese market can use (at least) 2 SIM cards simultaneously, but no such luck the Galaxy S6 I got in the US. There’s no way I’m giving up my T-Mobile SIM card, either: my plan comes with unlimited free data while roaming internationally, and while it’s not terribly fast, it’s a real lifesaver in China. You see, the Great Firewall is designed to limit access to information for locals, not foreigners, so it doesn’t even bother blocking mobile data if you’re roaming. This means that—wonder of wonders!!—I have slow but steady, constant access to Instagram, Twitter, and all of the Google services I use regularly.
But at the same time, having a local Chinese number is indispensable, not least because many local mobile and web services require one for verification purposes. And the Great Firewall goes in both directions: Chinese apps run incredibly slowly outside of it. My solution was to get a second phone in China that I could use just for phone calls and Chinese apps, and I ended up with the Oppo, a low-end Android smartphone designed for the Chinese and Indian market.
NETWORKS + NEW TOWNS is an extended site study of Jonathan, Minnesota and related areas. The suburban neighborhood of Jonathan was one of the first “totally planned communities” in the Midwest, born during the short-lived “New Town” movement of the late 1960’s. It grew up during an era characterized by great faith in the power of urban planning and the transformative potential of communications technology. This work uses Jonathan as a microcosm to understand the ways that we augment the earth with matter and data in an ongoing pursuit of better living.
The other chapters of the series are all really great.
I am a big fan of pretty much all of the women who appear in this video. It’s worth setting aside 18 minutes and listening to what they’ve been up to. There is also a book, available in both pulp and downloadable PDF formats.
In a pair of recent posts, Andre Torrez outlined an idea for solving the “how do I get photos from my iPhone onto a website” problem. I like this idea, and I’d happily install this hypothetical Community Camera app if anyone ends up developing it.
The central mechanism for Andre’s idea is a new URL protocol
camera: (similar to
ftp:) that a simple camera application could claim control over. One such built-in protocol on the iPhone is
sms:, which lets you easily direct users to send an SMS message. For example, clicking on this link (with URL
sms:+12125551212) would switch you over to the SMS application with the phone number already filled in. Here is a handy list of other iPhone-supported protocols. But if you’re not reading this on an iPhone, pressing that link will probably give you an error message.
sms: links are supported, and make the process much more seamless for users. As far as I know (
correct me if I’m wrong), such a mechanism doesn’t exist yet. It exists! See update below.
The email workaround
One workaround solution, used by many web applications including Flickr, is to provide a special email address that allows you to upload photos as an attachment. The benefit is that every computer with a browser supports email links, smartphones and otherwise. The downside is the unwieldy sequence of steps you have to follow. In the best case scenario, a user has already saved the web app’s special email address to her contacts:
- Switch to the Camera app, take a photo or find the one you want from your library
- Press the “utility button” and choose “Email Photo”
- Fill in the email address from contacts and press send
- Switch back to the browser and wait for the attachment to be received by the web app
A number of factors complicate this process, starting with the initial messaging. The natural thing to say is “Email a photo to upload,” linked with a
mailto: URL protocol. But on the iPhone you can’t attach photos from the Mail app, it only works from the Camera side of things. So that “Email a photo” link should probably go to a page that explains the process outlined above, including the important step zero “add our special email address to your contacts.”
Email uploading requires that you’re willing to read a bunch of steps, understand them, and follow them. Additionally, the web application is left with no button that initiates the process and no way of giving feedback about whether it worked or not. If you reload the web app and you see your photo, then it worked. If not, maybe you’ll get a email bounce message. It’s a process that works okay for experienced users, poorly for novices, and that fails ungracefully.
Plus there is the implementation challenge of receiving and parsing email, which is kind of a pain in the ass. As an alternative to Andre’s plan, if somebody wants to write a general purpose email-to-upload service, I would find that pretty useful. Or does this exist already? I haven’t looked very hard.
Compare those steps above to the
camera: method (including step zero, “install the Community Camera application”):
- Press the “upload photo” link, with its “camera:” URL protocol
- Using the native app that appears, take a photo or choose one from your library
- When finished, the app switches you back to a page that has useful feedback
This is a better user experience, but it does require that someone go and write that native camera app (and that I install it). And unless there’s some way of checking for
camera: support, even this will require some additional explanation.
Multimedia Messaging Service
Yet another solution can be found in SMS, or its more advanced permutation MMS (Multimedia Messaging Service). Using the
sms: protocol mentioned above, I could create a link to
sms:email@example.com that behaves almost exactly like the email upload method, while avoiding some of its complexity. On the iPhone, you can attach photos from the Messages app, and you can send MMS messages to an email address. And since there’s a link that initiates the process, it allows web apps to give some feedback on the page in response to a
The downside to this method is that it requires the user to have a mobile plan with reasonable rates for sending MMS messages, and could fail ungracefully for users who aren’t fully informed about their mobile plan.
In any case, writing all this up has made me realize web browsers should let you detect whether a given URL protocol is supported. Browser makers, please build that into your next release!
Update: Andre tweeted a clever trick for detecting URL protocol support! Here’s how it might work in PHP:
<?php // This will only work if the sms: protocol is supported header('Location: sms:firstname.lastname@example.org'); // If not, fall back on this other page echo '<html><head><meta http-equiv="refresh" content="0; url=sms-not-supported.html" /></head></html>'; ?>
Legislation that would break the Internet is absent from television news:
As the Stop Online Piracy Act (SOPA) makes its way through Congress, most major television news outlets — MSNBC, Fox News, ABC, CBS, and NBC — have ignored the bill during their evening broadcasts. One network, CNN, devoted a single evening segment to it.
To their credit, the online arms of most of these news outlets have posted regular articles about the fight over the legislation, but their primetime TV broadcasts remain mostly silent.
I’ve censored the following, in protest of a bill that gives any corporation and the US government the power to censor the internet–a bill that could pass THIS WEEK. To see the uncensored text, and to stop internet censorship, visit: http://americancensorship.org/posts/6562/uncensor
█████ are two ██████ ████████ █████ ██████ █████ way ███████ ████████ (████/████) ████ █████ ██████ █████ █████████ for ████████ ████ ████ to or ████ ███████████ █████████. █████ the █████ for the ████ ███████.
I’ve been tinkering with a new design for this site for a few months and have finally gotten to the point where it feels polished enough to start using. It’s not a huge departure from what was here before, but I’ve made some structural changes to how the WordPress theme works that should make it easier for me to maintain and improve. The old theme was ambitious, I invented my own object-oriented template system that shunned the well established conventions of making WordPress themes. This is all fine and good when a site first launches, but over time I forgot how all the parts fit together and was left puzzled by my earlier choices. This new theme is much more straightforward, no PHP fanciness this time around.
Aside from that I’ve mostly just trimmed back some text in the sidebar, added a new archives interface in the footer, and beefed up my links to projects and friends. It’s still a work in progress, but with a bit more fit and finish I could see releasing the theme for others to use.
A jQuery plugin for crashing IE6. That’ll teach those motherf!%@#s to upgrade their s#%t.
What worries me – and what I feel the need to call out – is not about whether or not everyone in the world will benefit in some ways by information and communication technologies, but whether or not the privileged will benefit more in ways that further magnifies structural inequality. I am certainly seeing this as the US college level, as more privileged US freshman are leaps and bounds ahead of their less privileged peers in terms of technological familiarity, a division that makes educating with technology in the classroom challenging.
Oh man, I can’t believe it’s been a whole year!
It was one year ago tomorrow that we launched the latest redesign of MoMA.org. (March 6 is a day that will be forever ingrained in the Digital Media team’s memory!) But MoMA has had an online presence for fifteen years now, since 1995, when an exhibition site for the design show Mutant Materials in Contemporary Design was developed. The following year, the Museum’s website, MoMA.org, officially launched, and we’ve been doing exhibition feature sites ever since.
One year ago I was working remotely from Groningen, NL where Ellie was doing a study abroad program. The weeks leading up to launch day were pretty brutal, probably my most intense working process since college. It seems so absurd, in retrospect, that most of it went down for me in that sleepy Dutch college town. Happy birthday MoMA.org! It was worth it.
I just got my first email from The Ebert Club and realized I forgot to link to it here. Roger Ebert says:
I want to make some money from the web. It may appear that I have an enormously successful web site here. I do. But I’m not making any money. In the years since the site began, my share of the profits has come to a pauper’s penny. The Far-Flung Correspondents aren’t the only ones here working for free. To be sure, the Sun-Times pays me handsomely, although less handsomely since we all went through a “belt-tightening,” so as not to lose our pants.
He goes on to discuss Negroponte’s micropayment future that never came to pass. It’s a simple problem that has evaded that particular simple solution:
The web that we surf every day is not paying for itself, and we sure as hell aren’t paying for it. You read me for free, and I read everybody else for free. This is not news.
If you like Ebert’s writing, or even if you’re not very familiar with it, read more about The Ebert Club and consider sending him five bucks.
Nakamura’s MONO*crafts 2.0 was also a big inspiration for me when I was first getting into web design. It feels dated now, of course, but I remember feeling thrilled to see this bold assertion in the navigation: interfaces can be impractical, users can be invited to explore and play.