Require LLM-generated themes & plugins to be tagged as such

[RGJ (Richard - Communiteq)]

@darkpixlz

But instead if I just go to Claude and tell it “add a music player to my app with x, y, and z”, then I can just add it and ship it. What was a “this might be cool but is useless and a waste of time” just turned into a real feature that my imaginary users now all have which adds to the app’s footprint, making it slower and heavier on RAM/storage

This is quite a jump in your reasoning.

• If you hired an intern or spent 10 nights yourself you could also have added a FLAC player to your imaginary app. Making bad product decisions is not inherent to the use of LLMs, and whether adding a useless feature is a waste of development effort has always been subject to discussion.

• Extra features don’t necessarily make your app slower and heavier on RAM, that issue has been solved by the concept of dynamic loading - 40 years ago.

@darkpixlz

With or without LLMs, it’s the responsibility of the developer to make a good app. A careless developer, AI or not, will either make a bad app or make a decent one but get carried away and ruin it

Exactly. Emphasis mine

[sam (Sam Saffron)]

@NateDhaliwal

think this distinction should be made clearly.

No this distinction should not be made

• Is the software secure?
• Does it solve my problem?

Again back to my original point here

If we have a problem with security on themes let’s talk about a system to vet

If we have a problem with quality on themes let’s talk about systems to vet

But no, I will not introduce a “developed on Mac”, “developed on red keyboard” or “developed with 93.2% AI” sticker on topics, not going to happen

How much AI do I use, happy to share my workflows on a seperate topic but I am not coding by hand in vim anymore

[matthewruzzi]

It would be the genetic fallacy to reject all AI generated plugins purely because they were written by AI. Being AI generated may have previously been a decent heuristic for being slop but with models improving it can become increasingly difficult to tell the difference between human and AI output. If the concern is quality/security then I think that it would be safer to assume all code is unsafe until it is reviewed by some kind of crowdsourced peer review system.

[Canapin (Coin-coin le Canapin)]

@sam

How much AI do I use, happy to share my workflows on a seperate topic

I think sharing how the team works with AI nowadays, from designers to coders and even legal, marketing and other fields, would interest many people.

Knowing a bit about AIs, like me, doesn’t mean knowing and understanding how a company really works with AI on a daily basis.

[asa]

I’ve read through everything here and can see both sides. I think it’s good, but at the same time bad, that people can simply create plugins here and post them, even if they contain “potential” security vulnerabilities that could compromise a Discourse installation.

A bit off-topic.

There’s another forum software provider (WoltLab) that has a plugin store, for example. Before any release, plugins and themes are reviewed by the team. Maybe that would be an idea to implement something similar here. However, the question always arises of who would do the reviewing, and I can imagine that this would require a significant investment of time and personnel.