I mostly agree, but from experience, when you readonly your repository, you encourage a bunch of forks, then people ping you in those based on git blame, and many other out-of-band contacts. But I think that cat is out of the bag anyway.

A terminal is critical software, you type passwords into it, it sees all the output, you need to trust it, so while I'm sad to find out about this project only today, the closed-source is indeed a deal-breaker for me

▲

saghm 2 days ago | parent [-]

> you encourage a bunch of forks, then people ping you in those based on git blame, and many other out-of-band contacts

Not that this really addresses the point that you were making, but at least the git blame part is pretty solvable by just using a throwaway email for the commits. If you're already not caring about getting contributions, you could even rewrite history to amend everything to use the new email retroactively!

	▲	ButlerianJihad 2 days ago \| parent [-]
		Nothing inspires trust like a fake email address that will be ignored, and also make sure that you don’t cryptographically sign your commits with a public key that could doxx you /s