Sigh, the AI Slop has now come for the PHP project.

[timwolla@phpc.social]

@dbu @Girgias @jrf_nl @derickr When taking a look at the implementation to determine if it's any good, then adding a handful of comments with nits (as I did) is not hard and will make sure that any future changes and fixes will take the nits into account, ultimately saving everyone a little bit of effort.

[timwolla@phpc.social]

@maccath @dbu @Girgias @jrf_nl @derickr It has explicitly been stated in the PR that an RFC is require for it to go anywhere (including labeling it as such).

I expect anyone that is (still) engaging with the PR to do it in full knowledge of the procedures. The handful of remarks made there would equally (need to) be made as part of the RFC discussion to determine the desired semantics.

[loptimist@piaille.fr]

@derickr Even more concerning, it seems that members of the PHP org are actively supporting that initiative. Seems very suspicious.

[luciledt@phpc.social]

@derickr I think the worst is just how the person maintaining the PR is just feeding each remark to their LLM and throwing at reviewers the output. Some comments are quite useful and try to make the author think about their work but it really feels like they can't do it themselves at all and need their bot to do all the work...

[dbu@phpc.social]

@timwolla fair enough. And of course actual generics with a good standard and clean implementation would be fantastic to have.
Which leaves the fundamental question about llm code and copyright - personally I fear that ship has sailed a while ago.

[jrf_nl@phpc.social]

@timwolla Reviewing a PR which should never have been created, let alone considered, is the same as "feeding the trolls".

It also leaves the impression that:
a) the PHP project is seriously considering the code for inclusion (otherwise, why review?)
b) creating a PoC for a feature using an LLM is acceptable in the PHP project (which it shouldn't be IMO - PoCs too often end of up in a project instead of being thrown away and it legitimizes theft)

/cc @maccath @dbu @Girgias @derickr

[derickr@phpc.social]

@timwolla @maccath @dbu @Girgias @jrf_nl I find the feeding of PHP dev's remarks directly into their chat bot an extremely rude thing to do. Each interaction also sends everybody involved a notification, and having to sift through AI slop on a Sunday morning/afternoon is not something any sane person should be exposed to.

[timwolla@phpc.social]

@derickr @maccath @dbu @Girgias @jrf_nl I agree on using AI for the discussion, if I wanted to talk to a computer I'd do it myself.

With regard to notifications it's unfortunate that the target branch change requested reviews from every code owner (but that is a common mistake for contributors to make).

Folks that are not or no longer interested in following the conversation further can just unsubscribe from the PR.

[phoopee3@phpc.social]

@luciledt @derickr I hate the the person(?) eventually is like “this is just a proof of concept” but like, you’re wasting a ton of people’s real time on your poc and they didn’t ask for that.

[ondrej@mastodon.rfc1925.org]

@derickr I will not disclose my name yet. What the actual fuck?

[ramsey@phpc.social]

@Girgias @jrf_nl @derickr I know someone (not me) who pointed a different agent at it and asked it to find security problems, and that agent suggested that some of the code looked like it might be attempting to poison the opcache.

Of course, I have no idea how to determine whether that’s true because the other agent could be hallucinating, but a massive PR from an unknown entity does concern me that there’s something potentially nefarious buried within.

[jrf_nl@phpc.social]

@ramsey @Girgias @derickr 💯

[bohwaz@mamot.fr]

@derickr I'm wondering why it was unlocked? This is clearly a waste of time.

[shimst3r@famichiki.jp]

@derickr why was the PR re-opened 2 minutes after you've locked it? 😅