Diigo's page caching feature apparently hasn't been working at all since Nov 17 (those pages cached earlier than that day are all kept accessible, though). I wonder if this is occuring only to me.
This really is a serious problem. I have spent a long time looking at all the social BM'ing options, if everything were working, you have a very strong service.
But, everything does not work. One of the most important features, caching, has been broken for going on two months, with no indication of when it might be fixed. A full text search for "internet" across all member's bookmarks, unbelievably, returns zero results.
Why are you developing v3 beta when v2 is still in beta (but given the above it feels more like alpha). You are asking users to make a significant investment of their time by putting all their data on your site, but we as users must feel we can trust you with that data, or we won't bother. Allowing xml exports goes some way (but even this doesn't allow exporting the cached page). How many users are you turning away daily by breaking promises of certain features that they read about when signing up?
Your relatively low standing according to Alexa (which surprises me considering the features) amongst social BM'ing makes me worried about your future, all the more reason to allow proper export of data, to reduce my risk only to change over costs should you go bust, not data loss.
Should I continue to use your service? Are you a serious company?
Regards, Fullness
Edit: P.S. I just want to make it clear that I really, really want you to fix these problems. I wouldn't have bothered with such a long post if I didn't think you had a service with excellent potential.
lucite wrote: > maggie_diigo wrote: > >Don't worry. all pages will be cached soon. > > Any update on this - it's been over 1 month and it still doesn't seem like cache is working. > > Thanks
Hi fullness, I am sorry some features in V2 is not stable enough, that's why we are developing V3 which is much stable than V2. I checked my cache. It works fine on V3, but it doesn't work on V2. Don't worry, your data is safe. We will fix it soon. Please let me know if you want to try out the V3.
You guys rock. When the problem happened I started looking around at what other services/sites offered and I have to say that every time I thought: Diigo is better. Your interface and your features are just better. And I'm saying this as a die-hard Google user for other types of services. If I stick with Diigo over the benefits that Notebook integration has for me, it's really that I think your service is THAT much better!
I'd love to try v3 to see what else you've got in store for us :)
joel, > I checked my cache. It works fine on V3, but it doesn't work on V2. Don't worry, your data is safe. ...
No, it's NOT always safe. I have checked the cached pages of my own as well, and have found out that many of the pages I bookmarked during the late November through the early December were not cached as expected. Go to my page and try viewing the cache for http://www.asahi.com/paper/editorial20071121.html for example. It says "the requested page is no longer available", which clearly shows that THE SOURCE PAGE HAD EXPIRED BEFORE DIIGO RESTARTED CACHING. Sticky notes for such pages have nothing left to "stick" to; likewise, highlighted texts are nothing more than odrinary comments now that they aren't associated to any particular portions of the original document. Things will be nearly the same for those pages which were modified during the downtime.
I am not asking you to recover such info now, since I know it's too late for anyone to do that. I just want you to make clear when your system's caching feature went down and when it was recovered, and let all the users (including ones who haven't tried V3 yet) know that their bookmarks created within that period may have lost part of their info.
I would like to try v3 in that case. But before you do it - do I lose any data? Is there an option to change to v3 somewhere, and some more information?
Thanks, Fullness
joel wrote: > Hi fullness, > I am sorry some features in V2 is not stable enough, that's why we are developing V3 which is much stable than V2. > I checked my cache. It works fine on V3, but it doesn't work on V2. Don't worry, your data is safe. We will fix it soon. Please let me know if you want to try out the V3.
We're currently doing cache server /database migration in the backend for the next version. Don't worry. all pages will be cached soon.
>Don't worry. all pages will be cached soon.
Any update on this - it's been over 1 month and it still doesn't seem like cache is working.
Thanks
But, everything does not work. One of the most important features, caching, has been broken for going on two months, with no indication of when it might be fixed. A full text search for "internet" across all member's bookmarks, unbelievably, returns zero results.
Why are you developing v3 beta when v2 is still in beta (but given the above it feels more like alpha). You are asking users to make a significant investment of their time by putting all their data on your site, but we as users must feel we can trust you with that data, or we won't bother. Allowing xml exports goes some way (but even this doesn't allow exporting the cached page). How many users are you turning away daily by breaking promises of certain features that they read about when signing up?
Your relatively low standing according to Alexa (which surprises me considering the features) amongst social BM'ing makes me worried about your future, all the more reason to allow proper export of data, to reduce my risk only to change over costs should you go bust, not data loss.
Should I continue to use your service? Are you a serious company?
Regards,
Fullness
Edit:
P.S. I just want to make it clear that I really, really want you to fix these problems. I wouldn't have bothered with such a long post if I didn't think you had a service with excellent potential.
lucite wrote:
> maggie_diigo wrote:
> >Don't worry. all pages will be cached soon.
>
> Any update on this - it's been over 1 month and it still doesn't seem like cache is working.
>
> Thanks
I am sorry some features in V2 is not stable enough, that's why we are developing V3 which is much stable than V2.
I checked my cache. It works fine on V3, but it doesn't work on V2. Don't worry, your data is safe. We will fix it soon. Please let me know if you want to try out the V3.
You guys rock. When the problem happened I started looking around at what other services/sites offered and I have to say that every time I thought: Diigo is better. Your interface and your features are just better. And I'm saying this as a die-hard Google user for other types of services. If I stick with Diigo over the benefits that Notebook integration has for me, it's really that I think your service is THAT much better!
I'd love to try v3 to see what else you've got in store for us :)
> I checked my cache. It works fine on V3, but it doesn't work on V2. Don't worry, your data is safe. ...
No, it's NOT always safe. I have checked the cached pages of my own as well, and have found out that many of the pages I bookmarked during the late November through the early December were not cached as expected. Go to my page and try viewing the cache for
http://www.asahi.com/paper/editorial20071121.html
for example. It says "the requested page is no longer available", which clearly shows that THE SOURCE PAGE HAD EXPIRED BEFORE DIIGO RESTARTED CACHING. Sticky notes for such pages have nothing left to "stick" to; likewise, highlighted texts are nothing more than odrinary comments now that they aren't associated to any particular portions of the original document. Things will be nearly the same for those pages which were modified during the downtime.
I am not asking you to recover such info now, since I know it's too late for anyone to do that. I just want you to make clear when your system's caching feature went down and when it was recovered, and let all the users (including ones who haven't tried V3 yet) know that their bookmarks created within that period may have lost part of their info.
I am sorry for what happened to you. Besides improving the stability, We will monitor cache feature as you suggest.
Thanks,
Fullness
joel wrote:
> Hi fullness,
> I am sorry some features in V2 is not stable enough, that's why we are developing V3 which is much stable than V2.
> I checked my cache. It works fine on V3, but it doesn't work on V2. Don't worry, your data is safe. We will fix it soon. Please let me know if you want to try out the V3.
To Top