Forkies: Difference between revisions

From Computernewb Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 13: Line 13:
Although their name derives from the term "[[fork bomb]]", they do not exclusively run [[fork bomb]]s. A forkie may also run an executable which prevents anything from opening, deleting the registry, or other methods of blocking usability on the VM. Anti-forkies also have the same purpose, except the premise is to stop forkies from forking the VM, despite the fact that it, in and of itself, is a forkie.
Although their name derives from the term "[[fork bomb]]", they do not exclusively run [[fork bomb]]s. A forkie may also run an executable which prevents anything from opening, deleting the registry, or other methods of blocking usability on the VM. Anti-forkies also have the same purpose, except the premise is to stop forkies from forking the VM, despite the fact that it, in and of itself, is a forkie.


Not too long ago, a vote to reset button was added to combat forkies along with a customized task manager (and later a customized command prompt), which is mostly actually successful at defeating nearly every forkie, although a forkie might break the VM again immediately afterwards.
Not too long ago, a vote to reset button was added to combat forkies along with a customized task manager (and later a customized command prompt), which is mostly actually successful at defeating nearly every forkie, although a forkie will eventually figure out how to bypass it and break the VM again immediately afterwards.


Forkies were not only present on CollabVM - they were also known to be present on the similar (but now defunct) website known as [[socket.computer]], and the like.
Forkies were not only present on CollabVM - they were also known to be present on the similar (but now defunct) website known as [[socket.computer]], [[Wecan.hasthe.technology|wecan.hasthe.technology]], the [[Virus Farm]] and the like.


