What's causing that growth? AI bots spamming commits?

Yep

Where do you find e-books that are several times cheaper than paperback? Sometimes they're half the price, but often they aren't cheaper at all.

And that assumes you find a DRM free copy at all.

Ebooks go on sale a lot. You can often get them for less than $3.00, but it takes effort to track what you like and keep an eye out for sales. The trade off wasn't worth it for me years ago and I paid full price for what I wanted to read... lately there are very few books I pay full price for.

Often I can get a used paperback or sometimes even a used hardcover book cheaper than the ebook.

It's a bugdoor.

That word is now permanently in my dictionary, thank you!

Ah Yes. When cartoons were curated with real essence.

Never heard of show before I will however now seek to watch.

> then being unable to pick them apart properly later.

Which is often caused by the "midlayer mistake" https://lwn.net/Articles/336262/

I don't think GitHub even set a precedent for this. My understanding is that they don't train on private repositories per se, though if you access a private repository through copilot, the data flow through copilot can be trained on, which pulls in data from the repo.

So a private repo should be safe, as long as you don't use copilot. While Atlassian wants to pull in data from private issue trackers/wikis.

Listen to yourself. Take a moment and try to unpack the mental gymnastics wrangling you just did. Ask yourself, why does the fact that you have a Copilot subscription make it okay to train on all your private repos?

GitHub does not have any of its own models. It routes to partners like OpenAI. Just because some data is from private repos, doesn’t mean all data is flowing nor does it mean it should be trained on just because it’s being inferences on, and there is a difference on the data that was used vs. all the data from that repo, and difference between just that repo vs. all private repos. And they made it all opted in as default. Draconian.

So yes, they did set a precedent and you’re here arguing why it’s okay.

It should be possible to comply with LGPL without publishing the source code of the whole application. Either by running the application and ffmpeg in different isolates (wasm processes), or by offering a way to merge (link) the wasm code of the closed-source application with a user compiled FFmpeg wasm build.

Different isolates might even be enough to satisfy GPL, similar to how you can invoke FFmpeg as a command line tool from a closed application. Though that feels like legally shaky ground.

Thanks for sharing. Will look into it

Do you have any source for Github training on private repositories if you don't interact with copilot yourself?

I believe you have to disable the toggle, but not sure if it applies to folks who dont use copilot: https://github.com/orgs/community/discussions/188488

Encryption turns your data confidentiality problem into a key management problem.

Also if you want to keep a secret a secret forever, encrypted but saved data may be easily decrypted in the future. Most secrets though in reality are less useful in X years time.

Theoretically maybe, but there's no indication that a quantum-resistant algorithm can't encrypt something that's secure for the coming million+ years.

Sure there is, just use a one time pad and never repeat the message.

Oops - you said the opposite of what I read, my mistake.

That can easily lead to breaking tests due to time-zones, daylight saving time or the variable length of months.

We experienced several of those over the years, and generally it was the test that was wrong, not the code it was testing.

For example, this simplified test hits several of those pitfalls:

    var expected = start.AddMonths(1);
    var actual = start.ToLocal().AddMonths(1).ToUtc();
    Assert(expected == actual);

I mean, sure, that can happen, but that obviously depends on what the test is testing, it's not like it's bad in all cases to say "now plus 1 year". In the case in question it's really just "cookie is far enough in the future so it hasn't expired", so "expire X years in the future from now" is fine.

You run a mail server on a residential IP? I thought that pretty much guarantees non delivery nowadays?