When I save an image on a page that I have already saved to diigo, 3 things happen that I do not want to happen:
- changes I made to the title of the bookmark are gone
- the bookmark description I added is lost
- the bookmark is converted from private to public

This is a serious step backwards of the paid version compared to highlighting images in previous versions. Thanks for fixing this soon.

Here is a summary of serveral issues with ampersand and semicolons (hope the URLs work...):

1. In cached URLs 'ampersandlang' is replaced with '〈'. Accordingly, fulltext search in bookmarked sites is not working. The same also happens on this forum.
See discussion at http://groups.diigo.com/Diigo_HQ/forum/topic/full-text-search-47344#6

2. When posting to Delicious, text following an ampersand or semicolon in the bookmark's title or description is not transferred to delicious. This makes crossposting useless.
See discussion at http://groups.diigo.com/Diigo_HQ/forum/topic/posting-to-delicious-truncates-bookmark-title-after-vertical-bar-or-semicolon-47080

See also the following discussions:
http://groups.diigo.com/Diigo_HQ/forum/topic/save-elsewhere-to-delicious-bugs-44334
http://groups.diigo.com/Diigo_HQ/forum/topic/bookmark-urls-exported-to-delicious-and-ma-gnolia-break-at-ampersand-character-5772

Issue 2 is still unresolved and I'd very much appreciate if someone could look into this. If there is an official tool for saving bookmarks to Delicious, Diigo should make sure it really works. However, it seems that things have become even worse in V4, for Diigo is now syncing the truncated text after each change made in Diigo (e.g. adding a new tag) - overwriting any corrections made in the meantime in Delicious.

According to Delicious the problem is not with them but with Diigo (see http://groups.diigo.com/group/Diigo_HQ/content/posting-to-delicious-truncates-bookmark-title-after-vertical-bar-or-semicolon-958832#6 ).

Thanks.

Graham Perrin wrote:
> I'll treat this topic as resolved.

Confirmed. Cross-posting to Delicious is working smoothly again:
- bookmarks appear in Delicious after a few seconds
- public/private status is preserved

Thanks for solving this.

Graham Perrin wrote:
> Subject: please, do not convert descriptions to personal comments
>
> Lars Bauer wrote:
> > descriptions … as a … comment
>
> With respect: I disagree strongly.
> When I write a description, I expect it to be presented as a description.

Graham, first I was of the same opinion as you are. But then I realized that things are more complicated because diigo handles group bookmarks as copies of users' bookmarks.

When I save a bookmark to a group that has already been shared to that group, my description and tags will overwrite existing descriptions and tags (and if I don't add any description or tags, existing ones will be deleted).
I assume that's why diigo automatically duplicates a description as a group comment by that user when I click 'Share to a group'. This way, original descriptions will be retained as a comment even after another group member has added a new description. A disadvantage is, however, that the last description will appear twice in group feeds and blog or e-mail forwardings: once as description, once as comment. This is not ideal either.

In my view, the only way to get around this is to handle group bookmarks and group content separately:

1. either by adding another field for group descriptions (as was suggested by Russ for group tags but which could be confusing/undesirable for some users),

2. or by allowing direct bookmarking to a diigo group (with an option to save a copy to your own bookmarks). Accordingly, one could add another command to the context menu / toolbar: "Bookmark this page to a Diigo group". If the bookmark had already been posted to that group the description and tag fields in the dialog box would then be populated with the existing content which could be amended/modified by subsequent users (same behavior as now for users' bookmarks). Each user could also add comments and highlights. This way, one could also stop duplicating bookmark descriptions as user comments.
Personally, I would prefer this second solution.

Graham Perrin wrote:
> For a bookmark that you expect to be amongst search results, check that a cached copy exists.

Thanks for the hint!

Searching in the fulltext of my bookmarks generally works fine. However, for some of my bookmarks Diigo seems to cache a wrong/altered URL.

Example:
http://www.diigo.com/user/basral/urteile%20unzumutbarkeit?tab=250

The original URL is:
http://relevancy.bger.ch/cgi-bin/JumpCGI?id=BGE-100-II-345&lang=de&zoom=OUT&system=clir

This URL is correctly shown in the browser's status bar when I hover over 'Cached'. However, when I click on 'Chached' '&lang' is replaced with a special character and no cached version is available ("Error. Invalid Reference"). This strange URL is also shown in the header of the expanded Diigo 'Preview' (although the page is displayed correctly).

Any idea what's going wrong?

Graham Perrin wrote:
> Can you report the URL issue in a separate topic? Thanks.

I've posted a summary at
http://groups.diigo.com/Diigo_HQ/forum/topic/summary-of-issues-with-ampersand-and-semicolon-in-url-title-or-description-47382

Graham Perrin wrote:
> Are you sure that
> |
> is a factor?
>
> At a glance, I see truncation after
> ;

You're right. It doesn't seem to be the pipe but the semicolon.
- ( ) / : > _ also work fine

text/text: text - text | text > text; addendum

only truncates the addendum.

Thanks for the hint, that narrows the problem. I nevertheless hope that semicolons can be included in the near future.

Graham Perrin wrote:
> I should recommend you contact Delicious to see if it's a known issue there.

FYI: Answer from Britta (Delicious Team Member):
"It sounds like this is a problem with Diigo - they probably aren't encoding the titles properly. You'll probably want to report this bug to them directly. Thanks!"

See http://support.delicious.com/forum/comments.php?DiscussionID=2749&page=1#Item_1

Graham Perrin wrote:

> The feed will reveal past and future descriptions, comments, sticky notes etc.

The feed also reflects renaming of tags. I dislike this reordering and wish it could be made optional at least. By default feeds should be sorted by date added.

I use tag feeds for drawing other team members' attention to new links; if they want to explore new highlightings, comments, tags etc. they can do this at the diigo site.