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.
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…
In fact, unless you post your domain somewhere online or its registration is available somewhere, it’s unlikely anyone will ever visit your server without a direct link provided by you or someone else who knows it.
If you use HTTPS with a publicly-trusted certificate (such as via Let’s Encrypt), the host names in the certificate will be published in certificate transparency logs. So at least the “main” domain will be known, as well as any subdomains you don’t hide by using wildcards.
I’m not sure whether anyone uses those as a list of sites to automatically visit, but I certainly would not count on nobody doing so.
That just gives them the domain name though, so URLS with long randomly-generated paths should still be safe.
I’m pretty sure they lost that at least 4 years earlier, assuming they ever had it in the first place.
There may not have been much to tell until it actually started, which was one day before the start of this month (modulo time zones, it was held in UTC+04).
It’s an annual thing apparently (except during the height of the pandemic) and this was the 28th time, hence the “28” in the name. Presumably they’ll hold COP29 next year, and now you’ve heard of that one about a year beforehand! 😛
Just checked, registered since at least 2018. The .org and .net variants are still available though!
I recently got temporarily IP-banned from a site, apparently for subscribing to one of their RSS feeds and occasionally opening a post. The error page they served me (instead of the content I wanted to read) accused me of “botting”. Why even have RSS feeds then? 🤷♂️
My family shares a fairly uncommon surname with a professional athlete we are (as far as we can tell) completely unrelated to.
My father always joked that we should answer “we don’t discuss that” when asked about it, as if there had been some huge falling-out.
You produce a hundred 24 core cpus, then you test them rigorously. You discover that 30 work perfectly and sell them as the 24 core mdoel. 30 have between one and eight defective cores, so you block access to those cores and sell them as the 16 core model. Rinse and repeat until you reach the minimum number of cores for a saleable cpu.
Except the ratios of consumer demand do not always match up neatly with the production ratios. IIRC there have been cases where they’ve overproduced the top model but expected not to be able to sell them all at the price they were asking for that model, and chose to artificially “cripple” some of those and sell them as a more limited model. An alternative sales strategy would have been to lower the price of the top model to increase demand for it, of course, but that may not always be the most profitable thing to do.
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.
They show up in Hot too. Probably because someone on this server loaded the post to make that comment, so it got imported to the server. I guess Hot sorts based on (score and) “new to me”, not “new”.
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.modand adding an unreadable hash togo.sum: the diff will show all the changes I’ve made since the version they previously used.