LOC? Line of Code? Surely 1-2 LOCs is significantly less than any recipe.
Re:Turn recipe websites into plain text
by aspenmayer on Saturday June 27, 2020 @01:34PM
(#23663193)
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.
https://blogs.loc.gov/thesignal/2012/04/a-library-of-congres...
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.
Re:Turn recipe websites into plain text
by icegreentea2 on Friday June 26, 2020 @09:56AM
(#23652006)
I'm guess it's "Library of Congress"
Re:Turn recipe websites into plain text
by aspenmayer on Friday June 26, 2020 @10:14AM
(#23652181)
Yeah, that’s what I meant. I was going for a visual metaphor that might be lost if I just said some number of bytes.
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