The rise in fan-based wikis allows fans to discuss TV shows and books in ways never before seen. Unfortunately, as fans, we have the problem of spoilers. Using a fan-based resource is wonderful for those who are current with their reading/watching, but it is frustrating for those who want to experience the suspense of reveals but have not caught up yet. Some sites have even added warnings to their pages to indicate the existence of spoilers, but these effectively tell visitors who are behind on their fiction consumption that the wiki cannot be used by them until they catch up.
RFC 7089, also known as Memento, provides a user the ability to choose a date and time in the past, then allows them to browse the web and see how it looked on that date. One of the great use cases of Memento is the avoidance of spoilers. Though Memento was original designed with the Internet Archive and other web archives in mind, these archives do not have all of the past versions of a page, subjecting fans to missing information they otherwise would have had access to, if all revisions of a page were available.
Jointly developed by Old Dominion University and Los Alamos National Laboratory, this is where the Memento MediaWiki Extension comes in.
The Internet Archive attempts to reconstruct web pages via snapshots (Mementos) that are taken of pages at various points in time. Many pages change more frequently than the Internet Archive can capture them, meaning that some revisions of a given web page are lost forever. Mediawiki, however, has all past revisions of a given page, and also its associated external resources. This inspired the development of the Memento Mediawiki Extension as an improvement over the Internet Archive's "drive by" method of digital preservation where Mediawiki sites are involved.
This curated talk will explore the problems of page reconstruction on the main web and detail the issues within the Mediawiki code that currently prevent and/or make it difficult to reconstruct the page in its totality as it looked at that revision.
I was invited to presented Test Driven Development to the ODU chapter of the ACM. Here I provide an introduction to the methodology, why one should use it, and the results of personal experience using the methodology, as well as why some do not think it is worthwhile.