> I LOVE the cache function. > > However, it would be even better if the cache included the > highlight/note.
Which advantage would that have? I just tested whether comments and notes are already included in full-text searches and they actually are. So, that can't be the advantage.
> Also, a couple of pages didn't cache: is there ever a delay? will they > be cached eventually? If not, is there a way pages can be 're-cached'?
The point of the cache is to preserve pages that might otherwise be removed from the web.
If a page is removed from the web, the cached version and the notes are separate entities. One cannot see them together as is normally the case.
Also, when I'm on a computer that doesn't have diigo installed, I again want to be able to access the cached version with the notes overlaid. Otherwise, again they are two separate entities.
So, what happens when a page isn't cached after several hours?
John Knight wrote: > The point of the cache is to preserve pages that might otherwise be > removed from the web. > > If a page is removed from the web, the cached version and the notes are > separate entities. One cannot see them together as is normally the case. > > Also, when I'm on a computer that doesn't have diigo installed, I again > want to be able to access the cached version with the notes overlaid. > Otherwise, again they are two separate entities.
OK, now I can see your points.
> So, what happens when a page isn't cached after several hours?
Normally, caching shouldn't take that long. But I do not know the answer to your question because I am just a Diigo user myself. Unless you have put a lot of work into the page by higlighting sections and adding comments/notes, you could try to delete that page from your personal bookmark collection and add it again. Maybe that helps.
Thanks for your input. Will consider offering that option. Meanwhile, try clicking on the "about" link for each bookmark - you will see lots of related stuff all nicely presented there.
Caching normally shouldn't take too long, but once in a while our servers get quite busy and some delay may occur. Also, once in a while, certain few pages have somewhat strange behaviors and are not being properly cached - we're looking into that as we're further optimizing our search capability now.
> John, > > Thanks for your input. Will consider offering that option. > Meanwhile, try clicking on the "about" link for each bookmark - you > will see lots of related stuff all nicely presented there.
Just to reiterate (and since this isn't the case yet...) annotations really *should* go with the cached page. Otherwise... what's the point of the cache? Is diigo a *cache*ing service??? or is diigo an annotation service?? neither here... nor there???
> annotations really *should* go with the cached page.
Relating to a single URL: content may change over time, and over a period of months or years I may iteratively add and subtract to my annotations for that URL.
Should Diigo cumulatively cache the content, and relate it to an annotation, _each_ time an annotation is made?
If so:
* how easy does it become for a person to view a cached copy of a page?
If presented with your thirty or forty cached copies of a page:
* which ones would you choose to view?
If in a busy group, a large number of people add annotations, all at different times, to a single URL:
* how many caches would you imagine, and which caches would you choose to view?
= Observation of the present =
Diigo 3 Beta offers, I believe, a reasonable, well-considered balance:
* one cached copy of the content of a URL
* extraction of annotations for that URL.
Beyond that: most browsers offer the ability to save content. For example:
1. Safari
2. view a URL
3. present Diigolet
4. File menu
5. Save As…
6. Web Archve
The Safari production does include highlights and annotations.
Problem solved: whenever I wish to save annotations with (not extract annotations from) a URL, I save as a web archive :)
From meta you can step to snapshots (user- and robot-contributed copies of the page, on a timeline) — and vice versa — those features plus everything else in Diigo 4.0 beta form a rich toolset in a neatly rounded package.
Performance in all key areas seems to be excellent, so I'm tagging this topic resolved unless any of the original contributors have anything to add.
John Knight wrote:
> I LOVE the cache function.
>
> However, it would be even better if the cache included the
> highlight/note.
Which advantage would that have? I just tested whether comments and
notes are already included in full-text searches and they actually are.
So, that can't be the advantage.
> Also, a couple of pages didn't cache: is there ever a delay? will they
> be cached eventually? If not, is there a way pages can be 're-cached'?
Here are two relevant threads:
Thread "Full Text Search doesn't work":
http://forum.diigo.com/topic/350#1216
Core message: There may a delay sometimes but it should be short. In
most cases, the pages will be cached immediately (this is my
experience).
Thread "Can I update cached pages?":
http://forum.diigo.com/topic/194#630
Core message: If a page has already been cached, it cannot be re-cached.
The first version of a cached page will always stay the cached version.
The point of the cache is to preserve pages that might otherwise be
removed from the web.
If a page is removed from the web, the cached version and the notes are
separate entities. One cannot see them together as is normally the case.
Also, when I'm on a computer that doesn't have diigo installed, I again
want to be able to access the cached version with the notes overlaid.
Otherwise, again they are two separate entities.
So, what happens when a page isn't cached after several hours?
John Knight wrote:
> The point of the cache is to preserve pages that might otherwise be
> removed from the web.
>
> If a page is removed from the web, the cached version and the notes are
> separate entities. One cannot see them together as is normally the case.
>
> Also, when I'm on a computer that doesn't have diigo installed, I again
> want to be able to access the cached version with the notes overlaid.
> Otherwise, again they are two separate entities.
OK, now I can see your points.
> So, what happens when a page isn't cached after several hours?
Normally, caching shouldn't take that long. But I do not know the answer
to your question because I am just a Diigo user myself. Unless you have
put a lot of work into the page by higlighting sections and adding
comments/notes, you could try to delete that page from your personal
bookmark collection and add it again. Maybe that helps.
Thanks for your input. Will consider offering that option. Meanwhile, try clicking on the "about" link for each bookmark - you will see lots of related stuff all nicely presented there.
Caching normally shouldn't take too long, but once in a while our servers get quite busy and some delay may occur. Also, once in a while, certain few pages have somewhat strange behaviors and are not being properly cached - we're looking into that as we're further optimizing our search capability now.
> John,
>
> Thanks for your input. Will consider offering that option.
> Meanwhile, try clicking on the "about" link for each bookmark - you
> will see lots of related stuff all nicely presented there.
Just to reiterate (and since this isn't the case yet...) annotations really *should* go with the cached page. Otherwise... what's the point of the cache? Is diigo a *cache*ing service??? or is diigo an annotation service?? neither here... nor there???
> annotations really *should* go with the cached page.
Relating to a single URL: content may change over time, and over a period of months or years I may iteratively add and subtract to my annotations for that URL.
Should Diigo cumulatively cache the content, and relate it to an annotation, _each_ time an annotation is made?
If so:
* how easy does it become for a person to view a cached copy of a page?
If presented with your thirty or forty cached copies of a page:
* which ones would you choose to view?
If in a busy group, a large number of people add annotations, all at different times, to a single URL:
* how many caches would you imagine, and which caches would you choose to view?
= Observation of the present =
Diigo 3 Beta offers, I believe, a reasonable, well-considered balance:
* one cached copy of the content of a URL
* extraction of annotations for that URL.
Beyond that: most browsers offer the ability to save content. For example:
1. Safari
2. view a URL
3. present Diigolet
4. File menu
5. Save As…
6. Web Archve
The Safari production does include highlights and annotations.
Problem solved: whenever I wish to save annotations with (not extract annotations from) a URL, I save as a web archive :)
Diigo meta views such as http://www.diigo.com/bookmark/http%3A%2F%2Fwww.utechtips.com%2Fround-two-and-version-4-diigo?f=m&tab=comment&uname=grahamperrin seem to serve this purpose.
From meta you can step to snapshots (user- and robot-contributed copies of the page, on a timeline) — and vice versa — those features plus everything else in Diigo 4.0 beta form a rich toolset in a neatly rounded package.
Performance in all key areas seems to be excellent, so I'm tagging this topic resolved unless any of the original contributors have anything to add.