Diigo approach to CNAME type DNS records: a thought for the distant future - 73 views

• 
  #1 Graham Perrin on 18 Nov 08

   

  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.

   

  <div class="cArrow"> </div><div class="cContentInner">A thought for the distant future: <br /> <br /> * CNAMEs <br /> <br /> 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'. <br /> <br /> 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. <br /> <br /> <a href="http://en.wikipedia.org/wiki/List_of_DNS_record_types" rel="nofollow" target="_blank">http://en.wikipedia.org/wiki/List_of_DNS_record_types</a> <br /> <br /> I expect no response to this topic. Just thinking out loud :) <br /> <br /> The current <a href="http://www.diigo.com/annotated/5739fb316e3a5d13001d771419b2818a" rel="nofollow">key principle </a> is understood: <br /> <br /> > Diigo's annotation / bookmarking is URL-specific.</div>

  ...

  Cancel
• 
  #2 Graham Perrin on 08 Dec 08

   

  > 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

   

  <div class="cArrow"> </div><div class="cContentInner">> a site manager may wish for one name (of a site) to be broadly <br /> > synonymous with another name - expressly for annotations such as Diigo. <br /> <br /> Cross reference <a href="http://groups.diigo.com/Diigo_HQ/forum/topic/8974" rel="nofollow" target="_blank">http://groups.diigo.com/Diigo_HQ/forum/topic/8974</a></div>

  ...

  Cancel
• 
  #3 Graham Perrin on 12 Mar 10

   

  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?

   

  <div class="cArrow"> </div><div class="cContentInner">Use case: <br /> <br /> Before too long, what's currently presented at <br /> <a href="http://centrim.mis.brighton.ac.uk/" rel="nofollow" target="_blank">http://centrim.mis.brighton.ac.uk/</a> <br /> may be presented instead at <br /> <a href="http://www.brighton.ac.uk/centrim/" rel="nofollow" target="_blank">http://www.brighton.ac.uk/centrim/</a> <br /> <br /> Key point: visible content will be 100% identical. <br /> <br /> (Apache is simply rewriting the URLs, and I hope for changes to the rewrite arrangements.) <br /> <br /> In a case such as this it will be nice to have all Diigo users' annotations of the content preserved, reappearing after the change. <br /> <br /> <a href="http://groups.diigo.com/group/Diigo_HQ/content/1217601" rel="nofollow" target="_blank">http://groups.diigo.com/group/Diigo_HQ/content/1217601</a> (January 2010) is <br /> <b>batch-change URL of previously highlighted sites?</b></div>

  ...

  Cancel

To Top