Here’s the conclusion that all the web gurus seem to have drawn over the past months: HTML5 is the future, and that future is slowly creeping into our midst. This article by Dave Shea is the latest proof of that. Then there are inspiration galleries and blogs dedicated to the use of HTML5 for markup, plus hardly any mention of XHTML2 anywhere else.
rel and more meaningful links
But I’m not going to get into the war between the two here; I’ll just focus on a specific development in the arena: link relations. There’s more to it than rel=stylesheet and rel=alternate. About a dozen more.
For example, the Google-imposed rel=nofollow will be officially added in HTML5, but the seemingly convenient rel=feed may be dropped due to browser implementation. Other interesting link relations mentioned are rel=search, which obviously points to a search page, and rel=sidebar, which refers to a document “shown in a secondary browsing context (if possible), instead of in the current browsing context.” More are being proposed here, including rel=accessiblity.
rel seems to be what plugins are to web browsers, so it’s interesting to see how they can make a markup language as extensible as possible.
rev and a less rotten web
Still related to link relations is the rev attribute, which stands for a “reverse link”. It hasn’t been as popular as its cousin rel up until microblogging boomed, and consequently, URL shorteners and the threat of link rot.
Considering just how popular Twitter is these days, particularly as a social media marketing and SEO tool where links are the mode of currency, using rev=canonical to indicate one URL is a shortened version of the other:
Google introduced rel="canonical" recently. It’s a way of pointing from an alternate URL back to the canonical URL of the current document: the relationship of the linked document to the current document is “canonical”.
If you’re linking from the canonical URL to an alternate URL (like, say, a shortened URL), you could use rev=”canonical”: the relationship of the current document to the linked document is “canonical”.
People are also advised to check long URLs at this RevCanonical app to determine whether they already contain shortened ones.
New year, new decade. But we still haven’t gotten past everything Web 2.0. We’re still dealing with the consequences of the social media revolution. The question is, which side are you on?
Pull the brakes?
We’ve seen people dumping Facebook and still not getting the Twitter mania, but here’s something pretty recent: the Web 2.0 Suicide Machine is making the meme rounds for those who suffer from social networking overexposure.
Most of the time we just hop on the bandwagon, publish the smallest details of our lives with abandon, and regret our actions only when it’s too late. Sites like My Parents Joined Facebook and Lamebook capitalize on those slip-ups, and we’ve all heard stories of people getting fired for something they posted online. A clean break from it all could be the answer. Or an exaggeration.
Interestingly though, Facebook has blocked the Suicide Machine. Thanks for playing!
Shift into high gear?
Tina Roth Eisenberg a.k.a. Swiss Miss tweeted that her unborn son already has a “gmail account, 3 domain names and a twitter account”. Pretty sweet, I’d say.
Again, this isn’t really a new phenomenon, but not many people are looking that far ahead. After all, who knows what the Web will be like in five to ten years. If domain names will still be the way to access websites.
Or maintain cruising speed?
Most of us probably lie in the middle and won’t think to axe their accounts or be so protective of their online identities as though they were real estate. Even if your new year’s resolution for social networking isn’t anything drastic, it’s still important to stay on top of your privacy concerns and online persona. Have you tweaked Facebook’s Privacy Settings yet? How about all the authorized third-party apps that have access to your Twitter account? Do you Google yourself every once in a while to see how other people find and paint a picture of you?
Bonus: try integrating a workout into those beloved websites. Now there’s a productive idea.
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.
Skittles on Facebook, Twitter, Flickr, YouTube
Years from now, people will look back to the day Skittles ditched its flashy site and chose to load the top social websites that talk about it instead.
I can’t even begin to fathom how brilliant a campaign this is (despite being pioneered by Modernista exactly a year before). Maybe it’s not. I don’t know whether it’s so open-minded and fun, it doesn’t even look like a gimmick anymore or it’s just plain lazy to put the Skittles-related Twitter, Flickr, YouTube, Facebook, and even Wikipedia pages right on Skittles.com.
The cynical
Why load tweets, photos, or videos if you can just pull them via the the sites’ ever-useful APIs and create a page that’s sprinkled with 100% more colors and candy? (Come on, don’t deprive web designers and developers of their jobs!)
Is it even legal for a company to load another company’s web page to promote itself? (But asking that is like saying Facebook owns whatever you post on its site, and we all know how that turned out.)
Is seeing yourself on Skittles.com enough incentive to build buzz about the product instead of the marketers who will be handsomely rewarded anyway? (A resounding yes if you’re one of those new media douchebags, but let’s get to that in a bit.)
Do these cynical questions even matter if you’re enjoying the experience anyway?
The self-absorbed
Skittles took a risk. Some other company would have been worried about the possibility of smack and smut polluting the streams.
It’s bound to happen anyway, if this campaign lasts long enough and the new media douchebags pounce on another pure phenomenon taking place. I think that’s what draws people to this experiment. It’s raw, unfiltered, and free from any sinister intentions. (At least to the naked eye.)
Remember when SEO hadn’t been invented? When Wikipedia was an unbiased reference? When Twitter was all about what you are doing right now? When your friends on Facebook didn’t have their own fan pages?
And what about the other side of that purity—the cold, hard, messy truth? Because it’s only a matter of time when Skittles, which is not just sweet, innocent, colorful candy, but also a huge corporation, rakes up some dirt in its dealings.
If there’s one thing to take away from all this is that if you’re a company and dreaming of pulling off something like this, it’s not about you. (Or maybe it is, but can you at least try to make it look like it isn’t?)
Any publicity is good publicity, order will emerge from chaos, and worry less about projecting a reality distortion field, focus more on making your product great, because it will speak for itself.
Here are three little tweaks that go a long way in improving one’s browsing experience and should become default features on every website.
Kottke’s unread posts notification in the title bar
It’s not just web applications like Gmail or Twitter that can enforce the “push” instead of “pull” format that is associated with the real-time web. If you spend a significant amount of time browsing Jason Kottke’s site you’ll probably notice the title bar changing when a new post gets published.
I added a new feature to kottke.org over the weekend: live updating on the home page. If you leave kottke.org open in your browser (with JavaScript on) and I post a new link, the page will display a message urging you to refresh to view some new posts. The page title changes too, so if you have it up in a tab, you can tell at a glance if something’s new. Right now the page checks for new posts every ten minutes, but that could change depending on server load, etc. Thanks to Twitter Search and Tumblr for the inspiration.
Developer hack: Kottke didn’t give details on how he did it, but this script is doing the work.
Infinite scrolling
Paginated websites make digesting content more manageable, but sometimes you just want to consume as much as possible too. Imagine devouring as many Google search results and Flickr images as you can.
Infinite scrolling—at least the hacks mentioned below—load the next page when you’re done browsing the current one. The next and previous page links are still there, so you have both options to choose from.
User hack: install Greasemonkey and the AutoPagerize user script.
Developer hack: use the jQuery plugin or the WordPress plugin.
FFFFOUND!’s keyboard navigation
Don’t underestimate the efficiency of the keyboard. At image-bookmarking site FFFFOUND!, using the keyboard is the best way to get around.
Developer hack: install paging_keys_js.
The mark of anything well-made is found in the details, and when it comes to geeky conferences for designers and developers, organizers are coming up with geeky new ways to spice up the offline event experience.
Badges
Gravatar-enabled WordCamp Badges
Let me first say that Gravatars, or globally recognized avatars, should be a staple in every social network or web app that lets uses upload avatars, because why upload one everywhere when it can be pulled from a centralized location?
Now combine Gravatar with sister application WordPress, specifically its conference WordCamp, and you’ve got brilliant automated way to print photos on conference badges. The best part is you can download the source code!
Creative Mornings Q&A Badges
This one’s not so high-tech, but a neat little idea nonetheless, especially for smaller, more frequent gatherings such as Creative Mornings. In place of names on the nametags, participants have to fill in the blank with an answer to a certain question.
Past sessions have asked questions like “What would you like to redesign?”, “What can you teach me?”, “What would you do if you had your own storefront?”, and “What would make you a good client?” Cheap, easy, and an instant icebreaker.
Crowdsourcing
dConstruct Time Capsule
With the theme of dConstruct 2009 being Designing for Tomorrow, it makes total sense to come up with a Time Capsule competition, where the best entry wins free passes including hotel accommodations and a seat at the speakers dinner.
The question is simple: “What do you see that you would like to preserve for the future?” but it also underscores how important understanding the past and present is in order to build for the future. Especially when it comes to the Web.
SXSW Panel Picker
For such a massive event as the South By Southwest (SXSW) Conferences and Festivals, tapping into the wisdom of the masses makes sense. Not only does the SXSW PanelPicker increase interactivity by letting the participants vote for the talks that will go live, but it also builds extra buzz as the speakers themselves campaign for their own panels.
Twitter & Co. Mashups
MIX09 Flotzam
These days everybody is contributing to the coverage of any one event, and it’s even more awesome to experience that collaboration during instead of after the fact. Mashups such as Flotzam grabs streams from Facebook, Flickr, YouTube, Digg, Twitter, and the blogosphere. This one looks especially nice with the Tetris skin, which was originally built for Microsoft conference MIX09.
Read more about the process here. Grab the .NET and Silverlight source code here.
Carsonified @HelloApp
@HelloApp, which debuts at the Future of Web Apps – London 2009, lets conference-goers meet new people via Twitter. First you tag yourself during check-in, earn badges and points for meeting new people and completing certain tasks, and browse the seating chart according to professional background (design, development, PHP, Rails).
A perfect blend of socializing and tweeting at the same time. Read how Carsonified created it.
What’s your great idea?
Got a great conference idea already executed, or still brewing? The moral of the story here: don’t leave your geekiness behind when you go offline. Embrace it, because it makes things a hell of a lot more interesting.
Tumblr is no longer just the home of reblogged pictures, quotes, music, videos, and journal entries of friends you follow; it’s also gaining favor with the more discerning content creators in the design and technology circles, turning it into a truly professional publishing platform. This phenomenon is thanks to its relatively easy customization while keeping its interface decidedly simple.
My question is, if Tumblr’s audience is becoming more mature, should it shift from its dead-simple appeal and grow up too? David Yeiser prefers its current approach:
What’s neat about Tumblr is it’s not only a great publishing platform but a great tool for content consumption. [...] as self-publishing has changed to shorter forms and varied media the traditional feed reader has become obsolete. I shouldn’t have to click a title of a post to read a quote. [...] I think the way Tumblr aggregates and displays blog posts is the future of feed readers. Though I’m not aware of any standalone readers that take this approach.
Personally, I disagree. I follow a lot of people (and non-people) on Tumblr, producing remarkably varied content genres (e.g. XKCD Explained, 53 Weeks of UX, Sweet Home Style) with no way of filtering which ones I’d like to view at a time. Infinite scrolling in the dashboard can only take you so far in browsing ease.
Unwieldy content consumption is a familiar problem experienced on Twitter and Facebook, and by people who want more options, more control. Except there are now methods of dealing them on those sites. It’s even a big business for third party companies. On Tumblr, that remains to be seen.
Dashboard filtering options would be a welcome addition to the site. The reason is that “following” is a one-size-fits-all option when the truth is we need many.
And there lies the rub with a hosted platform, as well as platform that caters to simplicity first and foremost. Notice that as the concept of feed reading, trackbacking, and commenting are abstracted, if not replaced with Tumblr’s own conventions of dashboard reading, reblogging, liking, answering, one is forced to adhere to a closed set of standards inside its community. For a community that’s got such a wealth of content, consuming and sharing and communicating through that content but with limiting, non-standard methods is a turn off. If I link to a Tumblr post from a non-Tumblr site, will the owner of that tumblelog even know that I did?
Again, all of this wouldn’t be so bad if there were more options available, even as premium features. Right now, there aren’t.
What should Tumblr do? Should it go the WordPress.org and Identi.ca route and provide an open, self-hosted platform? Should it take some notes from the old-but-still-strong LiveJournal? (In some ways their user bases are the same.) Should it push its API more aggressively? Should we just wait and see what they’re up to, or accept that it’s really just a different culture from what we’re accustomed to?
As someone who’s enjoyed a lot of great content on Tumblr and is tempted to migrate her personal blog over there, there are a glaring number of things holding me back.
Blackbird Pie is Twitter’s very own tool for embedding tweets on webpages without the cumbersome, semantics-killing screenshot method. It still lacks the dead-simple interface Twitter is notorious for, since you have to enter the URL of the tweet to grab the embed code and it’s not even built into the system yet, but that’s because it’s a rough prototype at this point.
Since Twitter is an ecosystem of early adopters, it didn’t take long before a bookmarklet surfaced, which sports only a minor difference with the original code in the date format, and seems to display better on this site.
Note that this method inherits your websites styles, which means you may or may not have to tweak your CSS to accommodate it. Unfortunately it still looks bad in feed readers.
Has progress been achieved here?
I’m not sure this is any better than a screenshot. Putting aside the long-winded user flow of grabbing the code since that can be remedied once it’s built into the Twitter system, there’s an overflowing amount of inline CSS to copy and paste. The advantage to this static code, however, instead of a JavaScript embed is that the text is preserved even when the tweet is deleted.
The question remains: should people go through all this trouble to use tweets as quotes? Is there really that much more to be gained by preserving the tweet “format” over a simple blockquote? I still don’t think so.
Amidst all the exciting and controversial new directions Twitter is taking since they’ve been announced at the Chirp conference, one stands out: Ev Williams admitting that “Twitter is too hard too use”, even mentioning that the phrase “I don’t get Twitter” is the second suggested search in Google.
After all these years of the pundits identifying Twitter’s strength and eureka moment to be its simplicity, Ev’s statement says a lot about the company. They could have skipped over this detail or worded it in some other way, but talked about it anyway. Sincerely and transparently.
We’ve known this for a long time, but it was growing too fast for us to address these issues.
There are several lessons rolled in here. Despite all of Twitter’s growth in usage and features, they still don’t want to drop the ball on simplicity even if other products probably would have, because they can afford to.
But simplicity doesn’t only mean keeping the number of features at a minimum; it also means being intelligent enough to anticipate what users need. The way Twitter is built makes it into “different things for different people”—hence the explosion of 3rd-party apps and the creation of its own jargon. Retweeting, hashtags, trending topics, recommended users, and lists were all created arbitrarily by the community later on integrated as real features. Now the company is pushing further in location awareness, mobile, infrastructure, and APIs.
As long as there’s this open dialogue among the founders, the users, and all the developers, Twitter will remain as inspiring and innovative as ever.
Dribbble is a finely crafted community for designers, by designers. It’s invite-only in order to maintain high quality work on the site, but that doesn’t mean you can’t browse around for inspiration. Give it enough time to fine-tune the tagging and search features (color search is already there; UI patterns, textures, etc. would be great) and we may have the most useful, A-grade design reference out there from people who know their stuff.
There are several things that set it apart from generic portfolio and gallery sites, as it is also dubbed the “Twitter for designers”. From the tagline “what are you working on?” to its system of “rebounds” (basically a response to a “shot”) to uploads of 400 pixels or less, Dribbble is focused on brevity and the right now even when they could have entertained the whole spectrum.
Of course there’s the basketball metaphor working all around too, which when expanded even further can create some interesting activities and interactions for the community: think games, collaborations, meetups, leagues, merits. Think social games like Foursquare and BarStar, only more productive.
People have been complaining about the quality of a lot of things in the design community lately, whether it’s resource articles or the actual interactions within the community, and I see Dribbble as a partial solution to that.
*/
