I think the use case of annotation + web archive that @hypothes_is & @webrecorder_io have been exploring could be a real catalyst for both.
-
-
Replying to @edsu
@edsu@hypothes_is@webrecorder_io See also http://arxiv.org/abs/1003.2643 Interestingly, I just had a DM chat with@dwhly about#memento and annot.2 replies 0 retweets 2 likes -
Replying to @hvdsomp
@hvdsomp@edsu@webrecorder_io Yup. It’s about time to implement archive-upon-annotation. A deorphanizer!2 replies 0 retweets 0 likes -
Replying to @dwhly
@dwhly@edsu@webrecorder_io That's for sure. But Ilya's "via" approach made me think of archiving first, then annotating the archived.2 replies 0 retweets 0 likes -
Replying to @hvdsomp
@hvdsomp@edsu@webrecorder_io For me it's whether the annotation is viewed against the original later.4 replies 0 retweets 0 likes -
Replying to @dwhly
@dwhly@edsu@webrecorder_io So, the challenge becomes how to map/display non-anchors annotations to the "current" URI2 replies 0 retweets 1 like -
Replying to @hvdsomp
@hvdsomp@edsu@webrecorder_io Oh, we’re thinking of an “orphans” bucket. Orphans would offer to be reattached to the archived copy.3 replies 0 retweets 0 likes -
Replying to @dwhly
@dwhly@edsu@webrecorder_io No. The annotations would attach seamlessly to the archive copies. Because that's what was annotated.2 replies 0 retweets 0 likes
-
-
Replying to @webrecorder_io
@webrecorder_io I really like your idea of the archive as the site where annotation can happen; less need for plugin, etc@hvdsomp@dwhly2 replies 0 retweets 0 likes -
Replying to @edsu
@edsu@webrecorder_io@dwhly Just for the record, the "via" approach is not an "archiving" approach, it's a proxy to the live thing.0 replies 0 retweets 1 like
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.