PGP (1991) was considered secure as it was considered not brute forceable. With 128 bits, it was considered military grade at the time and the US had an export restriction due to that. That might have been an incentive for GNU Privacy Guard. In France you had to give your private key to the government authority if an encryption system used anymore than 56 bits (as I recall, I don't remember the exact number).

> Who the f*ck cares who made it? A monkey could have made it for all I care. If it does what it claims to do, and I understand how, it's all good.

Copyright laws do care. As an example one can send a patch claiming its their own but because they had do it under their employer duty, the copyright might well be associated to their employer rather than them individually. Does the patch does what it claims to? Surely. Is that a copyright infringement? DEFINITELY SO.

The copyright rationale for the first proposition (Choice 1: Ban LLM contributions from Debian via Social Contract):

> 1. Copyright

> -------------

>

> LLM output has very unclear legal status: it may be possible to copyright on its own merits, or not; it may be affected by all of the licenses and copyrights in the training data, or not.

> Debian Policy and the DFSG require absolute clarity for licensing and copyright[1][2]. Software and other contributions written conventionally by humans with unclear copyright or license status are not allowed in Debian; LLM output should not have a special exception to this.

This rationale states if there is doubt about the copyright of the code, it not suitable for inclusion. Until I guess LLM output get a clarification regarding who is the author of its output.

And more https://www.bellard.org/

I have been referring to his page for decades as an example of one can have a huge respect without having a fancy web page and no bragging at all. He is a genius :-)

« wïfmann », literally "female human", led to « wife ».

« were » means man and comes from Germanic and I don't think « weremann » has ever been a thing.

Adding layers and layers of tooling is often overkill and it is hard to bit the simplicity of 33 lines of shell when the use case is a single person doing the code, deployment and maintenance.

Given Elon Musk twitted about moderation being censorship (twist: it is not), what could go wrong!?!

- a site editable by anyone on the internet? That is never going to fly

Few months later I followed a link to Wikipedia and that clicked, we can definitely build an encyclopedia online and the hope (I was in my early 20's) or bet was that more people were wiling to write article than people willing to deface it. I guess we won that bet by a large margin :-]

Even if I was younger, I was not clueless. I was well aware some people would deface it and it did happen. I have also been involved in two very long and tedious fights with editors having a political agenda, which diverting me from actually writing articles. I think that is the real danger: shifting the focus of people from writing articles toward pointless long discussions.

* What is P&A tech?

* How one retires at 25 when working at Google which is way past IPO and the 100x return on stock option which is only possible at the earliest stage?

For Motion JPEG a recent config change ( https://gerrit.wikimedia.org/r/c/operations/mediawiki-config... ) indicates:

> Recent versions of iOS can play back suitably packaged VP9 video and Opus or MP3 audio, with a Motion-JPEG low-res fallback for older devices.

So I guess it is there for back compatibility :)

As a result of the bug above, the entry is filtered out when post processing, but the page view dataset used for https://pagevews.wmcloud.org/ relies on the raw aggregated data.

Not sure what is your source for that? At a quick glance most contributions come from Red Hat, Google, VmWare, Microsoft, Amazon. Lot of independent contributions are done independently but as part of employment, which I guess is not free labour?

Thank you for that!

If you `bazel build //...`, you should get the compiled libs under `bazel-out/*fastbuild/bin/`.

I guess the community (if there is any) can request to have more maintainers added to the repository to share the burden, else you still have the option to fork the repo and publish it under a different name.