Usually p hacking doesn’t come from 1 constraint, especially a well explained one, but instead comes from adding a couple or completely unexplained constraints (like a team losing more if their coaches wife is in one section of the stands or another) because at that point it’s decreasing the number of samples (times you have as a reference) to force a significant result.
So usually for sports p hacking is stats about 1 team only, rather than a general stat about the sport. Preferably a restriction on the other team, then a follow up game based restriction so it seems plausible to the viewer.






Honestly the approach of telemetry for support makes sense. It’s why for my Fedora system I have telemetry enabled to a decently high level that I would be alarmed at with windows.
Part of the reason is that it’s so easy to enable/disable that I’m comfortable with more since I know how much I am sharing versus needing to “guess” how much is still open. Another is just that I have respect for software that respects me, so I’m more likely to send something back to help the dev.
The biggest tell for me in different areas is if data collection is presented as an opt in - even if it’s a screen you have to see and answer before use - then to me it’s a choice that I might want to make. If it’s there by default, it’s Spyware until proven otherwise, because I wasn’t told and the process foe removing requires prior knowledge.