[Design] Twitter in Chandler?

[Mimi Yin]

Hi Reid,

Feeds *could* be collections. For example, it sounds like your  
examples of subscribing to your son's school calendars (which are  
feeds?) would be collections you'd want in your sidebar because their  
content is highly relevant to your day-to-day life.

The Twitter mock-up is more about *ambient* information. Stuff that  
you subscribe to that you could or couldn't pay attention to.  
Information that you would *NOT* feel obliged to "catch-up" on if you  
went away on vacation for 2 weeks.

One analogy that comes to mind is the difference between when someone  
turns on the TV or radio just to have 'background' noise on in the  
morning as they get ready for work in the morning versus sitting down  
to watch a movie or listen to a particular show.

I think there needs to be a similar sort of division in a personal  
information manager. The 'floating palette UI' is a way of creating  
tiers of information that help people keep 'background noise', in the  
background, the periphery, without overwhelming the sacred territory  
of "critical path information" you work with all the time.

The mock-up I put together is essentially for the 'background noise'.

$$$ Add to wiki spec

Mimi

On Oct 23, 2007, at 10:55 AM, Reid Ellis wrote:

> Maybe I'm just not understanding something. Why can't each feed be  
> a collection?
>
> If you want to see multiple feeds, just click on them or pin them.
>
> One thing this immediately brings to mind is grouping collections,  
> which allows the user to switch to viewing the group by clicking in  
> one place. Having a filter on items to only show "unread" ones  
> would be useful, too.
>
> Reid
>
> On Oct 19, 2007, at 18:14, bear wrote:
>> Mimi Yin wrote:
>>> Morgen demo'd a Twitter parcel at the staff meeting today (sorry  
>>> to steal your thunder Morgen) which set off all kinds of  
>>> flammables in my head.
>>> In our interview with Robert Scoble, Scoble spoke about sitting  
>>> in Chandler and swimming in a sea of twitters, feeds, news  
>>> tickers etc. Morgen took the first steps towards realizing that  
>>> vision. I'm picking up where he left off with a sketchy mock-up  
>>> of what the user experience might be like. See wiki page for  
>>> screenshot.
>>> http://chandlerproject.org/Notes/TwitterHalfbaked
>>> *Note* This is not only a proposal for a Twitter extension, but  
>>> is intended to provide space in the UI for *ambient information*,  
>>> as in information people soak up, stuff that doesn't necessarily  
>>> require your full attention, but instead floats around you like  
>>> elevator music. Different people will define *ambient* in  
>>> different ways. The design list is at the core of of the work I  
>>> do, but is probably ambient information for most list  
>>> subscribers. Examples of sources of *ambient* information  
>>> include: Twitter, Facebook status, News tickers, RSS feeds,  
>>> mailing lists, etc.
>>> + Floating palette where all the twits come in
>>> + It'd be nice if it weren't just twits, but feeds of all shapes  
>>> and sizes (in the fullness of time as we like to say)
>>> + A drop-down at the top where I can choose to either:
>>> - View all feeds (I know feeds is the wrong word, but don't have  
>>> a better one right now.)
>>> - View a single feed
>>> - Add a feed
>>
>> While being able to view a single feed or all may be good for  
>> debugging, what I really want is for all of the incoming messages  
>> to be tagged and just available so I can aggregate them indirectly  
>> when I view a contact or view a topic or anything else that  
>> happens to "lump" the data.
>>
>>> + Twits / feed things scroll by, not sure if we need to archive  
>>> these things? We would need separate UI for that.
>>
>> archiving +1
>>
>>> + If one of the ambient items is just a headline for a longer  
>>> blog post / article, then clicking on it will take you to the  
>>> article in a browser.
>>
>> what method of linking in Chandler allows for an abstract/headline/ 
>> title to link to another longer item?  or would the ambient item's  
>> content just auto-magically become the title of the longer item's  
>> body in Chandler?
>>
>>> + At the bottom is an entry box to submit your own twit.
>>
>> what method of linking in Chandler allows for an abstract/headline/ 
>> title to link to another longer item?  or would the ambient item's  
>> content just auto-magically become the title of the longer item's  
>> body in Chandler?
>>
>>> *Now here's the killer feature:*
>>> + Drag and drop individual twits into the main Chandler window so  
>>> you can stamp it as a task, add it to the calendar etc.
>>> + I imagine that some feeds actually contain valid .ics files, so  
>>> those should get parsed as events automagically, if dragged into  
>>> the main window.
>>
>> with twitter items they may contain links to more info but one of  
>> the features of jaiku or pownce is that the meta data comes along  
>> with the post.  For example, pownce supports events, files along  
>> with posts.
>>
>>> *Things to Consider*
>>> + Do we want to have a twit/feed palette per collection?
>>> + Do we want to give users a way to specify where they'd like to  
>>> send their twit? Twitter v. Pounce v. Facebook v. MySpace?, etc.
>>> + Haven't figured out a way to integrate the 'timeline/calendar'  
>>> view that Morgen demo'd. But it was a very cool way to browse  
>>> one's twitter archive.
>>
>> I would imagine that a quick entry plugin would have a default set  
>> of targets for outbound postings - and if someone wants to send a  
>> specific item drag-n-drop or right-click to get a dialog.
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design