Forkies: Difference between revisions

From Computernewb Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
(One intermediate revision by one other user not shown)
Line 1: Line 1:
{{SeriousChangeNeeded}}
{{#seo:
{{#seo:
|description="Forkies" are (usually autistic) children who should not be using the internet, that destroys fake computers online in a futile effort to impress like-minded children and you.
|description="Forkies" are (usually autistic) children who should not be using the internet, that destroys fake computers online in a futile effort to impress like-minded children and you.
Line 11: Line 12:
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]]. They are often categorized by CollabVM users into [[Fags]].
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]]. They are often categorized by CollabVM users into [[Fags]].


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]]" (and was the original definition of Forkie), 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.


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.
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.
Line 17: Line 18:
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.
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.
-->


== Is being a "Forkie" a bannable offense? ==
== Is being a "Forkie" a bannable offense? ==
Line 26: Line 29:
The short answer is: '''If the moderation team is online, sometimes but mostly no'''.
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.
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 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, or run a banned script, or attempt to install another operating system over the VM's OS (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.
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.

Revision as of 15:17, 25 October 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. They are often categorized by CollabVM users into Fags.

Although their name derives from the term "fork bomb" (and was the original definition of Forkie), 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.

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.


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 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, or run a banned script, or attempt to install another operating system over the VM's OS (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.

Gallery

See also