Very nice insight. I might even go a step further and archive the entire page[1]; hard drive space is cheap, and how many recipes is one person going to save, honestly? 1-2 LOCs worth? Then you can just parse the content you want, with the ability to drop down into the original page as you first saw it.
As a person with better visual memory for certain kinds of data, having the original page content may have as much meaning as the recipe, for entirely different reasons. Food can be very personal, and recipe books doubly so. A recipe archive can be as personal as we like, or all of that can abstracted away when we don’t need it.
I meant Library of Congress, an anachronistic visual metaphor related to data storage from the 1990s, perhaps earlier? In 2012, 1 LoC was roughly equivalent to ~3 PB (petabytes).
I remember first seeing it on Slashdot way back in the day, before they had user moderation or user meta-moderation.
If you save the source document, the code needed to parse your recipe archive is likely to be pretty short. Then you have a corpus to do A/B testing of your recipe parsing code against.
Side note: I feel that moderation and later meta-moderation system on Slashdot was the most transparent, fun, positive moderation system I’ve ever been part of. I wish HN had more than just up and downvotes, for instance. User meta-moderation would help reduce flamewars immensely IMO.
As a person with better visual memory for certain kinds of data, having the original page content may have as much meaning as the recipe, for entirely different reasons. Food can be very personal, and recipe books doubly so. A recipe archive can be as personal as we like, or all of that can abstracted away when we don’t need it.
[1] https://www.gwern.net/Archiving-URLs