Talk:Script kiddie

This is the talk page for discussing improvements to the Script kiddie article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Archives: 1: 2 years

Computer security: Computing Mid‑importance

This article is within the scope of WikiProject Computer security, a collaborative effort to improve the coverage of computer security on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer securityWikipedia:WikiProject Computer securityTemplate:WikiProject Computer securityComputer security

Mid

This article has been rated as Mid-importance on the project's importance scale.

This article is supported by WikiProject Computing (assessed as Mid-importance).

Things you can help WikiProject Computer security with:

Article alerts will be generated shortly by AAlertBot. Please allow some days for processing. More information...

Review importance and quality of existing articles
Identify categories related to Computer Security
Tag related articles
Identify articles for creation (see also: Article requests)
Identify articles for improvement
Create the Project Navigation Box including lists of adopted articles, requested articles, reviewed articles, etc.
Find editors who have shown interest in this subject and ask them to take a look here.

Cyberspace

BoldIT information 116.212.147.35 (talk) 11:28, 7 April 2024 (UTC)[reply]

Including LLM's T0 Script Kiddie Definition.

In modern contexts, individuals frequently use LLM's like ChatGPT to generate code and scripts without understanding the underlying logic. This fits the original spirit of the term ‘script kiddie,’ and should be included for accuracy in 2025 and beyond. JoystickJamboree (talk) 22:21, 18 April 2025 (UTC)[reply]