Hello iPad user! You should definitelydownload and try our free iPad app!

Published (M)
by
Sun, Oct 09 2011 17:35:46

Twitter Debate on Product Design

  1. sparker
    The need for link shortening is idiotic, @jack -- links should be meta-data attachments to each tweet, not part of 140 char limit
    sparker
    Fri, Oct 07 2011 20:11:15
    0 likes
     · 
    0 comments

  2. Sean's initial tweet setup the argument, and began from a problem he experienced. Constraining one's thoughts to 140 characters is hard enough, but having to constrain it even farther to include a 10-12 character shortlink?


    Now that the initial problem has been identified and a proposed solution has been laid out, responses start coming in.

  3. sacca
    @sparker @jack That'll work when the metadata are supported across every platform on which Tweets are consumed. Until then, clicks pervade.
    sacca
    Fri, Oct 07 2011 20:31:15
    0 likes
     · 
    0 comments
  4. shervin
    @sparker @jack Agree. Links aren't human expression. They're only metadata for further contextual data. Arbitrarily limits human expression.
    shervin
    Fri, Oct 07 2011 20:36:33
    0 likes
     · 
    0 comments
  5. sacca
    @shervin @sparker @jack Links are absolutely an expression. They refer to anything. And because Twitter is open, metadata doesn't solve it.
    sacca
    Fri, Oct 07 2011 21:10:41
    0 likes
     · 
    0 comments
  6. sacca
    @shervin @sparker @jack FB owns both ends of it's consumption experience. So it can encode whatever it wants and decode on the other end.
    sacca
    Fri, Oct 07 2011 21:11:30
    0 likes
     · 
    0 comments
  7. shervin
    @sacca @sparker @jack To me, the expression lies in the content that the link contains not in the link itself. There's a difference.
    shervin
    Sat, Oct 08 2011 02:39:45
    0 likes
     · 
    0 comments
  8. sacca
    @shervin @sparker @jack But the openness of Twitter, and it's accesibility across the web and on SMS, requires a lowest com/denom protocol.
    sacca
    Fri, Oct 07 2011 21:14:12
    0 likes
     · 
    0 comments
  9. sparker
    @calebelston good pt, though less and less impt given native client adoption + exp for legacy SMS could gracefully degrade to multiple txts
    sparker
    Fri, Oct 07 2011 20:20:42
    0 likes
     · 
    0 comments
  10. alexroche
    @rycaut @sampullara I do too, but there's no reason why they're can't be both rich metadata and "basic" tweets for SMS or older clients
    alexroche
    Fri, Oct 07 2011 22:08:50
    0 likes
     · 
    0 comments
  11. sparker
    @falameufilho @jack re SMS where a product begins should not dictate where it ends up, products evolve beyond original constraints
    sparker
    Fri, Oct 07 2011 22:42:04
    0 likes
     · 
    0 comments
  12. erickschonfeld
    @sacca @shervin @sparker @jack SMS is keeping us down
    erickschonfeld
    Fri, Oct 07 2011 22:03:15
    0 likes
     · 
    0 comments
  13. sparker
    @tolles better user exp to have all links (video,photo,etc) turned into objects and represented functionally, we did it with "share" at fb
    sparker
    Fri, Oct 07 2011 20:42:38
    0 likes
     · 
    0 comments
  14. sacca
    @alexroche @shervin @sparker @jack There isn't an open ecosystem of FB clients? Closed makes it easier. Standards/terms are harder.
    sacca
    Fri, Oct 07 2011 21:22:20
    0 likes
     · 
    0 comments
  15. sparker
    @sacca @alexroche @shervin @jack totally agree re open vs. closed, it's a deliberate decision, i choose good prod over open, Apple approach
    sparker
    Fri, Oct 07 2011 21:23:57
    0 likes
     · 
    0 comments
  16. alexroche
    @alexroche @sacca @shervin @sparker @jack also quite ironic that I'm having to shorten english words like a 13 yr old bc replies r'nt mtadta
    alexroche
    Fri, Oct 07 2011 21:21:21
    0 likes
     · 
    0 comments

Did you find this story interesting? Be the first to or comment.

Liked!
Total views
390

Are you sure?

Are you sure you want to delete this story?

Feature story