Why does automatic authentication require a custom browser? Client certificates work well for this function in ordinary web applications (assuming a properly configured server).
As to collaborative browsing, that use case should be balanced against all the available applications that having a standard Firefox enables painlessly. Where is a user story of collaborative browsing (as contrasted to a shared bookmark repository) documented? On Mon, Jul 7, 2008 at 3:10 PM, Martin Langhoff <[EMAIL PROTECTED]> wrote: > On Mon, Jul 7, 2008 at 6:56 PM, C. Scott Ananian <[EMAIL PROTECTED]> > wrote: > > I'd rather see us just give up on Browse and ship and appropriately > > configured Firefox. I just can't see OLPC devoting enough developer > > Not so fast! The XS deliverables need a custom browser on the XO for > reasons we were discussing last Thursday :-) > > If we want > > - automagic authentication with the XS > - collaborative browsing (which can get better than what we have) > > we need a custom, bespoke, forked, evil, lasers-on-sharkies-heads > browser. Call it Betty if you want, but we need it. > > > > > m > -- > [EMAIL PROTECTED] > [EMAIL PROTECTED] -- School Server Architect > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > _______________________________________________ > Devel mailing list > [EMAIL PROTECTED] > http://lists.laptop.org/listinfo/devel > -- Frisbeetarianism is the belief that when you die, your soul goes up on the roof and gets stuck -- George Carlin
_______________________________________________ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
