James Addison

@weightwatchers-carlanderson Introducing those kind of checks within a separate GitHub Actions workflow (with separate Python requirements file for `great_expectations`) could be useful to prove the concept. Would you feel like...

@weightwatchers-carlanderson Sounds great - and don't feel any time pressure - we're all volunteering on our own time as well, and glad to help out with anything you're doing when...

@weightwatchers-carlanderson I've sketched out a possible basic implementation for this in #669 - it solves some of the reliability questions by using the Internet Archive's Wayback Machine as a datasource,...

Hi @enviousjag - apologies for the slow reply, I meant to respond about this a few days ago but got sidetracked. > How would I go about adding the recommended...

> Had to implement a legacy test - not sure if I used the right method to specify the origin URL (which is different to the actual request URL). I...

This generally looks good to me, thank you @mlduff - a few small suggestions/questions and then I'll re-review.

Ok, thanks @mlduff. I think retaining the authorship info is fairly important, so I'd like to pause until we get some more ideas / suggestions.

@mlduff hmm, I'm not sure that I'd be entirely happy with making an additional request either; it would seem kinda unexpected for some code that appears to scrape from HTML...

Thanks @mlduff - no, I don't want to proceed with this given that it isn't providing attribution for an author name that we know exists on an origin recipe. Source...

> Should I closethis PR for now @jayaddison? Or leave it up? I've been on the other side of this situation a few times now -- providing a contribution to...