Point.
-
-
So when is it all getting deployed into archive-it and webrecorder? Or is it not just a technical problem? Speaking of my PhD work...
1 reply 0 retweets 1 like -
Limited release of demo system+browser extension soon (happy to share w/ you). More detailed video screen captures available next week too. All Prototype though. IA and WR are aware.
1 reply 1 retweet 3 likes -
Replying to @mart1nkle1n @hvdsomp
Nice. Good luck! While I had seen Memento Tracer before I only recently found out about behaviors in Brozzler, which according to GitHub date back at least till July of 2015. https://github.com/internetarchive/brozzler/commits/master?after=809ea3885ffa1a9e2db9058f83b5e468e9724203+34&path%5B%5D=brozzler&path%5B%5D=behaviors.yaml …
#liveandlearn1 reply 0 retweets 1 like -
I think point
@edsu was making was about interoperability/standardization of automated behavior systems, something I've also suggested but is easier said than done. For example, both Brozzler and LOCKSS both have automated behavior systems, and we are developing one for WR1 reply 0 retweets 5 likes -
Replying to @IlyaKreymer @edsu and
They each have unique requirements and constraints, and slightly different implementation stacks. Tracer takes a uniquely different approach and introduces a visual scripting component instead of hand scripted behaviors. While this is very interesting and promising 1/2
1 reply 0 retweets 2 likes -
Replying to @IlyaKreymer @edsu and
that doesn't really make it interoperable with previous approaches. Arguably, a new approach makes interoperability with the previous solutions harder, not easier. Interop requires close collaboration, and investment both technical and political, esp. given limited resources 2/2
1 reply 0 retweets 2 likes -
As you know, system interop and standards dev is a big part of what we do, hence at the forefront of our thinking when developing new systems. I assume you are not arguing against a diverse landscape of interoperable and standards-compliant systems?
1 reply 0 retweets 0 likes -
I don't hear
@ilyakreymer arguing against diversity and interop. i hear him saying that successful standards are grown from people wanting to work together collaboratively. Hopefully the prototype you've built will generate that. If not, back to the drawing board, together.1 reply 0 retweets 3 likes -
We’ve already been in touch with
@IlyaKreymer regarding the language to record traces and the need to be able to use that language across systems. And, remember that the traces concept had the notion of community sharing of traces from the outset.1 reply 0 retweets 1 like
Yes, and I was just saying that I don't think @edsu ignored Tracer, because Tracer is not *yet* an interoperable solution. Interop is hard. Looking forward to working together so that we can arrive at an interoperable solution in the foreseeable future :)
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.