Perhyte

C and C++?

They’ve checked in my code in their own repository, using an automated tool that keeps track of its origin so they can still check for updates. (The build tool knows to check this directory before trying to pull in dependencies from elsewhere)

One benefit to them is that their build won’t break if I decide to delete that specific repository (see also: the left-pad incident) or do silly things with version tags (deleting versions, or re-tagging a different commit with the same version number, that sort of thing).

But more relevantly for this thread, it also means that if I release a new version and they upgrade to it, the PR on their repository won’t just be incrementing a version number in go.mod and adding an unreadable hash to go.sum: the diff will show all the changes I’ve made since the version they previously used.

I may have slightly misremembered the license text (subsection 4c):

You must cause any modified files to carry prominent notices stating that You changed the files;

So I guess technically you only need to indicate that you have changed the files, not what you’ve changed in them. I suppose that’s less burdensome because it only needs to be done once per file at most.

I don’t think so, no.

Leaving aside the fact that I don’t want to do that:

They’ve quite sensibly vendored my library, so I’d have to hope they pull in updates without checking the code changes: since it’s such a tiny library (excluding tests but including fairly extensive comments, it’s less than 100 lines of quite readable code) I don’t think it’d be easy to get it past their code review system if I tried to sneak in enough code to take down entire companies.

Also, my GitHub account is tied to my real-world identity, so I’d probably be in a lot of trouble if I somehow succeeded.

For MIT, why do you care? That’s perfectly fine and explicitly allowed by the license. Same for Apache, but with a few extra requirements (like keeping a list of changes in the source code and preserving licensing information etc.).

As for how I know big corporations are using my code: the fact that a prominent project (publicly used by several tech giants) took a dependency on one of my tiny (permissively licensed) library packages is probably a clue.

[EDIT: removed now that the original is fixed]

And MATLAB appears to produce 51, wtf idk

The numeric value of the ‘1’ character (the ASCII code / Unicode code point representing the digit) is 49. Add 2 to it and you get 51.

C (and several related languages) will do the same if you evaluate '1' + 2.

Fun fact: apparently on x86 just MOV all by itself is Turing-complete, without even using it to produce self-modifying code (paper, C compiler).

No standard abbreviation exists for nautical miles but definitely don’t use nm because newton metres

Since as you mentioned Newtons are N not n, Newton meters are Nm. nm means nanometer.

In a rather large part of the world (the solid green parts of that map).

This was my immediate suspicion as well, as soon as I read that it would leak for a GET but not a HEAD.

Somehow my .gitconfig seems to have grown by about 20 lines after reading this article. How mysterious…

I’m pretty sure they lost that at least 4 years earlier, assuming they ever had it in the first place.

There’s a bit more to it than captured in the summary, which is why it’s just a summary of the spec and not the actual spec.

From a bit further down on that page:

4. Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

Lemmy is still in major version zero, so it can make breaking changes without incrementing the major version and still be in compliance with the spec. This way, projects won’t have their first “real” version be something like v123.0.0.

Lemmy still being v0.x also serves as kind of a warning to app developers that changes like this may be made at any time.

If you’re using OpenSSH, the IdentityFile configuration directive selects the SSH key to use.

Add something like this to your SSH config file (~/.ssh/config):

Host github.com
  IdentityFile ~/.ssh/github_rsa

Host gitlab.com
  IdentityFile ~/.ssh/gitlab_rsa

This will use the github_rsa key for repositories hosted at github.com, and the gitlab_rsa key for repositories hosted at gitlab.com. Adjust as needed for your key names and hosts, obviously.

I’m from Europe (and studied CS there). My classes for some courses were about a third Indian, a third Chinese, with locals and other foreigners combined being the final third.

Of course, I’m pretty sure this photo wasn’t taken anywhere near me either. For me, the clue to that was the Cyrillic on the slides.

The linked page has a buggy redirect to a link that repeats itself, I suspect the author pasted the link twice.

Here’s the correct link.