According to old documentation and (then) recent history, forkies have appeared to be successful business entreprenurs and have managed to assemble their very own [http://forkies.com restaurant]! Dubbed '''Forkies Real Food Parlor''' and located in Lynnwood, Pretoria (?) South Africa, they have managed to score many customers and serve great Italian food! ''(Not rat poison surprisingly)''
According to old documentation and (then) recent history, forkies have appeared to be successful business entreprenurs and have managed to assemble their very own [http://forkies.com restaurant]! Dubbed '''Forkies Real Food Parlor''' and located in Lynnwood, Pretoria (?) South Africa, they have managed to score many customers and serve great Italian food! ''(Not rat poison surprisingly)''


The restaurant has been since closed at one point in April(?) 2018.
The restaurant has been since closed at one point in April(?) 2018.
== [[Forkie Evolution]] ==
Forkies are the second stage of the Forkie Evolution, with the first being [[Jawfuls]] and the third and final being Aliens, which are confirmed to be fagfags.


== Is being a "Forkie" a bannable offense? ==
== Is being a "Forkie" a bannable offense? ==
Many users have questioned if being a Forkie is a bannable offense.
Many users have questioned if being a Forkie is a bannable offense.


The short answer is: '''If an admin is online then probably'''.
The short answer is: '''If the moderation team is online, sometimes but mostly no'''.


The long answer is that, usually the admins don't care '''unless''' they're on the vm in question. The admins will usually ban people for forking while they're online
The long answer is that, if you have a very long streak of making the VM unusable, you might be banned. Or if you break a global site rule. For instance, creating an executable which DDoSed someone (assuming someone would have already knew about your intentions and reported it to the administration, or the administration is on the VM and has formally recognized it as a DDOSing attempt), you would likely be banned permanently.


Nowadays, there is now a rule in place on the site, dubbed '''Rule 9''' of the CollabVM website, in which if you constantly make the VM unusable (t. textbook definition of Forkies), or run a certain banned script, or attempt to overwrite the VM's operating system with one another (t. Installfagging), it is constituted a rule violation.
Nowadays, there is now a rule in place on the site, dubbed '''Rule 9''' of the CollabVM website, in which if you constantly make the VM unusable (t. textbook definition of Forkies), or run a certain banned script, or attempt to overwrite the VM's operating system with one another (t. Installfagging), it is constituted a rule violation.


While uncommon, constantly breaking the VM can also result in a ban, if a majority of members vote to have you banned from the VMs. This usually only happens however if you excessively abuse the VMs. You won't be banned for simply running malware or fork bombs or whatever once on the VMs.
While uncommon, constantly breaking the VM can also result in a ban, if a majority of members vote to have you banned from the VMs. This usually only happens however if you excessively abuse the VMs. You won't be banned for simply running malware or fork bombs or whatever once on the VMs, though others will find it very annoying.
 
== [[Fags]] ==
There are a lot of "forkie types", most of them ends with "fag".
 
=== Regfag ===
These forkies are probably the most common type. They open regedit and delete either HKLM\SYSTEM or HKLM\SOFTWARE, causing the vm to lock up and most system functions to stop working.
 
=== Guestfag ===
Guestfag is a generic name given to forkies with the name Guest. They can be any other type of forkie.
 
=== Rebootfag ===
These forkies constantly reboot the VM. When shutdown through normal means is disabled, they commonly restart through wmic.exe, or on Windows Server by the emergency restart function in the CTRL+ALT+DELETE menu.
 
=== BSODfag ===
These forkies constantly BSOD the VM. The most common ways are by killing CRSS.EXE or by running WININIT.EXE


== FTP Forkies ==
== FTP Forkies ==
Line 76: Line 58:


<gallery>
<gallery>
Primal Forkie.png|[[Forkies|Forkie]]
Primal Forkie.png | [[Forkies|Forkie]]
Jawful.png|[[Jawfuls|Jawful]]
ForkieIcon.png | Forkie icon (it's actually a restaurant logo)
Blue Forkie.png|[[Blue Forkies|Blue Forkie]]
Forkieinaction.png | [[CollabVM|VM]] destroyed by a forkie
ForkieIcon.png|Forkie icon (it's actually a restaurant logo)
Fork.jpg | A fork. That's all what it is
Forkieinaction.png|[[CollabVM|VM]] destroyed by a forkie
ForkLeft.jpg | Fork but flipped
Wtf.webp|Prototype Forkie
GoldFork.jpg | Gold fork
Fork.jpg|A fork. That's all what it is
Resturant_of_forkies_eating_right_now.jpg | Forkie Restaurant
ForkLeft.jpg|Fork but flipped
Forkies.jpg | Forkie Restaurant Logo
GoldFork.jpg|Gold fork
Abusefag.png|Blue version of the forkie icon (aka. Abusefag icon)
Resturant_of_forkies_eating_right_now.jpg|Forkie Restaurant
Forkies.jpg|Forkie Restaurant Logo
</gallery>
</gallery>


== See also ==
== See also ==
* [[Fags]]
* [[Fags]]
* [[Types of Forkies]]


[[Category:People]]
[[Category:People]]

Revision as of 09:17, 2 June 2022


Forkies
This article has contents related to Forkies.
➜ To report a rule violation, please join the CollabVM Discord and ask a moderator about it.
➜ Some articles about forkies may be slanderous. Help us by removing the slander!
An example of a CollabVM machine after being destroyed by a "Forkie".
Fact: Forkies used to look like this, before they became humans. (Shikashikashika~~!)

A "Forkie" is a nickname typically given to someone who maliciously causes destruction or otherwise renders the virtual machines unusable to annoy, intimidate and/or troll users of CollabVM.

Although their name derives from the term "fork bomb", they do not exclusively run fork bombs. A forkie may also run an executable which prevents anything from opening, deleting the registry, or other methods of blocking usability on the VM. Anti-forkies also have the same purpose, except the premise is to stop forkies from forking the VM, despite the fact that it, in and of itself, is a forkie.

Not too long ago, a vote to reset button was added to combat forkies along with a customized task manager (and later a customized command prompt), which is mostly actually successful at defeating nearly every forkie, although a forkie will eventually figure out how to bypass it and break the VM again immediately afterwards.

Forkies were not only present on CollabVM - they were also known to be present on the similar (but now defunct) website known as socket.computer, wecan.hasthe.technology, the Virus Farm and the like.

According to old documentation and (then) recent history, forkies have appeared to be successful business entreprenurs and have managed to assemble their very own restaurant! Dubbed Forkies Real Food Parlor and located in Lynnwood, Pretoria (?) South Africa, they have managed to score many customers and serve great Italian food! (Not rat poison surprisingly)

The restaurant has been since closed at one point in April(?) 2018.

Is being a "Forkie" a bannable offense?

Many users have questioned if being a Forkie is a bannable offense.

The short answer is: If the moderation team is online, sometimes but mostly no.

The long answer is that, if you have a very long streak of making the VM unusable, you might be banned. Or if you break a global site rule. For instance, creating an executable which DDoSed someone (assuming someone would have already knew about your intentions and reported it to the administration, or the administration is on the VM and has formally recognized it as a DDOSing attempt), you would likely be banned permanently.

Nowadays, there is now a rule in place on the site, dubbed Rule 9 of the CollabVM website, in which if you constantly make the VM unusable (t. textbook definition of Forkies), or run a certain banned script, or attempt to overwrite the VM's operating system with one another (t. Installfagging), it is constituted a rule violation.

While uncommon, constantly breaking the VM can also result in a ban, if a majority of members vote to have you banned from the VMs. This usually only happens however if you excessively abuse the VMs. You won't be banned for simply running malware or fork bombs or whatever once on the VMs, though others will find it very annoying.

FTP Forkies

FTP Forkies are forkies who destroy the (no longer existing) CollabVM FTP. Therefore this information is now irrelevant and is now only presented for historical purposes.

Indexfag

The Indexfag is a type of FTP forkie which adds an index.html into any folder of the FTP, which causes the page to be overwritten with the corresponding index page, forcing users to either have the file removed or use an external FTP client. As files cannot be deleted by regular users due to abuse, an admin must delete the file.

As of October 17th 2018, this forkie is fixed; users can still upload an index.html but users must click the file to load it.

Spacefiller

The Spacefiller is a type of FTP forkie which adds junk files to the FTP, causing disk space to be wasted or the FTP root to load indefinitely, causing a denial of service attack. These types of attacks are usually quickly cleaned and result in a ban.

It is pointless to fill the FTP as it takes forever and the FTP is large enough (4 terabytes, 2 terabytes for the 2 FTPs) and won't run out of disk space that easily.

Filebomber

The Filebomber is a type of FTP forkie which goes around looking for directories and then uploads file(s) intended to embarrass the corresponding folder's owner.

Such files (but not limited to) include: 'sethrogan.png' and '!!!!! !! ! !!!!!Anne Puts Her Foot Down!.mp4'.

Reversefag

The Reversefag is a type of FTP forkie which attempts to hack into the FTP server by uploading a PHP that loads in a reverse shell.

However, this fails miserably because the FTP server has PHP disabled for the FTP directory.

Gallery

See also