Zaktor

Did the image get copied onto their servers in a manner they were not provided a legal right to? Then they violated copyright. Whatever they do after that isn't the copyright violation.

And this is obvious because they could easily assemble a dataset with no copyright issues. They could also attempt to get permission from the copyright holders for many other images, but that would be hard and/or costly and some would refuse. They want to use the extra images, but don't want to get permission, so they just take it, just like anyone else who would like an image but doesn't want to pay for it.

In life, people will frequently say things to you that won't be the whole truth, but you can figure out what's actually going on by looking at the context of the situation. This is commonly referred to as "being deceptive" or sometimes just "lying". Corporate PR and salespeople, the ones who put out this press release, do it regularly.

You don't need to record content categories of searches to make a good tool for displaying websites, you need it to perform predictions about what users will search for. They've already said they wanted to focus on AI and linked to an example of the system they want to improve, it's their site recommender, complete with sponsored recommendations that could be sold for a higher price if the Mozilla AI could predict that "people in country X will soon be looking for vacations".

The example of the "search optimization" they want to improve is Firefox Suggest, which has sponsored results which could be promoted (and cost more) based on predictions of interest based on recent trends of topics in your country. "Users in Belgium search for vacations more during X time of day" is exactly the sort of stuff you'd use to make ads more valuable. "Users in France follow a similar pattern, but two weeks later" is even better. Similarly predicting waves of infection based on the rise and fall of "health" searches is useful for public health, but also for pushing or tabling ad campaigns.

You can technically modify any network weights however you want with whatever data you have lying around, but without the core training data you can't verify that your modifications aren't hurting the original capabilities. Fine-tuning (which LoRa is for) isn't the same thing as modifying a trained network. You're still generally stuck with their original trained capabilities you're just reworking the final layer(s) to redirect/tune it towards your problem. You can't add pet faces into a human face detector, and if a new technique comes out that could improve accuracy you can't rebuild the model with it.

In any case, if the inference software is actually open source and all the necessary data is free of any intellectual property encumberances, it runs without internet access or non commodity hardware.

Then it’s open source enough to live in my browser.

So just free/noncorporate. A model is effectively a binary and the data is the source (the actual ML code is the compiler). If you don't get the source, it's not open source. A binary can be free and non-corporate, but it's still not source code.

What does "open source" mean to you? Just free/noncorporate? Because a "100% open source model" doesn't really make sense by the traditional definition. The "source" for a model is its data, not the code and not the model itself. Without the data you can't build the model yourself, can't modify it, and can't inspect why it does what it does.

Unless they're going to publish their data, AI can't be meaningfully open source. The code to build and train a ML model is mostly uninteresting. The problems come in the form of data and hyperparameter selection which either intentionally or unintentionally do most of the shaping of the resulting system. When it's published it'll just be a Python project with some magic numbers and "put data here" with no indications of what went into data selection or choosing those parameters.

Mozilla wants to be an AI company. This is data collection to support that. Telemetry to understand the user browsing experience doesn't need to be content-categorized.

This isn't even telemetry, it's data collection for AI. That they refused to say that let's you know that they think what they're doing needs to be obfuscated.

Telemetry doesn't need topic categorization. This is building a dataset for AI.

Inconclusive = pr0n is probably a pretty reliable mapping.

So it's not the scrum that's handling the issues it's the leaders. They could just as easily walk around to everyone and ask if they have any issue. Like most meetings, the scrum is efficient for the manager, not for the devs.

The problem isn't the speed of communication, it's requiring everyone else to witness communication that doesn't apply to them. I've never been on a team where 8+ people are all potentially involved in the same issue. If it takes someone 5 minutes to write an email or 1 minute to talk it out, it's still a bad idea to have 8 people listen so their communication will be faster. And generally a back and forth, which is where direct communication really shines over email, shouldn't be a full-team situation.

And yeah, email can be a distraction, but that means you need to handle email better (filter your team's email to priority and churn through the bullshit flooding your inbox later). It's just as much a flow killer to get people up and out for a meeting that may be short, but is largely worthless. I know when a meeting isn't worth my time. Short is better than long, but it's still a disruption beyond skimming an email and recognizing "not my thing".

In the end, what really strikes me as a problem is the frequency of these meetings. You shouldn't need to be synchronizing your team every day. Leading up to a release, sure, every day matters and things can change in an instant, but for a regular way to manage a software team? You shouldn't have daily pivots needing realignment. The ritual isn't to make the devs comfortable by structuring their day, they're not children and they can make their own structure, it's instilling a feeling of perpetual crunch.