<?xml version="1.0"?>
<oembed><version>1.0</version><provider_name>Scholarly Communications @ Duke</provider_name><provider_url>https://blogs.library.duke.edu/scholcomm</provider_url><author_name>Kevin Smith, J.D.</author_name><author_url>https://blogs.library.duke.edu/scholcomm/author/ksmithl2duke-edu/</author_url><title>A"twitter" about contracts - Scholarly Communications @ Duke</title><type>rich</type><width>600</width><height>338</height><html>&lt;blockquote class="wp-embedded-content" data-secret="CeBMNrcV9e"&gt;&lt;a href="https://blogs.library.duke.edu/scholcomm/2008/06/13/atwitter-about-contracts-2/"&gt;A&#x201D;twitter&#x201D; about contracts&lt;/a&gt;&lt;/blockquote&gt;&lt;iframe sandbox="allow-scripts" security="restricted" src="https://blogs.library.duke.edu/scholcomm/2008/06/13/atwitter-about-contracts-2/embed/#?secret=CeBMNrcV9e" width="600" height="338" title="&#x201C;A&#x201D;twitter&#x201D; about contracts&#x201D; &#x2014; Scholarly Communications @ Duke" data-secret="CeBMNrcV9e" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" class="wp-embedded-content"&gt;&lt;/iframe&gt;&lt;script&gt;
/*! This file is auto-generated */
!function(d,l){"use strict";l.querySelector&amp;&amp;d.addEventListener&amp;&amp;"undefined"!=typeof URL&amp;&amp;(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&amp;&amp;!/[^a-zA-Z0-9]/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret="'+t.secret+'"]'),o=l.querySelectorAll('blockquote[data-secret="'+t.secret+'"]'),c=new RegExp("^https?:$","i"),i=0;i&lt;o.length;i++)o[i].style.display="none";for(i=0;i&lt;a.length;i++)s=a[i],e.source===s.contentWindow&amp;&amp;(s.removeAttribute("style"),"height"===t.message?(1e3&lt;(r=parseInt(t.value,10))?r=1e3:~~r&lt;200&amp;&amp;(r=200),s.height=r):"link"===t.message&amp;&amp;(r=new URL(s.getAttribute("src")),n=new URL(t.value),c.test(n.protocol))&amp;&amp;n.host===r.host&amp;&amp;l.activeElement===s&amp;&amp;(d.top.location.href=t.value))}},d.addEventListener("message",d.wp.receiveEmbedMessage,!1),l.addEventListener("DOMContentLoaded",function(){for(var e,t,s=l.querySelectorAll("iframe.wp-embedded-content"),r=0;r&lt;s.length;r++)(t=(e=s[r]).getAttribute("data-secret"))||(t=Math.random().toString(36).substring(2,12),e.src+="#?secret="+t,e.setAttribute("data-secret",t)),e.contentWindow.postMessage({message:"ready",secret:t},"*")},!1)))}(window,document);
//# sourceURL=https://blogs.library.duke.edu/scholcomm/wp-includes/js/wp-embed.min.js
&lt;/script&gt;
</html><description>Although I had heard of Twitter for a while now, I did not really know what it was until prompted to learn more by two recent articles. One is this piece in the Chronicle of Higher Education about potential library uses for the &#x201C;microblogging&#x201D; or social messaging service. It recalls the discussions I heard recently &hellip; Continue reading &rarr;</description></oembed>
