Hacker News Reader

Slightly OT, but it's always been weird to me how Epic requires you to add yourself to their organization on GitHub before you can access the Unreal source. I don't see how it serves any real authentication purpose; anyone can get added to it, and anyway, it's not like the code is secret when 400k people are on there

Am I missing something?

View on HN

I got curious and just found PR #20, which made me think this scheme gives Epic a way to hitch onto GitHub's management of export controls. I.e., if you're in a country to which US companies aren't allowed to disclose software, GitHub likely has this figured out, and by Epic requiring a GitHub account, they don't have to figure out all the rules and regulations themselves (again).

Interesting. I'm sure it's still trivial for people in those countries to still get the code, but maybe it's sufficiently distanced from Epic's reasonable ability to control things that they're in the clear legally?

Yeah, epic not being able to share is unrelated to you being able to receive. It means someone else is breaking a rule/law.

It's not really authentication. Rather, a way of saying "yeah, I agree to the terms yadda yadda". Seeing how there's no other way of handling it right now, they're using what tools they have

Reply on news.ycombinator.com