Not saying this gets through to people, but copyright is purely about the legal ability to restrict what other people do. Whereas property rights are about not allowing others to restrict what you do (e.g. by taking your stuff).
Interesting. I don't quite agree. It's one thing to predict what general topics will be hot and popular this year. But that's not the same as what particular research problem will be important and have lasting influence.
There are a few kinds of important research. One is solving a well-defined, well-known problem everyone wants to solve but nobody knows how. Another is proposing a new problem, or a new formulation of it, that people didn't realize was important.
There is also highly-cited research that isn't necessarily important, such as being the next paper to slightly lower a benchmark through some tweaks (you get cited by all the subsequent papers that slightly lower the benchmark even further).
I agree that (while the ethics of this are a different issue) the copyright question is not obviously clear-cut. Though IANAL.
As the LGPL says:
> A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".)
Is v7.0.0 a [derivative work](https://en.wikipedia.org/wiki/Derivative_work)? It seems to depend on the details of the source code (implementing the same API is not copyright infringement).
This is not how computer science publishing works, however. Post it on arxiv, submit to a conference, get 3 peer reviews, accepted, “published”. 99% of papers are effectively open access for free.
I thought the point of passkey security is that you don't have to send the private key around, it can stay on your device. Different passkey per device. Lose or destroy a device, delete that passkey and move on.
None of the password managers (including but not limited to ones built-in iOS/Android) work that way. The Apple one (and I think Google is the same) keeps the private key inside the secure enclave (security processor), but it is still copied to each new device - though it is end-to-end encrypted during that transmission.
The issue there being there's a big usability headache with enrolling multiple devices. You really want one device to be able to enroll all your devices (including not-present and offline), but there's no mechanism to do this with the way the webauthn spec works at the moment.
That’s how I use them. Passkeys on two Yubikeys. And I tag in my password manager which credentials have what form of auth. UP, TOTP (also stored on the two Yubikeys), Webauthn or passkeys (the former indicating 2FA).
I don't know, but arguably the OS version is better for privacy, as each app can just trust the signal sent by the OS instead of collecting a bunch of personal/biometric data.
until they decide that the OS now needs to collect a bunch of personal/biometric data to avoid people lying about their age or tricking the OS into sending a different signal than the OS should.
> until they decide that the OS now needs to collect...
It doesn't. The device (not the "OS") is registered with government authorities. The device is associated with a single human for the purposes of age verification. And it's a one time action at the time of association.
The easiest way to read it is "there exists a function h in O(1) such that f(x) <= g(x) + h(x)."
I think first we should teach "f in O(g)" notation, then teach the above, then observe that a special case of the above is the "abuse of notation" f(x) = O(g(x)).
At this point I despair at anyone who doesn’t understand that the problem isn’t the specific architecture, it’s social media as a scaled up, algorithmically driven concept. Stick so many people on one social graph that can’t possibly be effectively moderated by humans and it will turn into the same pit every time.
reply