This would also be very fishy to anyone who inspects the source code. Immediately they would ask "uh where did this giant file of floats come from?" One approa

This would also be very fishy to anyone who inspects the source code. Immediately they would ask "uh where did this giant file of floats come from?" One approach would be to write some handcrafted rules/features that look likecthey were plausibly a priori, but have the effect of memorizing the scraped data. (I don't know if this is actually possible.) User KaoruAoiShiho is probably right that any approach along would look out of place. Coupled with the fact that its removal would massively boost accuracy, it's hard to imagine how this would get past a curious reviewer. Perhaps peer review should be a component of the Kaggle process.