Skip to main content

Home/ Diigo Community/ Contents contributed and discussions participated by Ole C Brudvik

Contents contributed and discussions participated by Ole C Brudvik

Ole C  Brudvik

View Google Docs i Webslides - 19 views

googledocs webslides
started by Ole C Brudvik on 13 Nov 11 no follow-up yet
  • Ole C  Brudvik
     
    I have added a bookmark to a Google doc in a list that I would like to be viewable when played in webslides. But it says it does not support HTTPS connection. Anyway around this?
Wade Ren

Is the site slow for you? - 107 views

performance speed
  • Ole C  Brudvik
     
    I am located in Singapore now and Diigo have been much slower than usual during the last week or so, but right now its fast. My Bookmarks about same speed as Delicious right now. Previous days some of the pages/sections never load. Will let you know if it slows down again.

    Cheers
    Ole
  • Ole C  Brudvik
     
    Diigo is very slow from Singapore today.

    ping www.diigo.com -t (the ping replies never stops....)

    Reply from 216.237.113.34: bytes=32 time=241ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=210ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=238ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=238ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=239ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=241ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=216ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=223ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=239ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=243ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Request timed out.
    Reply from 216.237.113.34: bytes=32 time=228ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=241ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=223ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=223ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=241ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=216ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=226ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=228ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=224ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=281ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=239ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=239ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=248ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=240ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=216ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=226ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=223ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=216ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=215ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=216ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=228ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=216ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=228ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=216ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=240ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=238ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=227ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=216ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=206ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=227ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=216ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=223ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=190ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=216ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=224ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=439ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=248ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128


    Ole
  • Ole C  Brudvik
     
    Right now Diigo is fast again. Same as Del.icio.us. Except for (alpha):

    One section (Slides) is slow, and not does not load: Application error

    Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html

    This section is slow almost every day.

    One section (List->Play) does not load: Application error

    Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html

    The other pages are fast right now.

    Current Ping:

    I run Win Xp in Virtual Machine on Mac Os X and this is the ping from Win Xp pro:

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Administrator>ping www.diigo.com -t

    Pinging www.diigo.com [216.237.113.34] with 32 bytes of data:

    Reply from 216.237.113.34: bytes=32 time=248ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=240ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=228ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=247ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=226ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=238ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=241ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=223ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=224ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=224ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=227ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=248ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=245ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=227ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=224ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=223ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=225ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=239ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=238ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=224ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=226ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=239ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=243ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=225ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=245ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=238ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=244ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=243ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=245ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=241ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=224ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=224ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=238ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=241ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=242ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=227ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=246ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=239ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=253ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=547ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=248ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=224ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=226ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=248ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=244ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=226ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=251ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=243ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=54ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=243ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=229ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=227ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=238ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=238ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=242ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=217ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=225ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=223ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=247ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=228ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=240ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=246ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=237ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=223ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=228ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=251ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=235ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=242ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=225ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=223ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=236ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=256ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=242ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=225ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=231ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=232ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=256ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=220ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=239ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=238ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=245ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=242ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=226ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=226ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=219ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=221ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=242ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=239ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=234ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=233ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=238ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=230ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=222ms TTL=128
    Reply from 216.237.113.34: bytes=32 time=218ms TTL=128

    This is the Ping from Mac Os X:

    Ping has started ...

    PING www.diigo.com (216.237.113.34): 56 data bytes
    64 bytes from 216.237.113.34: icmp_seq=0 ttl=50 time=236.095 ms
    64 bytes from 216.237.113.34: icmp_seq=1 ttl=50 time=234.804 ms
    64 bytes from 216.237.113.34: icmp_seq=2 ttl=51 time=226.148 ms
    64 bytes from 216.237.113.34: icmp_seq=3 ttl=51 time=220.999 ms
    64 bytes from 216.237.113.34: icmp_seq=4 ttl=51 time=221.948 ms
    64 bytes from 216.237.113.34: icmp_seq=5 ttl=50 time=249.232 ms
    64 bytes from 216.237.113.34: icmp_seq=6 ttl=50 time=236.415 ms
    64 bytes from 216.237.113.34: icmp_seq=7 ttl=50 time=230.187 ms
    64 bytes from 216.237.113.34: icmp_seq=8 ttl=50 time=240.396 ms
    64 bytes from 216.237.113.34: icmp_seq=9 ttl=50 time=230.667 ms
    64 bytes from 216.237.113.34: icmp_seq=10 ttl=50 time=247.670 ms
    64 bytes from 216.237.113.34: icmp_seq=11 ttl=51 time=218.355 ms
    64 bytes from 216.237.113.34: icmp_seq=12 ttl=51 time=222.927 ms
    64 bytes from 216.237.113.34: icmp_seq=13 ttl=50 time=237.193 ms
    64 bytes from 216.237.113.34: icmp_seq=14 ttl=51 time=221.634 ms
    64 bytes from 216.237.113.34: icmp_seq=15 ttl=50 time=257.614 ms
    64 bytes from 216.237.113.34: icmp_seq=16 ttl=50 time=241.418 ms
    64 bytes from 216.237.113.34: icmp_seq=17 ttl=51 time=219.552 ms
    64 bytes from 216.237.113.34: icmp_seq=18 ttl=50 time=245.126 ms
    64 bytes from 216.237.113.34: icmp_seq=19 ttl=50 time=240.428 ms
    64 bytes from 216.237.113.34: icmp_seq=20 ttl=50 time=245.820 ms
    64 bytes from 216.237.113.34: icmp_seq=21 ttl=50 time=282.594 ms
    64 bytes from 216.237.113.34: icmp_seq=22 ttl=50 time=246.139 ms
    64 bytes from 216.237.113.34: icmp_seq=23 ttl=51 time=226.192 ms
    64 bytes from 216.237.113.34: icmp_seq=24 ttl=50 time=235.749 ms
    64 bytes from 216.237.113.34: icmp_seq=25 ttl=51 time=220.515 ms
    64 bytes from 216.237.113.34: icmp_seq=26 ttl=51 time=218.381 ms
    64 bytes from 216.237.113.34: icmp_seq=27 ttl=51 time=224.513 ms
    64 bytes from 216.237.113.34: icmp_seq=28 ttl=51 time=219.166 ms
    64 bytes from 216.237.113.34: icmp_seq=29 ttl=51 time=218.237 ms
    64 bytes from 216.237.113.34: icmp_seq=30 ttl=51 time=226.524 ms
    64 bytes from 216.237.113.34: icmp_seq=31 ttl=50 time=234.427 ms
    64 bytes from 216.237.113.34: icmp_seq=32 ttl=51 time=224.720 ms
    64 bytes from 216.237.113.34: icmp_seq=33 ttl=50 time=243.059 ms
    64 bytes from 216.237.113.34: icmp_seq=34 ttl=50 time=246.814 ms
    64 bytes from 216.237.113.34: icmp_seq=35 ttl=51 time=237.122 ms
    64 bytes from 216.237.113.34: icmp_seq=36 ttl=50 time=246.650 ms
    64 bytes from 216.237.113.34: icmp_seq=37 ttl=51 time=234.098 ms
    64 bytes from 216.237.113.34: icmp_seq=38 ttl=51 time=222.279 ms
    64 bytes from 216.237.113.34: icmp_seq=39 ttl=50 time=242.753 ms
    64 bytes from 216.237.113.34: icmp_seq=40 ttl=50 time=242.592 ms
    64 bytes from 216.237.113.34: icmp_seq=41 ttl=51 time=223.023 ms
    64 bytes from 216.237.113.34: icmp_seq=42 ttl=51 time=229.991 ms
    64 bytes from 216.237.113.34: icmp_seq=43 ttl=51 time=220.225 ms
    64 bytes from 216.237.113.34: icmp_seq=44 ttl=50 time=244.770 ms
    64 bytes from 216.237.113.34: icmp_seq=45 ttl=50 time=236.987 ms
    64 bytes from 216.237.113.34: icmp_seq=46 ttl=50 time=233.081 ms
    64 bytes from 216.237.113.34: icmp_seq=47 ttl=50 time=241.253 ms
    64 bytes from 216.237.113.34: icmp_seq=48 ttl=51 time=220.186 ms
    64 bytes from 216.237.113.34: icmp_seq=49 ttl=51 time=221.683 ms
    64 bytes from 216.237.113.34: icmp_seq=50 ttl=51 time=235.629 ms
    64 bytes from 216.237.113.34: icmp_seq=51 ttl=50 time=236.583 ms
    64 bytes from 216.237.113.34: icmp_seq=52 ttl=51 time=222.458 ms
    64 bytes from 216.237.113.34: icmp_seq=53 ttl=50 time=251.799 ms
    64 bytes from 216.237.113.34: icmp_seq=54 ttl=51 time=222.134 ms
    64 bytes from 216.237.113.34: icmp_seq=55 ttl=50 time=234.154 ms
    64 bytes from 216.237.113.34: icmp_seq=56 ttl=51 time=233.017 ms
    64 bytes from 216.237.113.34: icmp_seq=57 ttl=50 time=233.476 ms
    64 bytes from 216.237.113.34: icmp_seq=58 ttl=51 time=234.118 ms
    64 bytes from 216.237.113.34: icmp_seq=59 ttl=50 time=236.742 ms
    64 bytes from 216.237.113.34: icmp_seq=60 ttl=51 time=222.106 ms
    64 bytes from 216.237.113.34: icmp_seq=61 ttl=51 time=228.175 ms
    64 bytes from 216.237.113.34: icmp_seq=62 ttl=50 time=238.266 ms
    64 bytes from 216.237.113.34: icmp_seq=63 ttl=50 time=234.415 ms
    64 bytes from 216.237.113.34: icmp_seq=64 ttl=50 time=234.077 ms
    64 bytes from 216.237.113.34: icmp_seq=65 ttl=50 time=230.742 ms
    64 bytes from 216.237.113.34: icmp_seq=66 ttl=51 time=222.004 ms
    64 bytes from 216.237.113.34: icmp_seq=67 ttl=51 time=223.219 ms
    64 bytes from 216.237.113.34: icmp_seq=68 ttl=51 time=219.638 ms
    64 bytes from 216.237.113.34: icmp_seq=69 ttl=50 time=232.743 ms
    64 bytes from 216.237.113.34: icmp_seq=70 ttl=50 time=241.040 ms
    64 bytes from 216.237.113.34: icmp_seq=71 ttl=51 time=224.737 ms
    64 bytes from 216.237.113.34: icmp_seq=72 ttl=51 time=220.807 ms
    64 bytes from 216.237.113.34: icmp_seq=73 ttl=50 time=236.871 ms
    64 bytes from 216.237.113.34: icmp_seq=74 ttl=50 time=235.700 ms
    64 bytes from 216.237.113.34: icmp_seq=75 ttl=50 time=234.855 ms
    64 bytes from 216.237.113.34: icmp_seq=76 ttl=50 time=233.044 ms
    64 bytes from 216.237.113.34: icmp_seq=77 ttl=51 time=224.155 ms
    64 bytes from 216.237.113.34: icmp_seq=78 ttl=50 time=242.854 ms
    64 bytes from 216.237.113.34: icmp_seq=79 ttl=50 time=235.867 ms
    64 bytes from 216.237.113.34: icmp_seq=80 ttl=51 time=221.177 ms
    64 bytes from 216.237.113.34: icmp_seq=81 ttl=51 time=225.237 ms
    64 bytes from 216.237.113.34: icmp_seq=82 ttl=50 time=234.683 ms
    64 bytes from 216.237.113.34: icmp_seq=83 ttl=50 time=234.505 ms
    64 bytes from 216.237.113.34: icmp_seq=84 ttl=51 time=231.182 ms
    64 bytes from 216.237.113.34: icmp_seq=85 ttl=51 time=224.284 ms
    64 bytes from 216.237.113.34: icmp_seq=86 ttl=50 time=236.138 ms
    64 bytes from 216.237.113.34: icmp_seq=87 ttl=50 time=238.545 ms
    64 bytes from 216.237.113.34: icmp_seq=88 ttl=50 time=233.745 ms
    64 bytes from 216.237.113.34: icmp_seq=89 ttl=50 time=235.019 ms
    64 bytes from 216.237.113.34: icmp_seq=90 ttl=50 time=233.801 ms
    64 bytes from 216.237.113.34: icmp_seq=91 ttl=51 time=244.883 ms
    64 bytes from 216.237.113.34: icmp_seq=92 ttl=50 time=236.259 ms
    64 bytes from 216.237.113.34: icmp_seq=93 ttl=51 time=235.243 ms
    64 bytes from 216.237.113.34: icmp_seq=94 ttl=51 time=238.256 ms
    64 bytes from 216.237.113.34: icmp_seq=95 ttl=50 time=240.025 ms
    64 bytes from 216.237.113.34: icmp_seq=96 ttl=50 time=239.013 ms
    64 bytes from 216.237.113.34: icmp_seq=97 ttl=50 time=238.476 ms

    Cheers
    Ole
