Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Thanks to @parkjs814 and all other contributors to this project; it is an amazing resource for learners.
Overview
This issue is intended to continue a conversation from #228 on the problem of the complex API, which @nem035 has explained clearly in his comment:
I've run into this 'noisiness' problem too and want to open a discussion so that we can:
Ideas
@nem035 suggested something similar to variable watch in Chrome Dev Tools:
Another idea he suggested is to create a Babel plugin or macro that hides the tracer code (in the individual algorithm scratchpads). This sounds promising along with the idea of using some special comment syntax which Babel could operate on.
One additional (yet 'rough') idea could be to utilize the Chrome DevTools Protocol in a similar way as it is used in the 'Sources' tab of the debugger. I'm thinking something similar to the way that the editor when stepping through code, you can 'inspect' program variables via hovering or displayed to the right of the line. One obvious downside of using CDP in this way would be potential browser compatibility issues.
What are some techniques used in other tracing libraries that we could take inspiration from and apply to this project? Are there common patterns we can utilize?