{"id":20,"date":"2005-01-23T02:15:13","date_gmt":"2005-01-23T06:15:13","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/longestnow\/2005\/01\/23\/archiveorg-and-mixed-messages\/"},"modified":"2005-01-23T02:15:13","modified_gmt":"2005-01-23T06:15:13","slug":"archiveorg-and-mixed-messages","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/longestnow\/2005\/01\/23\/archiveorg-and-mixed-messages\/","title":{"rendered":"Archive.org and mixed messages"},"content":{"rendered":"<p><a name='a750'><\/a><\/p>\n<p>\nArchive.org is one of the great organizations around.&nbsp; They aim to<br \/>\nprovide pure services, aren&#8217;t afraid of trying out new and daring<br \/>\nprojects for improving public access to information, and stand for all<br \/>\nof the right ideals of openness and advancement through sharing.<\/p>\n<p>But they seem to suffer from <span style=\"font-weight: bold;\">quirks <\/span>like any other organization; they<br \/>\nhave a confusing and complicated website, which has only grown more<br \/>\nconfusing since two years ago, when I recall giving up trying to use it<br \/>\nto find out what I wanted to know about their content archives.&nbsp;<br \/>\nToday I tried to upload some audio file to the site, and found that<br \/>\ntheir project nomenclautre was as <span style=\"font-weight: bold;\">inconsistent <\/span>and<br \/>\nconfusing [was I uploading &#8220;live music&#8221;?&nbsp; No.&nbsp; But that was<br \/>\nthe only link I had to follow for information on uploads], and their<br \/>\nchanging color schemes and profusion of navbar-like elements as<br \/>\ndistracting, as ever&#8230;<\/p>\n<p><a href=\"http:\/\/joi.ito.com\"><br \/>\nJoi<\/a> tried to explain how easy it is to upload content to archive.org :<\/p>\n<div style=\"margin-left: 40px;\">[once you have created an account on the site and logged in]\n<\/div>\n<div style=\"margin-left: 40px;\">just ftp to audio-uploads.archive.org&nbsp; <br \/>\n[logging in with your email address and password from the website]<br \/>\nmkdir the name of the file without the extension<br \/>\ncd to it<br \/>\nupload it<br \/>\nthen go to http:\/\/www.archive.org\/audio\/audio-contribute.php<br \/>\nimport it, <br \/>\ntag it and away it goes\n<\/div>\n<p>\nWell!&nbsp; That might be pretty easy compared to downloading and<br \/>\ncompiling your own software, but it requires seven+ steps, two logins,<br \/>\nand two pieces of software. And this is a task that one presumes<br \/>\nnon-geeks are supposed to be able to do.&nbsp; From an efficiency<br \/>\nstandpoint, this is a disaster&#8230; consider that the basic task at hand,<br \/>\n<span style=\"font-weight: bold;\">uploading a file<\/span> from your<br \/>\nmachine to a remote machine using a browser, is neatly handled by the<br \/>\ntwo-step &#8220;Browse&#8230;&#8221; form with which every Windows user and most web<br \/>\nusers are familiar.<\/p>\n<p>So I want to know how this could be allowed to happen?&nbsp; How can<br \/>\nall of the brilliant people who I know both visit archive.org often,<br \/>\nknow its developers and supporters, have excellent design sense&#8230; how<br \/>\ncan these people let the site slouch around in its current state of<br \/>\nconfusion?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Archive.org is one of the great organizations around.&nbsp; They aim to provide pure services, aren&#8217;t afraid of trying out new and daring projects for improving public access to information, and stand for all of the right ideals of openness and advancement through sharing. But they seem to suffer from quirks like any other organization; they [&hellip;]<\/p>\n","protected":false},"author":135,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[206],"tags":[],"class_list":["post-20","post","type-post","status-publish","format-standard","hentry","category-a-la-mod"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/longestnow\/wp-json\/wp\/v2\/posts\/20","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/longestnow\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/longestnow\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/longestnow\/wp-json\/wp\/v2\/users\/135"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/longestnow\/wp-json\/wp\/v2\/comments?post=20"}],"version-history":[{"count":0,"href":"https:\/\/archive.blogs.harvard.edu\/longestnow\/wp-json\/wp\/v2\/posts\/20\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/longestnow\/wp-json\/wp\/v2\/media?parent=20"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/longestnow\/wp-json\/wp\/v2\/categories?post=20"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/longestnow\/wp-json\/wp\/v2\/tags?post=20"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}