= Suggestion =

Allow Diigo to recognise the manageress/manager of a site.


= Implementation =

Following the Google approach:

1. manager contacts Diigo claiming ownership/managership of a site

2. Diigo asks the person to add a uniquely named file to the root of the site

3. manager adds the file

4. Diigo finds the file and recognises the site's owner/manager.


= Purposes =

A manager may wish to add highlights to a home page

- I wish to do this, for the home pages of my groups' sites.

A manager may wish to remove legacy graffiti from a home page.

A manager of two sites, which have near-identical texts but dissimilar styles, may wish to *carefully* define (for Diigo users' annotations) a relationship/similarity between the two; see below.

Et cetera.


= Relevance to previous topics =

http://www.diigo.com/annotated/bb5768665eaf6bd219dfaad9e0574ed5 (2008-11-18)

> a site manager may wish for one name (of a site) to be broadly
> synonymous with another name

http://www.diigo.com/annotated/874e6aceaca7b35ae89c8f61cc983e08 (2008-11-25)

> site manager-defined 'URL synonyms' (for want of a better expression)

et cetera.

> A manager may wish to remove legacy graffiti from a home page.

More usefully, less destructively:

* from a home page, a manager may wish to extract all annotations then

- delete the floating sticky notes and others that have graffiti-like appearance

- from the extracts: re-post valuables, in a more presentable form, either at the home page or (more likely) at pages that are more relevant to the annotation.

Ah, juggling. I have months on, months off… :)

A thought for the distant future:

* CNAMEs

I don't imagine any special consideration for CNAMEs within a current Diigo roadmap. It may eventually fall under an umbrella of 'things that site managers might request'.

Example: in rare circumstances, a site manager may wish for one name (of a site) to be broadly synonymous with another name - expressly for annotations such as Diigo.

http://en.wikipedia.org/wiki/List_of_DNS_record_types

I expect no response to this topic. Just thinking out loud :)

The current key principle is understood:

> Diigo's annotation / bookmarking is URL-specific.

> a site manager may wish for one name (of a site) to be broadly
> synonymous with another name - expressly for annotations such as Diigo.

Cross reference http://groups.diigo.com/Diigo_HQ/forum/topic/8974

Use case:

Before too long, what's currently presented at
http://centrim.mis.brighton.ac.uk/
may be presented instead at
http://www.brighton.ac.uk/centrim/

Key point: visible content will be 100% identical.

(Apache is simply rewriting the URLs, and I hope for changes to the rewrite arrangements.)

In a case such as this it will be nice to have all Diigo users' annotations of the content preserved, reappearing after the change.

http://groups.diigo.com/group/Diigo_HQ/content/1217601 (January 2010) is
batch-change URL of previously highlighted sites?

Comparison

Diigo About http://about.diigo.com/about/www.pcmag.com%2Farticle2%2F0%2C2817%2C2351132%2C00.asp gives a correct title for the bookmark.

Regression? This bug is re-opened. Cross-reference http://groups.diigo.com/group/Diigo_HQ/content/965967

I see a few examples of this bug today, most recently
http://www.diigo.com/annotated/874e6aceaca7b35ae89c8f61cc983e08
http://www.diigo.com/annotated/bb5768665eaf6bd219dfaad9e0574ed5

> Editing a URL

Tagged as FAQ,
http://groups.diigo.com/group/Diigo_HQ/content/553935

> editing the URL is often NECESSARY

You can do so using Diigolet, but beware of the consequences. See at least http://groups.diigo.com/group/Diigo_HQ/content/960338

On 12th May 2008, Pierre-Yves Gillier suggested:

> finish main features of this API.

> a lots of devs will try to use tags and/or lists.

> I can't give it to users as "bookmarks" is the only feature available.

+1
to extending and improving the APIs.

Historically:

* a plan to publicise the API was announced in April 2008 http://groups.diigo.com/Diigo_HQ/forum/topic/3049

* alpha of the API was publicised in May http://groups.diigo.com/Diigo_HQ/forum/topic/3776

* http://www.diigo.com/tools/api currently comes under the banner of Diigo V3 beta

* and Diigo recently have a mass of suggestions to consider ;)

> Google Wave…  one to watch … Diigo services should
> fit somewhere, probably in more than one place, very neatly.

