I’ve noticed this trend to screenshot tweets instead of copy-pasting their texts in blockquotes for some time now. On web design and technology blogs, no less. You’d think these sites who constantly write articles about HTML, CSS, web standards, usability, semantics would actually listen to their own advice.
What do people get out of doing it, though? Is Twitter really that much of a game-changer that you can now break the conventions of quoting people in articles on websites? Is it really that big of a deal to debate on how you should add tweets to articles—which is so obviously linkbait?
Are tweet pages designed so much prettier than your default blockquote designs that you feel compelled to use them instead (that’s definitely an “unsuccessful designer trend” isn’t it)? Though, consider the construction: large text, a clear indication of who said the tweet, and a fuzzy timestamp. Maybe that’s what blockquotes should aspire to be?
Are tweets such special data forms that you need specialized plugins and scripts like WP Quote, Twickie, QuoteURL to display them? Or do those exist to up one’s geek cred and feed the third-party Twitter apps machine?
Still, those aren’t as bad as web apps like tweetshots. Want to share a tweet on Tumblr? Use the Quote post type. WordPress is getting custom post types in its next major release too. But publishing platform or no publishing platform, that’s what the HTML tag <blockquote> is for.
Let me channel Steve Ballmer and say: Blockquotes, blockquotes, blockquotes, blockquotes, blockquotes. They’re not that hard to use, certainly not more than taking a screenshot and uploading it.
I understand why on some occasions using images instead of text and other data formats is preferred. They’re usually more portable when passed around in email, forums, social networks, and other communication platforms. More people know how to deal with images than URLs too. But for the purpose of quoting tweeple on websites, I see no excuse for displaying text as images.
I’ll spell it out for you in <strong> and <em>: display text as text, not as images, damn it!
Sure, screencapping tweets may not be as grave a sin as using tables for layouts, but back when that was the dominant method of creating websites, it was a pragmatic choice to make do with the technology available. The choice to use images for text is illogical today. It is confusing behavior that is inexplicably linked to Twitter’s success.
This week, the Museum of Modern Art added the @ symbol to its permanent collection in the Department of Architecture and Design. Although it stands out because it’s intangible it carries just as much history and impact. For starters, did you know that @ has been around since the 6th or 7th century to denote a unit of measure? It’s been used for commerce since, made its way into the typewriter in 1885, then in 1971, Ray Tomlinson decided to use it in the first email system, giving it new purpose in the age of computing.
The story of the @ sign and its entry into the MoMA is also a fascinating lesson on what design can do:
The appropriation and reuse of a pre-existing, even ancient symbol—a symbol already available on the keyboard yet vastly underutilized, a ligature meant to resolve a functional issue (excessively long and convoluted programming language) brought on by a revolutionary technological innovation (the Internet)—is by all means an act of design of extraordinary elegance and economy. Without any need to redesign keyboards or discard old ones, Tomlinson gave the @ symbol a completely new function that is nonetheless in keeping with its origins, with its penchant for building relationships between entities and establishing links based on objective and measurable rules—a characteristic echoed by the function @ now embodies in computer programming language. Tomlinson then sent an email about the @ sign and how it should be used in the future. He therefore consciously, and from the very start, established new rules and a new meaning for this symbol.
The article continues on its value as a different kind of design piece: “It does not declare itself a work of design, but rather reveals its design power through use.” Around the world, different countries have composed different mythologies for it, and its uses are still expanding both socially and technologically.
This is probably the greatest kind of design—the @ symbol is both ancient and modern, local and universal, practical and beautiful, by continuously evolving in its meaning.
One of the most ambitious efforts to come out of the Googleplex (or anywhere, really) in ages is Google Wave, a real-time messaging, sharing, and collaborating service unveiled last week. Finally, Google’s crack at the Real-Time Web. We’ve been waiting.
Google’s Real-Time Web
You might recall ReadWriteWeb proclaiming the big G missed the boat on that, as Twitter rules over real-time search these days. However, Wave makes one realize there is more to the real-time web than 140-character messages.
It’s a new way of doing things. It’s decentralized, open-source, and poised to take over online communications the way email has, since it’s built as a fundamental protocol. But it’s not even just “the new email”, it lets you do a lot more than that. It was built to service needs knowing the capabilities of the Web today:
Ezra Pound once wrote: “”The artist is always beginning. Any work of art which is not a beginning, an invention, a discovery is of little worth.” And elsewhere: “Make it new!”
Even more than the application itself, I love the way Wave doesn’t just build on what went before but starts over. In demonstrating the power of the shared, real-time information space, Jens and Lars show a keen understanding of how the cloud changes applications.
When I saw Wave for the first time on Monday, I realized that we’re at a kind of DOS/Windows divide in the era of cloud applications. Suddenly, familiar applications look as old-fashioned as DOS applications looked as the GUI era took flight. Now that the web is the platform, it’s time to take another look at every application we use today, and ask the same question Lars and Jens asked themselves: “What would this look like if we invented it today instead of twenty-five years ago?”
This is not another reboot of the social network format the way Google redid email with Gmail and redid search with Google Search. But it does feel this is the way social interactions on the Web were supposed to be. Aren’t you tired of signing up over and over for the hottest new web service, OpenID/etc. not withstanding?
I love the diversity and downright chaos of the Internet, but the future has got to be seamless integration between all things. Text, photos, videos, blog posts, polls, calendars, petitions, lyrics, jokes, LOLcats, whatever.
Now when Google says real-time, it means your friend’s message appears on your screen by the character, instead of a “your friend is typing…” notice as you twiddle your thumbs. It also means you can reply to any part of your friend’s message, edit any part of a document, and replay exactly how everything happened when you’re done. See video above. It’s brilliant.
Terrifying ramifications?
That’s barely scratching the surface. I’m not sure if the protocol will succeed—not everybody lives in real-time online, or can handle this many features (see Twitter).
If it does succeed, it might become too successful that users are addicted, possibly trapped in this real-time space. We continue to blur the line between the real and the virtual, and even if at this point we can tell the difference between the two, will we ever reach the point of being “too” connected, transparent, hyperreal?
I’m not even sure if we should be trust yet another invention from Google—there has to be something in it for them, right?
Are you terrified yet? I think I am, but I’m pretty excited too.
*/
