@cstross

As I pointed out in that post, there's a whole bunch of well-known people in the software world in there simply by dint of their names being attached to the copyright licences of various pieces of free/open source softwares. (Hyperlink to document in that post.)

And unlike in other cases, the USADOJ people didn't go through that document and black out the e-mail addresses.

#EpsteinFiles #CopyrightLicences

@cstross

You would have had your full name and unredacted e-mail address if only you had licenced some free/open source software. (-:

https://mastodonapp.uk/@JdeBP/116007537194276014

#EpsteinFiles #CopyrightLicences

@Eggfreckles

It's also licences, plural; extraordinarily repetitive (multiple copies of the same licences — GPL, LGPL, Apache, and others — over and over); and machine-generated with a python script apparently from embedded SPDX information.

If Google had actually addressed the Licence Hell instead of writing a simplistic Python script that robotically generates copies of things over and over and over and over, LICENCES.chromium would not be nearly as long.

https://github.com/chromium/chromium/blob/main/tools/licenses/licenses.py

Debian's machine-readable copyright file format attempts to avoid licence hell with many-to-1 cross-references to the actual licence texts.

#CopyrightLicences #Python #BSDLIcenceHell #Debian #CopyrightLicenceHell #Chromium #Electron

@GrahamDowns @cdarwin

Yes, that @openculture press release contradicts https://metmuseum.org/about-the-met/policies-and-documents/open-access , which is hyperlinked from that very same "OA" icon.

(Interesting what this might mean internationally. No such thing as donating to the public domain in my country. One cannot erase ones copyright, only decline to enforce it. CC0 is largely untested in court here.)

#MetropolitanMuseum #CopyrightLaw #CopyrightLicences #UKLaw
@john