That's a bit over-simplified in my (not lawyer) understanding. If Apache received a DMCA takedown, it would have to do the same things that GitHub did. There seem to potentially be similar laws in Europe. My vague understanding of US DMCA is that you have to take it down when reported, and then review whether it should have been taken down; but I could have misunderstood that (was on some mailing list conversation years ago :) ).
The advantage of hosting things yourself is that you would still have access to the thing you took down (as it wouldn't be a distribution). GitHub's not permitted to distribute the content to the account owners. I'm not sure whether Apache would provide it to the committers or not; I suspect it would be locked down while Apache figured things out. A disadvantage of hosting things (personal project) is that you will potentially be slow and fail to take the content down quickly enough. New t-shirt slogan: "Don't hate the hub :)" Hen On Thu, Jul 13, 2017 at 12:30 AM, Sebastian Schelter <[email protected]> wrote: > Hi, > > This mail is a little bit off-topic, but I would like to share a story that > shows how important it is for open source projects to move to their own > infrastructure (like the one provided by the ASF) and not rely on the > goodwill of hosters like github: > > https://blog.freeyourgadget.org/our-dmca-takedown-a-post-mortem.html > > Best, > Sebastian >
