I think this is a brilliant illustration of the "wear marks" around a basic service. At its core, it's still 140 chars, but each of these subtle deviations represents a bend in the direction of features valuable to users.
Developers and designers can benefit from this by not overspecifying how a technology is to be used until loads of feedback has returned. Kind of like the old story about the architect who didn't fill in the sidewalks until students had worn paths into the campus lawn :)