Ole C  Brudvik

Add Feed to a Group - 21 views

feature rss
started by Ole C Brudvik on 18 Jul 07 no follow-up yet
  • Ole C  Brudvik
     
    Hi,

    How about a feature that allows a Group to subscribe to Feeds. For example, Slides under the Forum in a Group.

    Cheers,

    Ole
Ole C  Brudvik

digital digs: the positive confluence of academia and the web - 5 views

  • Clearly one of the challenges academia faces is to figure out a productive use of networks in terms of research practices. Usually I write more about the teaching aspects of the university and clearly there are many ways universities will employ networks. But I want to think specifically about the use of the web for research with a few goals in mind: to enhance collaboration between academics to publish and share research to share knowledge with a broader audience (students, governments, industries, non-profits, the general public, and so on) One might say that these have been answered, but the real challenge is that as the web continues to evolve and now converge with other networks, the practices we have established need to change as well. That is, from the inception of the web, one could find the appearance of academic journals: genuine, rigorously reviewed, academic scholarship available freely online. There were (and are) listservs that might facilitate collaboration. Similarly individual faculty and faculty organizations built websites where they offered information, policy statements, and so on (NCTE or MLA for example in English Studies). But how are we moving forward?
  • Conventional academic discourse lies with journals and conferences. For all the advantages of these modes, neither offers an ongoing, dynamic interchange. Listservs offer that, but, in my experience anyway, they don't really create a productive, collaborative space. Sometimes there are debates on listservs; sometimes there is sharing of information (e.g. does anyone know a good article about x"?). But there isn't a sustained building of knowledge there. I suppose there could be, but there isn't, probably b/c we all go off to write our individually authored articles and conference presentations. In any case, the listserv is too large a community for collaborative work. Yes, tens of thousands contribute to Wikipedia, but they don't all work on the same article, right? So I don't know what the magic number is, but let's say I was looking for a dozen scholars in who were interested in the same things I'm interested in: mobile networks virtual worlds audio/video production public, collaborative learning It's unlikely that we would all work on the same research project at once, but there would be a handful of project undertaken by individuals or small groups. There would be a public face to the group and a private project management site, like Basecamp. The public face would offer a steady stream of information as we shared what we were doing, what was going on in our teaching, what we were reading and writing. We'd be assembling streams of information from our blogs, twitters, flickr, YouTube, and so on--wherever we were post information. The result is a collection of information that is hopefully useful groundwork for more formal investigation and also a mechanism for fruitful collaboration between our classes.
  • Meanwhile, in a more private space we might be orchestrating collaborative classroom projects and sharing research, drafts, and other media: constructing our scholarly work. When it's complete, we publish it in traditional venues and republish it on our public site as well.