For what I imagined, Google Wave is not proving so friendly.
There's a public wave permalink to a blip, wavelet or wave
(short URL: http://ur1.ca/fv8l)
that highlights the lack of permalinks. In brief:

* multiple ways to refer to a wave (no single definitive URL)
* no way to refer to a wavelet
* no way to refer to a blip
* no way to refer to a point in playback.

Some other topics that discuss groups API:

http://groups.diigo.com/group/Diigo_HQ/content/551536
http://groups.diigo.com/group/Diigo_HQ/content/553687
http://groups.diigo.com/group/Diigo_HQ/content/554265
http://groups.diigo.com/group/Diigo_HQ/content/958154
http://groups.diigo.com/group/Diigo_HQ/content/958159
http://groups.diigo.com/group/Diigo_HQ/content/1068151
http://groups.diigo.com/group/Diigo_HQ/content/1206831

Other topics that discuss groups API, in order:

http://groups.diigo.com/group/Diigo_HQ/content/549678
http://groups.diigo.com/group/Diigo_HQ/content/551536
http://groups.diigo.com/group/Diigo_HQ/content/553687
http://groups.diigo.com/group/Diigo_HQ/content/554265
http://groups.diigo.com/group/Diigo_HQ/content/958154
http://groups.diigo.com/group/Diigo_HQ/content/958159
http://groups.diigo.com/group/Diigo_HQ/content/1068151

FWIW I'd aim for the one that has the attention of Diigo team.

Suspect that the AJAX aspect of Google Docs reduces the possibility of this happening.

> (without slash at end) is not working.

http://groups.diigo.com/Diigo_HQ/bookmark/tag/3984 refers to
http://www.moviezone.cz/clanek/14359-derrickson-a-dalsi-velke-sci-fi
(no solidus at tail) which works fine in Safari 3.2.1 (5525.27.1) and Firefox 3.0.5 on Mac OS X 10.5.6.

> Firefox 3 beta 5 current night build, Diigo Toolbar addon 3.1.5.4, Windows XP SP3

Maybe an issue with your Firefox or Windows?

> Firefox 3 beta 5 current night build, Diigo Toolbar addon 3.1.5.4, Windows XP SP3

Your Diigo is considerably outdated, please use the Tools menu of Firefox to gain the update to 3.1.6.13.

Regards
Graham

Subject: another example, consequences etc.

Example:
http://groups.diigo.com/Diigo_HQ/forum/topic/41995

Probable consequence:
http://groups.diigo.com/Diigo_HQ/forum/topic/41994

Related:
http://groups.diigo.com/Diigo_HQ/forum/topic/41996

Thanks to Michael for the clarification, much appreciated.

Let's await a response from Diigo.

Observations

If a user of Diigolet wishes new bookmarks to be private, that privacy must be set every time a bookmark is made.

Users may overlook the setting. The likelihood of user error is greater when a user is busy or distracted.

Publication of something private is an accident that occurs too easily, too frequently in Diigolet 3.1b506.


Suggestions

1. For a new user's first bookmark, Diigolet should default to public.

2. For a new user's first highlight, Diigolet should default to obscurity.

3. Diigolet should allow the user to prefer obscurity for new bookmarks.


Implementations

[√] 1. is current behaviour.

[-] 2. is close to current behaviour but the expression is different. (Expression will be a separate topic.)

[X] 3. is not possible, the introduction of this feature should be prioritised.


Rationale

Any issue that involves lack/loss of privacy should gain priority attention.

The user error (PEBKAM) element should not detract. Wherever a Diigo UI allows the user to too easily make such errors, leading to lack/loss of privacy, that aspect of the UI should gain priority attention.


See also

http://groups.diigo.com/Diigo_HQ/forum/topic/9587
http://groups.diigo.com/Diigo_HQ/forum/topic/9618

Special note

This topic originated in January 2009, and once existed as http://groups.diigo.com/Diigo_HQ/forum/topic/9588, but the original topic is missing or lost.

A radio button approach something like
http://pastie.textmate.org/358496 lines 2 and 3
(extracted from notional http://pastie.textmate.org/357303 )
may be applied to the Bookmark dialogue.

Two radio buttons + persistence (cookie)
in lieu of one [√] tick box
should kill two birds with one stone, in which case

> 3. Diigolet should allow the user to prefer obscurity for new bookmarks.

need not require any preference-setting elsewhere.

Bug

http://groups.diigo.com/Diigo_HQ/forum/topic/9588 (referred from http://groups.diigo.com/group/Diigo_HQ/content/549001#3 ) redirects to
http://groups.diigo.com/group/Diigo_HQ?type=topic

http://groups.diigo.com/group/Diigo_HQ/content/tag/obscure doesn't find the topic, which was once named Diigolet should allow the user to prefer obscurity as a default for new bookmarks and tagged with the word obscure so I'm fairly certain that it's missing from this group.

I have recreated the missing topic at
http://groups.diigo.com/group/Diigo_HQ/content/1380563 ,
Diigo service should allow obscurity/privacy by default for Diigolet, Post to Diigo and other scripts