11–19 of 19 posts
Here is an excerpt from Twitter's branding guidelines:
Don't:
* Use Twitter in the name of your website, application or product.
* Register a domain containing twitter, misspellings, transliterations or similar variations thereof.I'm a bit concerned about the name of your project... Here is an excerpt from Twitter's branding guidelines: Don't: * Use Twitter in the name of your website, application or product. * Register a domain containing twitter, misspellings, transliterations or similar variations thereof.
I'm a bit concerned about the name of your project... Here is an excerpt from Twitter's branding guidelines: Don't: * Use Twitter in the name of your website, application or product. * Register a domain containing twitter, misspellings, transliterations or similar variations thereof.
I'm a bit concerned about the name of your project... Here is an excerpt from Twitter's branding guidelines: Don't: * Use Twitter in the name of your website, application or product. * Register a domain containing twitter, misspellings, transliterations or similar variations thereof.
Those are guidelines, not rules. They can't do anything, unless they want to cut off his API access.
I'm a bit concerned about the name of your project... Here is an excerpt from Twitter's branding guidelines: Don't: * Use Twitter in the name of your website, application or product. * Register a domain containing twitter, misspellings, transliterations or similar variations thereof.
Those are guidelines, not rules. They can't do anything, unless they want to cut off his API access.
Thoughts/suggestions:
• I expected there to be a rollback option, perhaps via the '-' button. (Didn't expect to have sticky varying faster-than-realtime rates instead.)
• A slider/timeline-scrubber would probably be ideal, with indicator ticks everywhere there's an upcoming tweet. Then you can either 'play' real-time, and drag-'seek' to any interesting point forward or back, and fairly easily re-sync to an approximate minute after out-of-band DVR ops. (Also, 'next'/'prev' buttons would be more natural accelerated navigation to me, rather than the steppable-FF-rate.)
• Would benefit from explicit 'permalink'/sharing-of-well-crafted-range-query support. Such permalinks could be decorated with more contextual metadata (eg: name of program).
• Does Hulu work in a frame? (Or more generally: permalink metadata mentioned above could include recommended links to legitimate playback sources.)
• You might let people layer in their own lagged tweets by assisting them in using a hashtag offset convention. For example, "#lizanddick #11-25t0h8m blah blah blah".
There were a few startups attempting to enable synchronous group TV-event watching in past years... but I suspect they all suffered from the rise of DVRs among exactly their online-immersed target audience. Leveraging Twitter and allowing a blend of synchrony or asynchrony might work better.
Good luck!
Cool project. The sample you have makes it easy to see the uses. It would be cool if people could submit "fun" or good examples of great timelines. I think that would bring the social aspect into the project. Most people won't have the time to put together the criteria to produce the "query" so having a set of samples would be helpful in gaining traction