Ole C  Brudvik

Museum 2.0: Hierarchy of Social Participation - 0 views

  • Level 4: Individual, Networked, Social Interaction with Content (Me to We with Museum) This is the level where web 2.0 sits. Individuals still do their interacting with the content singly, but their interactions are available for comment and connection by other users. And the architecture promotes these connections automatically. For example, on Netflix, when you rate a movie highly, you don’t just see how others have rated it; Netflix recommends other movies to you based on what like-minded viewers also rated highly. By networking the ratings, tags, or comments individuals place on content, individuals are linked to each other and form relationships around the content. A successful level 4 experience uses social interaction to enhance the individual experience; it gets better the more people use it. The social component is a natural extension of the individual actions. Which means, perhaps, users are ready for…
  • As always, comments are encouraged—and in this case, strongly desired as I work on refining this content for the article.
  • using web 2.0 to promote civic discourse in museums, I’m developing an argument about the “hierarchy of social participation.” I believe that, as with basic human needs, experience design in museums (and for other content platforms) can occur on many levels, and that it is hard to achieve the highest level without satisfying, or at least understanding, those that come before it. One of the impediments to discourse in museums is that fact that designers want to jump straight from individuals interacting with content to interacting with each other. It’s a tall order to get strangers to talk to each other, let alone have a meaningful discussion. And so, I offer the following hierarchy of social participation.
  • ...2 more annotations...
  • Level 5: Collective Social Interaction with Content (We in Museum) This is the holy grail of social discourse, where people interact directly with each other around content. Personal discussions, healthy web bulletin boards and list-servs fall in this category. Healthy level 5 experiences promote respect among users, encourage community development, and support interaction beyond the scope of the content.
  • So how do we level up? The good news is that moving up the levels does not require new content. At all levels, the interaction and participation can occur around pre-existing content. A lot of museums top out at level 2 or 3, imagining that offering people heightened opportunities to interact with content, or to create their own content, is enough. Granted, I’m not sure if social engagement is the goal for interactive designers. But with side benefits like deeper connection with the content, greater appreciation for the museum as a social venue, and heightened awareness of other visitors, it deserves a place at the drafting table.
