tag:blogger.com,1999:blog-3018115029736777901.post5061201081109189117..comments2023-07-23T11:59:15.770+01:00Comments on futureArch, or the future of archives...: Investigating Terms of ServiceSusan Thomashttp://www.blogger.com/profile/04962583988591861531noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-3018115029736777901.post-16681593577498764862009-10-29T08:41:29.920+00:002009-10-29T08:41:29.920+00:00Good discussion. The practicality of archiving blo...Good discussion. The practicality of archiving blogs and other contributary websites is problematic. One of the few times that permission for me to archive a blog was not granted was when the blog owner felt unable to grant me permission to archive other peoples material. This was one of the very few occassions when a site owner was sufficiently aware of rights issues to raise concerns. <br /><br />I wonder how publishing a blog under a Creative Commons Licence - accepted by all contributors - would affect things?dnthttps://www.blogger.com/profile/11218789008554869322noreply@blogger.comtag:blogger.com,1999:blog-3018115029736777901.post-26737629456755297502009-10-16T09:03:57.725+01:002009-10-16T09:03:57.725+01:00Cool post! I love that most of 'em pretty much...Cool post! I love that most of 'em pretty much say "Yeah, you own everything, but it is also ours - thanks!". While we dream of freedom, it still remains the case that you don't get sommit for nuffin! :-)<br /><br />Does seem odd to have a bunch of restrictions on the Web pages and yet give everything away via RSS or other mechanical means. Seems like a tangled legal mess that no one is quite sure about so I'd be inclined to grab the bits worth grabbing, keep them safe somewhere (it that really *using* it?), and wait to see what happens.<br /><br />To my knowledge no one has (yet) sued Google for indexing their Web content (or indeed resurfacing it out of the Google cache). Archiving a Web page strikes me as being akin to indexing a Web page. <br /><br />Dunno.<br /><br />ps. Google, I hearby revoke your non-exclusive, royalty-free, world-wide license to use this comment. Not even read it. If you're an employee of Google, stop reading now. Oh. Damn. Too late... :-)pixelatedpetehttps://www.blogger.com/profile/01298274275234137603noreply@blogger.comtag:blogger.com,1999:blog-3018115029736777901.post-34058527268636069532009-10-14T17:30:32.697+01:002009-10-14T17:30:32.697+01:00We need to look more closely at the APIs different...We need to look more closely at the APIs different services make available for getting stuff out (and judge whether we care about properties that might be lost in the process). <br /><br />This post by Matt Asay on moving data into/between/out of cloud services is interesting: <a href="http://news.cnet.com/8301-13505_3-10367052-16.html" rel="nofollow">http://news.cnet.com/8301-13505_3-10367052-16.html</a>.Susan Thomashttps://www.blogger.com/profile/04962583988591861531noreply@blogger.comtag:blogger.com,1999:blog-3018115029736777901.post-42157299670748998302009-10-14T16:24:33.500+01:002009-10-14T16:24:33.500+01:00This isn't the whole story, though. Some of th...This isn't the whole story, though. Some of these services provide access to their underlying data via other means. Twitter is an obvious example, where the API is designed to do exactly the sort of things with the ToS for the web interface prohibit. Automated retrieval of twitter data via the API is encouraged, albeit rate-limited. For archival purposes, this will almost always be sufficient, unless one is specifically concerned with the appearance of twitter's web interface as opposed to the content it is delivering.<br /><br />The same is true in a different way of blogs on Wordpress, accessible via RSS feeds. That alternative approach is the key behind the <a href="http://archivepress.ulcc.ac.uk/" rel="nofollow">ArchivePress</a> project (http://archivepress.ulcc.ac.uk/)Kevin Ashleyhttps://www.blogger.com/profile/15371869767865369079noreply@blogger.com