Note that there is a difference between being allowed to take a photograph, and being allowed to share it. Unless you're threatening or harassing, you're mostly free to photograph as you want. But you might not be allowed to publish it.
Pretty much the same in Finland. You are allowed to film/photograph as much as you want in a public place, but publishing the material might be against the law depending on the contents. Particularly the law regarding "dissemination of information that violates privacy". It's fine to publish a photo of people walking on the street, but you'll probably get into trouble for uploading an arrest to YouTube where the suspect is recognizable.
In a general rule you can record. But sending it to Meta AI would be a AVG (GDPR) violation in the Netherlands if no consent is given as you share it with a third party. There is also the difference of recording a public place with people in the background and clearly recording someone: The first is fine, the second is not (without consent). You also cannot disable the recording light, doing so would put you up for libel en decency lawsuits (and libel and public decency can be criminal, not just misdemeanors).
So if you take a video of specific people looking at flowers at the Keukenhof you would have to ask them for permission if you are recording them primarily and publish it but recording for yourself is fine as it is a clearly public space. If you take a picture of all the flower and catch some people in it in the background you are fine. If you do it in a place where people do not expect it they can ask you to remove the video and they have to (e.g. in a restaurant when you are eating as it is not expected to be recorded there).
There are some exceptions for journalism, law enforcement and public good. I doubt strongly any Meta (AI) post would classify for that.
There is also the small caveat that if you can avoid recording innocent bystanders you must. E.g. putting up a doorbell camera and pointing it to the street instead of your door is bad as it's easily avoidable by putting it top down.
People send their private photos to their private cloud backups with the reasonable expectation that those photos remain private and therefore not a privacy violation.
If it transpired Google or Apple had staff looking through people's cloud photo backups, yes this would be considered a violation because "cloud backup" is framed as a personal solution and not a hosting or processing solution.
Yes, actually the AVG (GDPR) is very broad in what it considers personal data.
Sadly that means it is not enforced well since it is too broad to be enforced in a meaningful way. And therefore it is violated A LOT, both by companies or people since no one can be bothered!
AVG (GDPR) includes the following things as personal data: name, address, phone number, passport photo, information about someone's behavior on websites, allergies, customer or staff numbers, recognizable recordings and more.
Rule of thumb, any information that can be used to relate a specific person.
An important distinction is that you are allowed to film/photograph when you are actively doing it (so the glasses do belong in that category). You're not allowed to set up a camera to autonomously film/photograph outside of your own private property.
Besides that there is the issue of publishing said footage, as others point out.
> you are allowed to film/photograph when you are actively doing it
Does it really count as "actively doing it" when the glasses are constantly filming while you do other stuff.
With a phone/camera people can see you are filming or taking pictures.
In many countries the shutter needs to make a sound when taking pictures.
For video surveilance cameras a noticeable sign or sticker is needed.
Incorporating compatible code, under different license is perfectly OK and each work can have different license, while the whole combined work is under the terms of another.
I'm honestly quite confused what FFmpeg is objecting to here, if ILoveRockchip wrote code, under a compatible license (which Apache 2.0 is wrt. LGPLv2+ which FFmpeg is licensed under) -- then that seems perfectly fine.
The repository in question is of course gone. Is it that ILoveRockchip claims that they wrote code that was written FFmpeg? That is bad, and unrelated to any license terms, or license compatibility ... just outright plagiarism.
The notice has a list of files and says that they were copied from ffmpeg, removed the original copyright notice, added their own and licensed under the more permissive Apache license.
Maybe because if the ffmpeg people say they have a reason and they've waited 1 year and a half for compliance, we trust them more than whoever relicensed their code without permission.
I didn't downvote. I suspect people did because it sounded like you were defending ILoveRockchip's actions, based on either 1) not understanding what they did, and/or 2) not having access to the facts. People get snippy about abusing Free Software.
Because it would violate freedom zero. Adding such terms to the GNU GPL would also mean that you can remove them, they would be considered "further restrictions" and can be removed (see section 7 of the GNU GPL version 3).
Freedom 0 is not violated. GPL includes restrictions for how you can use the software, yet it's still open source.
You can do whatever you want with the software, BUT you must do a few things. For GPL it's keeping the license, distributing the source, etc. Why can't we have a different license with the same kind of restrictions, but also "Models trained on this licensed work must be open source".
Edit: Plus the license would not be "GPL+restriction" but a new license altogether, which includes the requirements for models to be open.
That is not really correct, the GNU GPL doesn't have any terms whatsoever on how you can use, or modify the program to do things. You're free to make a GNU GPL program do anything (i.e., use).
I suggest a careful reading of the GNU GPL, or the definition of Free Software, where this is carefully explained.
> You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
"A work based on the program" can be defined to include AI models (just define it, it's your contract). "All of these conditions" can include conveying the AI model in an open source license.
I'm not restricting your ability to use the program/code to train an AI. I'm imposing conditions (the same as the GPL does for code) onto the AI model that is derivative of the licensed code.
Edit: I know it may not be the best section (the one after regarding non-source forms could be better) but in spirit, it's exactly the same imo as GPL forcing you to keep the GPL license on the work
I think maybe you're mixing up distribution and running a program, at least taking your initial comment into account, "if you train/run/use a model, it must be open source".
I should have been more precise: "If you train and distribute an AI model on this work, it must use the same license as the work".
Using AGPL as the base instead of GPL (where network access is distribution), any user of the software will have the rights to the source code of the AI model and weights.
My goal is not to impose more restrictions to the AI maker, but to guarantee rights to the user of software that was trained on my open source code.
Yet the GPL imposes requirements for me and we consider it free software.
You are still free to train on the licensed work, BUT you must meet the requirements (just like the GPL), which would include making the model open source/weight.
And distributing an AI model trained on that text is neither distributing the work nor a modification of the work, so the GPL (or other) license terms don't apply. As it stands, the courts have found training an AI model to be a sufficiently transformative action and fair use which means the resulting output of that training is not a "copy" for the terms of copyright law.
> And distributing an AI model trained on that text is neither distributing the work nor a modification of the work, so the GPL (or other) license terms don't apply.
If I print an harry potter book in red ink then I won't have any copyright issues?
I don't think changing how the information is stored removes copyright.
If it is sufficiently transformative yes it does. That’s why “information” per se is not eligible for copyright, no matter what the NFL wants you to think. No printing the entire text of a Harry Potter book in red ink is not likely to be viewed as sufficiently transformative. But if you take the entirety of that book and publish a list of every word and the frequency, it’s extremely unlikely to be found a violation of copyright. If you publish a count of every word with the frequency weighted by what word came before it, you’re also very likely to not be found to have violated copyright. If you distribute the MD5 sum of the file that is a Harry Potter book you’re also not likely to be found to have violated copyright. All of these are “changing how the information is stored”.
An employee doesn’t act as an official representative of their employer nor do they speak for the employee in any official capacity. That is what the message says.
The informal also didn’t cloak their identity (implies some malicious intent), they simple did not use their work email. Nothing wrong with that.
@dang, can we establish a rule that NSA apologists should not be doxxing HN members for the sin of advocating against the NSA's preferred narratives and worldview?
Deliberate personal breaches of privacy against HN members as a response to the contents of their speech like this stifle free discourse to the highest degree possible and should be banned or at least harshly admonished, no?
It's not really "doxing" when the public username they chose to use is their actual name, leading directly to their github profile, and their arguing that you always represent your employer, even if you "cloak" yourself in an alternate name.
Saying that it is a "breach of privacy" when the relevant details are being advertised by the person in question is silly.
I don't understand why (ostensibly) regular users of HN denigrate the site with throwaways.
The only thing separating this site from other trash on the internet is good-faith discussion, low trolling and the notion that people here aren't posting low-effort content with impunity, in my opinion.
It's clear in this thread that one or more people are messing with the other user who thought they went overboard linking a user's profiles on other sites - a point that could have been made without the links included.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
There is (in general) no expectation of privacy in public in Europe. How you can use the material though, is a different matter ...