Copyright issue applies to all services that allow you to save a page, even Google would be guilty for caching. It is up to the user to judge for a copyright infringement before saving a page.
Since I'm currently exploring some of the same problems, I'd like to ask further..
How do you guard yourself against user-shared copyrighted content* ? Do you delete on request from the copyright holders? Do you weed out in the shared content once in a while? Do you have some kind of policy or agreement transfering the infrigement to the sharing user in such cases ?
*Say, a user has access to some content behind a paywall, but shares it un-blocked through your service.
We have to delete public content that has been requested to be deleted by the copyright holders. In such a case the user will be notified about the infirigement and the possible removal of his content.
If you have an example site that dynamically renders a page I could try it out and show you the result
Re:A different approach to bookmarking
by jamesbritt on Sunday March 27, 2011 @01:46AM
(#2374282)
http://lifehacker.com/#!5785555/how-perfectionism-can-lead-t...
for example.
I was pleasantly surprised to find that Firefox will do a successful Save As of the content, even though View Source only shows the original page. And the ScrapBook plug-in also saves the page correctly.
There you go: http://copyto.co/b/MTQ , used the Chrome extension to select the main content only and saved it + made the bookmark public
Re:A different approach to bookmarking
by jamesbritt on Sunday March 27, 2011 @07:01PM
(#2376355)
Sweet! Thanks.
Really? Even if copyright holders litigiously suggest otherwise?
Of more practical value, does it work on pages that use JavaScript to dynamically render a page?