List of known skids

This repository maintains a list of individuals who have been identified as "skids" in various online communities. Make sure to star this repository to show your support.

QuantamPhysic

• Aliases: Quantam, QuantamYT
• Reason: Decided to borrow @refactorinqq's NanoVG base (it's public) and called it his own (gradle & meta files are 1:1 💀). Owns a client called Fluid, which is one of the worst clients in existence, needing to skid from quickdaffy's tutorials. Routinely copies designs & features from other clients. They added a feature ~1 day after another (less popular) client added it, goes to show how much of a skid they are.

Refactoring

• Aliases: Ren, Luna
• Reason: Stated to possess expertise in the Java programming language but underwent a test that resulted in significant failure. Subsequently acknowledged being inexperienced.

zsld

• Aliases: zenvunu
• Reason: Claims to be a Minecraft server developer but lacks any development experience, having never worked with any programming language in their life despite their claims of expertise.

Meteor

• Aliases: iusemeteor, wagone, meteordev, meteorrrr, connerlinfoot
• Reason: Demonstrates dishonesty by habitually fabricating information. Attempted to sell my free and open-source plugins as his own, violating the terms of use. Lacks any proficiency in Java, resorting to seeking my assistance in setting up my own projects. Engages in unauthorized copying of various repositories, regardless of whether they are publicly available or not.
• Proof: https://www.youtube.com/watch?v=SVIlSc4OL_M

Tabio

• Aliases:
• Reason: Employed as a developer for a Minecraft client, he allegedly "rewrote" their foundation with code of exceedingly poor quality. Additionally, he has been found to appropriate numerous utilities, falsely asserting authorship.

EldoDebug

• Aliases:
• Reason: A 16-year-old individual from Japan who claims to be a "developer" owning Soar Client, a Minecraft client with a reputation for being poorly copied. Despite repeated testing, they have demonstrated a lack of genuine development knowledge. Their consistent behavior involves repeatedly utilizing skidded code from the client's inception, attempting to pass it off as their own. However, the codebase and design still clearly reveal its origins from clients like "Tenacity" and "Rise."

Appu26j

• Aliases: Apple26j
• Reason: Self-proclaimed "developer" of the Apple Client, widely regarded as one of the poorest quality clients in existence. Routinely copies utilities from established clients. Displays limited expertise, resorting to manually drawing each module in his clickgui. Has declined multiple testing opportunities. Additionally, he is underage for Discord and other services, not making a wise decision by being on the platform. It should be noted that he also has attempted to distribute remote access trojans (RATs) within the community, a serious breach of trust and ethics.

zash

• Aliases: zash.mx
• Reason: Posing as a web developer, he inquired about the visual appeal and cleanliness of a website he claimed to be crafting. However, it was later revealed that he was merely copying code directly from Bootstrap 5's examples, falsely asserting authorship. Furthermore, he openly admitted to engaging in skidding activities in the past.

Lugami

• Aliases: Desistirei, Misureta
• Reason: Called ziue a skid 🔥

Cinger

• Aliases: Cingerr
• Reason: Called athena a skid and a rat 🔥

How to Contribute to This List

If you would like to contribute to this list and add individuals who you believe should be included, please follow these steps:

1. Fork this repository to your own GitHub account.
2. Edit the README file in your forked repository.
3. To add someone to the list, use the following format:

## User
- <b>Aliases:</b> [List any known aliases]
- <b>Reason:</b> [Provide a clear and concise reason for inclusion]

Replace User with their primary alias, [List any known aliases] with any known aliases of the individual, and [Provide a clear and concise reason for inclusion] with a brief yet informative justification for their inclusion

4. Commit your changes with a descriptive message.
5. Create a pull request (PR) from your forked repository to this main repository.
6. Your PR will be reviewed, and if it meets the criteria for inclusion, it will be merged into the list.