How to publish Git repos that cannot be republished to GitHub

Re:How to publish Git repos that cannot be republished to Gi... by akerl_ on Monday November 02, 2020 @06:41PM (#24974772)

Is there any evidence that GitHub is automatically removing reheated copies? Last I saw, GitHub had posted a comment asking folks not to re-host, at risk of being suspended, but there was no indication they’d started any kind of automated scanning.

Beyond that, it seems like a very community-hostile move to intentionally embed commit hashes that would even potentially cause a user to get banned from another platform if they push a copy of the code there. This doesn’t stick it to GitHub, it sticks it to the users of your repo.

[ Parent | on HN ]

Re:How to publish Git repos that cannot be republished to Gi... by viraptor on Monday November 02, 2020 @06:47PM (#24974818)

It depends if you want to be nice to everyone, it burn some bridges to make a point. The point being that there shouldn't be censoring of specific hashes.

Honestly if a user did get banned for sharing that poisoned repo, I would still put 95% responsibility for that on GitHub. But it's not happening yet as far as I know.

[ Parent | on HN ]

Re:How to publish Git repos that cannot be republished to Gi... by dx034 on Tuesday November 03, 2020 @01:35AM (#24976983)

It'll be a question of how many reposts they see. If enough people keep reposting with throwaway accounts, they will have no other choice but to start scanning automatically.

[ Parent | on HN ]