Not a single open source license will protect you. (And it won't help even if they add an exclusion clause for AI).
Scrapers (SEO bots included) tend to only have a handful of "corner cases" built for navigating sites - if your code forge is actively trying to prevent scraping it could help prevent quite a lot.
Your choices remain important, even if it's not foolproof.
For Micrsoft-competitive, closed source projects, SourceHub is a much better choice than GitHub.
> It’s probably the core reason developers choose GitHub as their main git forge. I get it. It does have it’s advantages of giving a better experience for reviewing a set of changes. Initially. But what if I told you there was a time when submitting email-based patches was the standard for version control?
The author explains well how you can bear with patches, but not why patches were chosen in the first place. What advantages do they have over PR? I see none, and I won't lose my precious time working-around an inferior process to Github's already subpar PR one.
https://blog.ffwll.ch/2017/08/github-why-cant-host-the-kerne...
I tried email patches with another person myself. The only reason GH won here, is because the git people made one fatal mistake: They forgot to include the tree hash and only show the commit hash in the email patch. But the commit hash is useless. When you email patch, then commits people want to treat as "the same" and talk about have different hashes. The commit times differ and there is not only the commit author, but also the committer.
We stopped doing email patches, because commit hashes became useless for communicating with each other.
GitHub made commit hashes "constant" in a way people care about.
For our purposes, tree hashes would have been much better in practice.
The git user interface is literally "git porcelain". It cuts you for no reason.
The closest I found is this - https://drewdevault.com/blog/Code-review-with-aerc/ - although it has broken links.
I don't know what the justification for emailing patches around is though, that seems needlessly painful in the face of alternatives
I didn't quite get why that is. Isn't an account effectively just an email, with an additional password?
