Final update: Missing annotation responses never appeared.
No single bookmarked page ever got over 200 annotations. Is 200 a limit for annotations + responses per page?
This seems like a bug and it seems like it would be easily reproducible for testing:
Have 2-3 people annotate the same Web page. Invite them all to a group. Have them share their annotations for that same page with the group. Then have them write responses to other members' annotations. See if the total number can go above 200 without losing annotation responses.
If the above clears testing just fine, add this wrinkle: Do the same for multiple groups who are all annotating and responding to the same Web page. One member (i.e. the teacher) is in ALL groups and shares his annotations with each of the multiple groups. Perhaps the bug surfaces when one member is in multiple groups and is writing annotation responses to multiple groups on the same Web page (however, more than just my comments were lost--students' responses disappeared too).
The usage pattern I describe above is exactly what we're looking for in terms of using technology in high school English classrooms. Please investigate and resolve the situation so that we can use your site in our lessons!
Comparing status reports, in the toolbar of Diigolet, with end results: proposed tests
Test 001
To help troubleshoot, maybe you and a few willing volunteers could:
* work with a single bookmark
* add not too many annotations (for the purposes of this test, maybe fewer than one hundred annotations in total)
* add your few annotations in 'bursts' (aiming to all communicate with the server at or around the same moment)
* after each addition: each user should ensure that the toolbar of Diigolet has progressed to its 'Welcome {username}' state.
Test 002
If the results of the first test are good: then perform an extremely rushed test, bursts in rapid succession without pausing, aiming to deliberately ignore the status of the toolbar of Diigolet. I would hope that loss arises only if the user attempts to add something before the server has finished handling a previous request.
No single bookmarked page ever got over 200 annotations. Is 200 a limit for annotations + responses per page?
This seems like a bug and it seems like it would be easily reproducible for testing:
Have 2-3 people annotate the same Web page.
Invite them all to a group.
Have them share their annotations for that same page with the group.
Then have them write responses to other members' annotations.
See if the total number can go above 200 without losing annotation responses.
If the above clears testing just fine, add this wrinkle: Do the same for multiple groups who are all annotating and responding to the same Web page. One member (i.e. the teacher) is in ALL groups and shares his annotations with each of the multiple groups. Perhaps the bug surfaces when one member is in multiple groups and is writing annotation responses to multiple groups on the same Web page (however, more than just my comments were lost--students' responses disappeared too).
The usage pattern I describe above is exactly what we're looking for in terms of using technology in high school English classrooms. Please investigate and resolve the situation so that we can use your site in our lessons!
PS: Added it to the Roundup list
I'm not very familiar with behaviours of locally installed versions of Diigo.
> using MacOS X 10.5.x, the latest diigolet widget on Firefox 3.0.x or Safari 3.1.x.
Hint: acquaint yourselves with what's shown in the toolbar of Diigolet whilst there's communication with Diigo services. http://groups.diigo.com/group/Diigo_HQ/content/1399333
Comparing status reports, in the toolbar of Diigolet, with end results: proposed tests
Test 001
To help troubleshoot, maybe you and a few willing volunteers could:
* work with a single bookmark
* add not too many annotations (for the purposes of this test, maybe fewer than one hundred annotations in total)
* add your few annotations in 'bursts' (aiming to all communicate with the server at or around the same moment)
* after each addition: each user should ensure that the toolbar of Diigolet has progressed to its 'Welcome {username}' state.
Test 002
If the results of the first test are good: then perform an extremely rushed test, bursts in rapid succession without pausing, aiming to deliberately ignore the status of the toolbar of Diigolet.
I would hope that loss arises only if the user attempts to add something before the server has finished handling a previous request.
Postscript
For test 001, feel free to join the sandpit then use
http://groups.diigo.com/group/sandpit/content/1399974.