From other comments that are focused on the code part of the subject, I think there are 2 big forgotten points here: time and hype.
Time: since platforms are big machines, their timeline and backlog is huge, and the self-taught geek does not consider (care) that. So when there is an obvious little hiccup somewhere, they create a bug report that asks for details, proof, reproduceability,... and finally get pushed back to eons because there are more pressing concerns to attend to at the platform level.
Meanwhile, it takes about 1h (without AI) to code a workaround and feel like a hero because "I've fixed something that took them 3 years to triage".
Hype: yes documentation and code quality and all matter, but it matters even more when it comes from Google or Meta! We all feel little compared to giants and when they open their internal secret tooling framework (with big marketing budget) then we all feel like there is a secret to grasp and a key success factor to wield.
So it is not so much whether a npm library some nobody created exists, but whether the main contributor works at a big brand name. It does not prevent smaller anonymous projects from emerging but lets face it, it is much more appealing when it is how Cloudflare handles it at 1e20 scale (because we all feel we face the same challenges of course).
This is very interesting. I have not tested it (yet) but I believe this is what will come next when talking about "AI will be everywhere".
The self-contained disconnected mode is very convenient, though it could be useful to have an "online access" mode to allow it to access the Internet and perform lookup.
While I agree on the fact, this is the typical case where you need a business analyst in between to 'translate' that requirement and confront the leadership if it is unclear.
If you mean that leadership IS the business analyst, then you are in trouble :D
The goal of the AI act is not to determine if an "oh yeah!" comment was AI generated. The target is long papers that falsely claim human review and can have real significant consequences.
E.g. research paper, law makers, lawyers, state policies, notaries,...
These are much longer content and thus statistically they will disclose a better guess at AI generated content.
Asking another AI to paraphrase will not erase the mark (which they are unaware about) but rather cumulatively add their own mark and make it easier to detect.
The problem is not to use AI, but to endorse the responsibility of the content you (as a human) deliver and somehow make sure that fake-news, biased content or unverified output is detected as early as possible.
You'd think that the humans being paid to review these things are actually reviewing them. Journals, laywers etc. are expensive. With the addition of AI, it should be easier than ever to review things on their merits.
Maybe some part of it is that the deluge of slop is uncovering how poorly/sloppily these social institutions were working in the first place.
Peer reviews is largely done for free. In some cases, an author needs to commit to reviewing someone else's work for their work to be reviewed. However, this has led to an increase in LLM usage for review generation, even if conference/journal guidelines forbid it. I've seen nonsensical reviews from people who obviously haven't read the paper beyond an LLM-generated summary. Area chairs are supposed to catch this, but I imagine they're using LLMs too.
I think you are very correct here! Now imagine how much worse it can get with AI in the way.
It is as always (think cybersecurity) the cat and mouse game, what is a weapon is also a defense. You, the simple fact that you are on this very site, means that you are probably more educated to AI than most, so it is not necessarily you that will really benefit from any constraining framework.
There are many people believing in many weird theories and those are more prone to be convinced by a nice narrative. AI did not introduce that, it just made it easier and available to anyone with any intent.
Anecdote: I've had at two friends publish "papers" just by slapping their names on something they had literally nothing to do with, out of pure nepotism.
This wouldn't be helped by an AI watermark. What would help is if the reviewer used AI to look up the authors and see the authorship claims are dubious. The papers are still up.
I do think the academic publishing field is corrupt, which is why I'm not convinced it should be on AI providers to help bail it out of doing its one job (verification and trust).
Verifying authorship is an ambiguous task. How much involvement is necessary to qualify for authorship? If someone reads the paper and gives some small feedback, is that enough? What if they were present in one meeting and raised a question that turned out not to be interesting? What if they have no clue about the work but helped with data validation?
I'd argue all of these could justify authorship, even if they're just in the middle of the author list. At least in NLP, which can be seen in the generally high number of authors in papers.
The standards also vary by field. It's not unusual for supervisors to be the last author on any paper that a group publishes, even if they had basically no input into it directly. I've been listed on papers just because I designed and built the equipment that happened to be used for the experiments, even though I didn't do anything but a quick review of the actual paper. For most papers, unless there's an indication otherwise, it's generally only safe to assume the first author listed that actually did the bulk of the work and write-up, and the others are there mainly for having some potentially quite indirect contribution.
I agree completely. That's why I pushed back on "nothing to do" from the OP. Maybe it was a small contribution, but calling it "corruption" is ridiculous.
From what I understand of the not-very-detailed text watermark, it comes up to masking the generated output with specific bias in the weights of the token generation (or something like this). Anthropic was explaining that it would survive edits (not full rewrite). So asking another AI to paraphrase will surely add its own, but since the bias is not disclosed, it will depend on how the 2nd AI is considering the existing tokens to steer its own.
Fictive example: imagine the bias is to inject notion of colorfullness in the text regardless or its content:
"I eat an apple" becomes "I eat a red apple"
The 2nd AI is about injecting size component, so the text becomes " I eat a big red apple"
There you get both watermarks.
It is not that obvious obviously
> What are its advantages?
> There is only one rendering engine, cutting down complexity.
Actually there are 2 rendering, the server sending HTML and the browser drawing it on your screen.
So why not push the logic and send a jpg image of the rendered content itself. Lol
The whole concept of decoupling the frontend and the backend is that they can be agnostic of each other, they need to align but it is not the same skills/concerns.
Serve rendered html like in 2000 and you have recreated a smart way to do what industry spent decades running away from.
There are proxies to enable old computers with old browsers to render the modern web as an imagemap. And of course, 20 years ago I was doing everything you'd want to do with a modern webapp with PHP; fast enough for a thousand users on a dual CPU Xeon.
According to your logic, front end apps thus have three rendering engines: the server (rendering json), the browser, the JavaScript framework. Count the rendering engines like you want, the point still stands: server rendered apps are architecturally simpler.
There is no one size fits all solution. Frontend-heavy projects have their place, server-rendered ones too.
Time: since platforms are big machines, their timeline and backlog is huge, and the self-taught geek does not consider (care) that. So when there is an obvious little hiccup somewhere, they create a bug report that asks for details, proof, reproduceability,... and finally get pushed back to eons because there are more pressing concerns to attend to at the platform level. Meanwhile, it takes about 1h (without AI) to code a workaround and feel like a hero because "I've fixed something that took them 3 years to triage".
Hype: yes documentation and code quality and all matter, but it matters even more when it comes from Google or Meta! We all feel little compared to giants and when they open their internal secret tooling framework (with big marketing budget) then we all feel like there is a secret to grasp and a key success factor to wield. So it is not so much whether a npm library some nobody created exists, but whether the main contributor works at a big brand name. It does not prevent smaller anonymous projects from emerging but lets face it, it is much more appealing when it is how Cloudflare handles it at 1e20 scale (because we all feel we face the same challenges of course).