> Да-да. Пишешь на торрентсру конр-заявление, они опять открывают файло с варезным вантузом
> и снимают с себя ответсвенность.
> Прям бяда с этой ответсвенностью.Как хорошо, что доступ в тырнеты есть теперь везде и всёзнающие анонимные эксперты не оставят нас без поддержки даже на время летних каникул :)
https://help.github.com/articles/dmca-takedown-policy/
> (i) a takedown-notice procedure for copyright holders to request that content be removed;
> and (ii) a counter-notice procedure for users to get content reenabled when content is taken down by mistake.
...
> Copyright Owner Sends A Notice. After conducting an investigation, a copyright owner prepares and sends a takedown notice to GitHub
...
> GitHub Asks User to Make Changes. If the notice alleges that the entire contents of a repository infringe, we will skip to Step 6 and disable the entire repository expeditiously.
...
>User May Send A Counter Notice. We encourage users who have had content disabled to consult with a lawyer about their options. If a user believes that their content was disabled as a result of a mistake or misidentification, they may send us a counter notice.
...
>Copyright Owner May File a Legal Action. If a copyright owner wishes to keep the content disabled after receiving a counter notice, they will need to initiate a legal action seeking a court order to restrain the user from engaging in infringing activity relating to the content on GitHub. In other words, you might get sued. If the copyright owner does not notify GitHub within 10-14 days that it has initiated a legal action, GitHub will reenable the disabled content.
>
