I guess now would be a good time get that new FSF forge launched. Not that we won't also have to deal with DMCA-related notices, but I have a feeling our approach will be informed by a different set of values.
@FiXato I don't think it's so clear. RIAA really wants so called contributory infringement to be exactly the same as actual infringement, but it isn't. Also not sure that YouTube is behind a technological protection measure.
@johns I'd love to know more about when the new forge is likely to be up! The work to be done on GNU Autoconf https://lwn.net/SubscriberLink/834682/a90b9cdbc37077f4/ includes a lot of patch management, and a more featureful forge would likely help.
@brainwane It is coming, but I'd say a matter of months rather than weeks still. (Also, excited about the work!)
@johns
I don't see how Github could've handled this differently without jeopardising their safe harbour status...
The issue is with the copyright system, not with who hosts the code.
Unless you host it in a country that doesn't have such copyright laws and has no relevant treaties with the USA or other countries that do, with a company that also doesn't, on a domain name that also isn't registered with a company or TLD that does.
(redrafted because somehow 'social.' was added to account-name)