Good idea.
On Wed, Dec 23, 2009 at 11:19 AM, Anne Kathrine Petterøe <[email protected]> wrote: > We could go to the results, like twitter does it today or their home page. > But I think we should just create a tag cloud without links for now, just to > make it all go a bit faster. > We can always go back and make changes later. What do you think? > > On 23. des. 2009, at 09.48, Richard Hirsch wrote: > >> What happens when user clicks on the tag cloud? Or is the tag cloud >> created without links? >> >> On Wed, Dec 23, 2009 at 9:32 AM, Anne Kathrine Petterøe >> <[email protected]> wrote: >>> Why don't we change it so that the opening page displays the tag cloud >>> instead? >>> >>> >>> On 23. des. 2009, at 08.33, Richard Hirsch wrote: >>> >>>> The idea is that the display on the opening page is from the public >>>> timeline and is read-only. It is only used for users to see that there >>>> is activity on the platform. >>>> >>>> On Wed, Dec 23, 2009 at 6:40 AM, Vassil Dichev <[email protected]> wrote: >>>>>> My new changes are in the branch. The first challenge is to get the >>>>>> first page working with the public timeline. We have to add a comet >>>>>> back-end that feeds just one message instead of 40 (which is the >>>>>> existing implementation) and then map the existing javascript >>>>>> (display_messages.js) to the new ids or change the new ui to match the >>>>>> ids in the existing javascript. >>>>> >>>>> Wait, I thought we decided against sending just one message for now, >>>>> because of many limitations of this approach. For instance, if you >>>>> reply to a message, the old message will become a part of a >>>>> conversation, but will not have an updated conversation link. >>>>> >>> >>> > >