Hilary Reynolds

Citations - 149 views

citations biblio
  • Ole C  Brudvik
     
    APA style for electronic references:

    http://www.apastyle.org/elecsource.html

    Ole
  • Ole C  Brudvik
     
    One issue would be who is the author?

    "The status of the author in the postmodern world is an uncertain one. Though it seems self-evident that each of us has our own meanings to express, there are those, most notably French semiotician Roland Barthes, who take the notion of authorship to be a mere chimera. Barthes (1977) famously argued that if there ever were such a thing as an author, s/he is presumed "dead." Barthes writes, "a text is not a line of words releasing a single theological meaning (the 'message' of the Author-God) but a multidimensional space in which a variety of writings, none of them original, blend and clash" (p. 146). The defining characteristic of Barthes' (nonexistent) author is the ability to conceive and express original ideas. He does not say that we cannot write, simply that we cannot write anything that is unique to ourselves."
    (http://www.diigo.com/user/olebrudvik/multimodality+literacy+meaning-making?tab=253 , 2006, Annotation 5, from Nelson, 2005. Retrieved May 7, 2007).

    This highlight above i have not written any sticky notes or comment to it. I have selectively chosen 5-6 highlights from the article. But who is the author? Both, none, Nelson, me?? Did i do what Barthes says and wrote a text that is not unique to myself but its my text? Or did i simply plagiarise. If i add a comment or sticky notes to this one how then?

    References:

    http://www.diigo.com/user/olebrudvik/multimodality+literacy+meaning-making?tab=253 (2006), Annotation 5 from Nelson, 2005. Retrieved May 7, 2007.

    or

    OleBrudvik (2006). Annotation 5, from Nelson 2005. Retrieved May 7, 2007 from Diigo at http://www.diigo.com/user/olebrudvik/multimodality+literacy+meaning-making?tab=253.



    Another issue is the Avatar names we use, with the big thing with second life i think it is getting towards ok to use Avatar names. I used one in a journal article and have not been punished for it yet, all though article still in revision.

    Cheers
    Ole
  • Ole C  Brudvik
     
    I use www.Zotero.org , if i import a bookmark from Diigo and choose Forum Post as the type, it gives me this (APA):

    My Bookmarks tagged multimodality literacy meaning-making. Retrieved May 6, 2007, from http://www.diigo.com/user/olebrudvik/multimodality+literacy+meaning-making?tab=253.

    Zotero dont have one for Annotation but maybe....Diigo + Zotero....

    Cheers
    Ole
Ole C  Brudvik

Increase size of the Tags field in forum? - 30 views

forum tag
  • Ole C  Brudvik
     
    Hi,

    The "Tags:" field in the forum topic form seems to be set to max. 60 characters. Can you increase it?

    Would it be possible to add tags to individual replies in a topic in the forum?

    Cheers
    Ole
  • Ole C  Brudvik
     
    Hi Maggie,

    Yes agree with you, the Group is collaborative space so excessive tagging might not be desired. I use the Group feature privately now I am doing a literature review using Groups with Forum, So I am making use of the tags for such things as themes, concepts and other relevant tags. Some of the content comes from websites using the bookmarking with tags and some from books or PDF that I can not bookmark & annotate, I use the forum for those. I import the resources into Endnote citation software. I am interested in how the tagging and Groups can be utilized for such a purpose to using MS Word. So i run out of space for tags sometimes and it would maybe be useful to be able to assign an additional tag or two to replies. So just exploring...

    Cheers
    Ole


    maggie_diigo wrote:
    > Hi Ole,
    >
    > > The "Tags:" field in the forum topic form seems to be set to max. 60 characters. Can you increase it?
    >
    > I suppose that can be easily done. While tagging is quite useful, personally I'm not crazy about excessive tagging. Because everyone's tagging style and preference is quite different, as the group forum host, I'd like to keep the incoming tags "manageable" especially in a "group env't". So I sometimes do some editing to apply some consistency in the group forum tagging.
    >
    > In this particular post, for example, the original tags are "forumtopic, tags, topicreplies" -- > some tags are fairly unique and likely not used by the majority of group members, so I changed them to "forum, tags"
    >
    > Welcome others' input on this.
    >
    >
    > > Would it be possible to add tags to individual replies in a topic in the forum?
    >
    > Anything is possible, but this requires extra effort. Is this feature very needed, or just nice-to-have, and only helpful occasionally?
  • Ole C  Brudvik
     
    No strong need.

    Cheers
    Ole
    maggie_diigo wrote:
    > Hi Ole,
    >
    > Sounds like a very interesting research. After publishing it, please share with all of us. Love to learn more.
    >
    > Q: do you really have a strong need to increase the tag field size?
    >
    > cheers,
    >
    > Maggie
Joy Huang

Adding Suggested Tags - 56 views

feature tag suggestion suggestions suggest suggested recommended recommend recommendation recommendations Post to Diigo
started by Joy Huang on 19 Apr 07 no follow-up yet
  • Ole C  Brudvik
     
    Working with ontologies and folksonomies:

    There are several people working in this area: Patrick Schmitz has presented research into a
    model that works with both folksonomies and ontologies by leveraging statistical natural
    language processing. His goal is to develop a system that retains the flexibility of free tagging
    for annotation but make uses of ontology in the search and browse interface (Schmitz, 2006).
    Another proposal, from Dave Beckett (2006), is to make more use of the social context within which tags are created by separating the tool that creates the tags from the tool with which
    they are used. He also proposes that wiki pages should be created for individual tags which
    users could then add to/edit so that the wiki page, in effect, becomes the tag. The on-going
    process of refinement for each separate tag would form a kind of consensus as to the meaning
    of that tag and would also record the processes (the semantic path) by which the end result is
    being reached. This would, to take just one simple example, allow direct links to other
    language versions of the same tag.

    In terms of bookmarking services such as Del.icio.us and the open source SiteBar
    (www.sitebar.org), one of the key problems is how best to classify the growing list of URLs.
    At the WWW2006 conference in Edinburgh, Dominic Benz et al, from the University of
    Freiburg, put forward an idea for automatically classifying bookmarks. The authors proposed
    an automated system which takes account of how the user has classified bookmarks in the
    past and how other people with similar interests have also classified their bookmarks. In other
    words find a similar user who has already classified and stored a bookmark and derive a
    recommendation based on what they did.


    Seely Brown's book The Social Life of Information makes a powerful case for taking account and
    care of the social context in which information exists

    See: http://www.informatik.uni-freiburg.de/cgnm/software/caribo/index_en.html
Ole C  Brudvik

Search Diigolet - 20 views

diigolet search highlight keyword suggestion
started by Ole C Brudvik on 18 Apr 07 no follow-up yet
  • Ole C  Brudvik
     
    Hi,

    I have started to use the Diigolet with Safari on Mac. It works very nice, but I miss the customized search feature and the option to highlight your search keywords on the web page. Are you planning to put these features on the Diigolet?

    Cheers
    Ole
Ole C  Brudvik

T H E H O R I Z O N R E P O RT - 0 views

  • THe New sCHoLarsHiP aNd eMerGiNG forMs of PubLiCaTioN Time-to-adoption Horizon: four to five Years The time-honored activities of academic research and scholarly activity have benefited from the explosion of access to research materials and the ability to collaborate at a distance. At the same time, the processes of research, review, publication, and tenure are challenged by the same trends. The proliferation of audience- generated content combined with open-access content models is changing the way we think about scholarship and publication—and the way these activities are conducted
  • Increasingly, scholars are beginning to employ methods unavailable to their counterparts of several years ago, including prepublication releases of their work, distribution through nontraditional channels, dynamic visualization of data and results, and new ways to conduct peer reviews using online collaboration.
  • New forms of scholarship, including fresh models of publication and nontraditional scholarly products, are evolving along with the changing process. Some of these forms are very common—blogs and video clips, for instance—but academia has been slow to recognize and accept them. Some scholars worry that blogging may cut into time that would otherwise be used for scholarly research or writing, for example, or that material in a podcast is not as well researched as material prepared for print publication. Proponents of these new forms argue that they serve a different purpose than traditional writing and research—a purpose that improves, rather than runs counter to, other kinds of scholarly work. Blogging scholars report that the forum for airing ideas and receiving comments from their colleagues helps them to hone their thinking and explore avenues they might otherwise have overlooked.
  • ...2 more annotations...
  • While significant challenges remain before the emerging forms of scholarship we are seeing are accepted, nonetheless, there are many examples of work that is expanding the boundaries of what we have traditionally thought of as scholarship. In the coming years, as more scholars and researchers make original and worthwhile contributions to their fields using these new forms, methods for evaluating and recognizing those contributions will be developed, and we expect to see them become an accepted form of academic work.
  • examples of the New scholarship and emerging forms of Publication The following links provide examples of the new scholarship and emerging forms of publication.
Ole C  Brudvik

Adding Suggested Tags - feature,tag - Diigo Community | Diigo Group Forum - 1 views

shared by Ole C Brudvik on 22 Apr 07 - Cached
  • Another proposal, from Dave Beckett (2006), is to make more use of the social context within which tags are created by separating the tool that creates the tags from the tool with which they are used. He also proposes that wiki pages should be created for individual tags which users could then add to/edit so that the wiki page, in effect, becomes the tag. The on-going process of refinement for each separate tag would form a kind of consensus as to the meaning of that tag and would also record the processes (the semantic path) by which the end result is being reached. This would, to take just one simple example, allow direct links to other language versions of the same tag.
    • Ole C  Brudvik
       
      I like something like this. On a webpage one clip is relevant for one user, another clip on the same webpage relevant for another user. There are more than one way to interpret a clip thus a clip as a object the more tags attached to it the more possible meanings it can have, and in different contexts.
1 - 12 of 12
Showing 20 items per page