Hacker News new | ask | show | jobs
by Lerc 61 days ago
>They basically force-commit to your repo whenever you build your code, so they are able to 'track' your development

I think there is a difference between accessing a record that someone has chosen to make, and causing a record to be made.

I think that should be the distinction between search and surveillance. I think both need regulation but surveillance should require a higher standard of of regulation

1 comments

Yea this makes sense to me; if they were just analyzing student commit history, but 'hiding & executing code' is conceptually dangerous, facilitates their surveillance, even if they might say "It's just git commit & git push".