Original sources of this guide (might be more up to date in case you're viewing a mirror of it):
https://old.reddit.com/youtubedl/comments/jktx5b/how_to_anonymously_host_the_continued_development/
https://raddle.me/f/AntiCopyright/121477/how-to-anonymously-host-the-continued-development-of-youtube
In this guide I will go through how to anonymously host the continued development of youtube-dl offshore using companies that have a track record of being very resilient to DMCA takedowns. As a general disclaimer, youtube-dl is not illegal, no matter how much the RIAA wants it to be. Hosting it is not illegal, but the RIAA doesn't care about what's legal, so we'll have to act accordingly and not rely on companies that will bend over backwards for them. This post is basically my way of flipping the bird to the RIAA.
DMCA ignored hosting providers
RIAA report including DMCA ignored hosting providers
MPAA report including DMCA ignored hosting providers
United States Trade Representative report including DMCA ignored hosting providers
ESA report including DMCA ignored hosting providers
Europol report including DMCA ignored hosting providers
La Liga report including DMCA ignored hosting providers
Former bulletproof hosting reseller reviews offshore hosting providers
Former bulletproof hosting reseller on what the most warez friendly hosting providers are
(Novogara aka Ecatel recently got busted for tax evasion and are shady as hell in general, allowing anything to be hosted on their servers, so it's best to stay away from them.)
Take into account what data center the hosting provider uses. If they don't run their their own data center the company running the data center can shut down the server if the data center isn't DMCA ignored. That isn't to say that resellers can't be resilient, but it depends on how resilient the data center they use is.
This goes without saying, but keeping the hosting provider secret makes it a lot harder to take down.
Some countries like Ukraine, Kazakhstan, and Korea force hosting providers to use government SSL certificates, meaning that they can MITM the connection.
CDNs and proxies to hide the real hosting provider
DDoS-Guard - Highly recommended. Based in Russia. Doesn't care about DMCA at all. DDoS-Guard is mentioned in the MPAA's Notorious Markets report and currently provides protection for Nyaa (the world's largest public torrent tracker for anime and manga) and Sci-Hub (the world's largest piracy website for academic papers which is under constant legal pressure from big US publishers). Has a free plan and accepts Bitcoin for paid plans. DDoS-Guard might be inaccessible outside of Europe for a few hours/month, meaning that sites using it would be unreachable outside of Europe during that time. This is probably peering related, but I'm not sure. Just tell site visitors to use ProtonVPN's free plan and connect to one of their VPN servers in the Netherlands if that happens.
While I recommend DDoS-Guard, I'll list some other alternatives in case something happens:
CloudFlare - Might be a honeypot, especially since I'm not sure how they'd be able to get away with this otherwise, but CloudFlare works for now. Just don't expect privacy from them. They're a US based company so they'll probably be reigned in eventually, but for now they're having their Wild West days. CloudFlare has a free plan. If CloudFlare is not configured properly when set up the real hosting provider will be leaked. More info about that here: 1, 2, 3, 4, 5, 6, 7

It's a myth that Cloudflare does not forward DMCA complaints, they forward everything. However, Cloudflare does not store any "sensitive data", which means forwarding "useless" information is similar like ignoring the DMCA request. A general advice is that whenever you use Cloudflare you should use a bulletproof backend server as well to avoid DMCA takedown request in the first place, so less or nothing gets forwarded (less "leakage risk").

Source: CHEF-KOCH / Warez / Bulletproof Hosting.md
OVPN's public IPv4 proxy (the Switzerland proxy) - Swedish company that provided a proxy for The Pirate Bay for a while, went to court because of it, and won. The two advantages with their Switzerland proxy in particular is that it's hosted by Interxion - the same Netherlands based company that is hosting Feral Hosting's DMCA ignored seedboxes - and that Switzerland is a pretty good jurisdiction. OVPN also scores well on That One Privacy Site. Accepts Bitcoin.
Before we go into registering a domain, I think it's worth considering if it's really worth keeping the name youtube-dl or if it could be spun off into a more accurate and less trademark infringing name like media-dl, for example. It downloads video and audio from a lot more sites than just YouTube, after all.
Resilient TLDs (there are more options than just these)
.is - As of a few years ago ISNIC had only ever suspended one domain and it was connected to ISIS.

When we asked whether ISNIC would follow Greenland’s lead and move for a proactive suspension, we got a clear answer.
“The short answer is no. Such an action would require a formal order from an Icelandic court. ISNIC is not responsible for a registrant’s usage of their domains,” ISNIC’s Marius Olafsson told TorrentFreak.
“This policy applies equally to any .is domain,” Olafsson says, adding that it’s the domain owner’s responsibility to abide by the law, not theirs.

Source: https://torrentfreak.com/pirate-bay-finds-safe-haven-in-iceland-switches-to-is-domain-130425/

“Domains can hardly be considered illegal any more than a street address. A street address is not illegal even if there is illegal activity in one apartment at the address,” ISNIC says.

Source: https://torrentfreak.com/torrent-domain-suspensions-damage-credibility-registrar-says-140617/
.ru / .su - Good for anything that doesn't affect Russia or go against Russian interests.
.to - Used by a lot of torrent and other filesharing websites. I have never seen one get suspended. .to is managed by a US company though, so it being "bulletproof" could change.
.cr is a resilient TLD according to the International Intellectual Property Alliance's (IIAP) report:

thepiratebay.cr domain is still online despite actions against it from the Internet Corporation for Assigned Names and Numbers (ICANN) and the U.S. Embassy in Costa Rica. Other notorious infringing sites are following the trend of using .cr domains as a safe haven (e.g., kickasstorrents.cr). Costa Rica’s failure to deal effectively with its obligations regarding online infringement, more than eight years after they came into force under DR-CAFTA, is a serious concern.

In case you want cheaper options that are available on Njalla, .ws and .ch are said to be pretty good.
.ec is also looking pretty solid as Library Genesis (the world's largest book piracy website, which is under constant legal pressure from big US publishers) have been using it for some time without getting suspended.
Vulnerable TLDs
.com, .net, .cc, .tv, and .name are operated by VeriSign, a Washington DC based company that is controlled by the US government.
.org, .info, .asia, .aero, .ag, .bz, .gi, .hgn, .in, .lc, .me, .mobi, .mn, .sc and .vc are operated by Afilias, a company that blocked one of WikiLeaks' domains.
.site, .website, .tech, .online, .uno, .fun, .space, .store, and .press are operated by Radix, a company that has an anti-piracy partnership with the MPAA.
All TLDs operated by Donuts, a company that has an anti-piracy partnership with the MPAA.
Resilient domain registrars/resellers
Recommended:
Njalla - As anonymous as you can get when buying a domain. Njalla is a Nevis registered company that buys the more common domains from Canada based Tucows, which is pretty abuse friendly and some TLDs like .is they buy from the registry directly. They then lease it to you while legally speaking they own the domain. This means that you don't have to give them any personal information to register it and they take Monero. Njalla is mentioned in the RIAA and MPAA's Norotious Markets reports. Njalla has a Tor Hidden Service, PGP key, and has support for registration via XMPP with OTR. Njalla is run by one of the Pirate Bay founders and they kept the Pirate Bay sense of humor alive when dealing with DMCA.
Other:
NiceVPS - As anonymous as you can get when buying a domain. NiceVPS is a domain reseller based in the Dominican Republic that buys the domain from easyDNS and then leases it to you, meaning that you don't have to provide any personal information since they own the domain on paper. Accepts Monero. Has a Tor Hidden Service, PGP key, and warrant canary. I've seen NiceVPS recommended on some websites, but I'm not sure how solid it is. Doesn't seem to offer all of the TLDs that Njalla, Openprovider, and easyDNS offer, including a lot of the more resilient ones.
Openprovider aka Hosting Concepts B.V. - Netherlands based registrar that is one of the most abused registrars by rogue pharma sites. Doesn't suspend domains without a WIPO decision or court order. Has a full section dedicated to it in the United States Trade Representative's 2019 report and a brief mention in the 2020 report.
easyDNS - Canada based registrar that has a big focus on due process. The current registrar of The Pirate Bay's .org domain, which it defended against the RIAA. Wouldn't suspend a domain for a video downloader like youtube-dl unless ordered by ICANN, CIRA, or a court according to their takedown policy. Accepts Bitcoin.
There are a few resellers of bulletproof Russian and Chinese registrars that accept cryptocurrency, but because those are pretty much only used by cyber criminals they would not be a good look for this project. And there's also the risk that they'll just be gone one day without a word and no way to transfer domain and not much recourse. Because of those reasons I'm omitting them from this list. I think the above mentioned registrars and resellers will be good enough, the project is legal after all.
Worth considering:
In order to anonymously directly register a domain at any of the other mentioned services than Njalla and NiceVPS you'd have to fake the WHOIS information, which violates ICANN's rules and registrars usually suspend domains because of that. I could especially imagine easyDNS doing this. Not sure how the other registrars would react to that, but ICANN does have the power to withdraw their accreditation - meaning that the registrars would lose the ability to issue domains - if they don't follow ICANN's rules. In the cases of Njalla and NiceVPS they aren't a registrar, they just fill in their own details and buy the domain for you from a registry/registrar when you register a domain using them.
If you use Njalla or NiceVPS you're handing over control of the domain to somebody else and have to take their word for it that you'll always have access to the domain. It's easier to trust Njalla than NiceVPS in this case since it's known who owns Njalla and they have more of a track record than NiceVPS, which is fairly unknown.
TLS/SSL
Let's Encrypt - Free, uses open source software, backed by EFF, Mozilla, and others. Easy to set up and easy to maintain with an auto-renewal script.
If you're using CloudFlare, you'll have to use their phony SSL certificate.
Keeping your server secure and other technical advice

Check your server, and how reliable it is in terms of security and privacy, online services like https://centminmod.com can test your server and it's configuration to ensure nothing is "leaking".
Check if someone can see your hidden backend server IP via https://dnsdumpster.com. In general you should block every IP connection to your backend server, only allow your own connection, VPN's or reverse proxies. You quickly can check if someone has an "open" backend IP service via services like https://censys.io.

Source: CHEF-KOCH / Warez / Bulletproof Hosting.md
If you use CloudFlare, also check that your backend isn't leaking using CrimeFlare.
If you have set up email with your domain, use SMPT and a custom mail server so it doesn't leak your origin server IP. Email is the easiest way to leak origin server IP addresses.
Use SSH instead of VNC. With VNC the login information is sent unencrypted via plaintext, meaning that a rogue exit node in the Tor network and any server the login information is sent over on the clearnet could record your login information if they wanted to.
Use a password generator for all accounts and have it set to the max number of characters. Don't put the login information into a proprietary password manager or an online password manager. Make sure to back up the login information to multiple hard drives/SSDs/USBs/etc.
Try and make the site portable so that all software and all configurations can be saved to an ISO that can be spun up at any hosting provider at a moment's notice in case the site has to move at some point.
If you get a VPS, make sure it's KVM. KVM is much more secure than OpenVZ since OpenVZ doesn't have much separation between different customers on the same server. OpenVZ is also easy to oversell. Xen is also secure, but has worse performance than KVM.
Use nginx, it has a lot better performance than Apache.
Use MariaDB. It's a more up to date fork of MySQL developed by MySQL's original developer after he sold MySQL to Oracle. Contains bug fixes that sometimes have not gotten into MySQL yet. It is of course fully compatible with MySQL databases.
Basic security hardening (I'd probably use OSSEC + Shorewall instead of fail2ban and ufw, but I'm not an expert at this ¯\_(ツ)_/¯ )
nginx configuration for improved security (and performance): GitHub Gist | blog post (8.8.8.8 and 8.8.4.4 are both Google Public DNS resolvers, so if you enable OCSP stapling, use a more privacy friendly DNS resolver, like Njalla's public DNS, one of the DNS resolvers mentioned on PrivacyTools, one of the DNS resolvers in DNS66's settings, or an OpenNIC server that doesn't keep logs. Digitalcourage e.V. and Chaos Computer Club are pretty trustworthy organizations, so their DNS servers from DNS66's settings along with Njalla's DNS resolver are probably solid, at least. Few OpenNIC servers seem to last very long, judging by that most of them were added in 2019 and 2020. If you use CloudFlare for the site, just use CloudFlare's 1.1.1.1 DNS, they'll get site traffic data regardless, so just use them for that DNS resolver as well instead of sending out data to another party.
nginx tuning for best performance
nginx SSL/TLS hardening including HTTP Strict Transport Security
Top 25 Nginx Web Server Best Security Practices
Let's Encrypt auto-renewal script
If you need FTP server software, Pure-FTPd is the most secure option. Use SFTP instead of FTPS for better security and less of a headache.
Disable password access for administration, require login using a SSH key, and limit the number of login attempts.
Change default ports, like SSH. If anyone tries to access the default SSH port, have the firewall block them for a few hours.
Disable root login.
More security tips for SSH are available here. Don't implement port knocking though.
Disable nginx logging once everything is set up to protect user privacy and improve performance.
Keep the software up to date to decrease the risk of your serveVPS being hacked.
Don't use analytics. If you have to, self-host Matomo (formerly known as Piwik). It's open source.
Keep up to date backups of the site on multiple hard drives/SSDs/etc.
Anonymous payments
Bitcoin is fully traceable nowadays and tumbling/mixing your Bitcoin won't make any difference.

Tumblers are useless
Against my better judgement, I’m going with this click bait heading, but the premise is correct. Due to the software running real time analysis on the ledger, simply avoiding taint and breaking up coins is now entirely ineffective, as it matches the full bitcoin amount to be received over a period of time, as the software is built around a neural net of sorts (talking out of school here, I’m not a programmer) it appears to self-correct in real time as a more "likely" or "accurate" owner conclusion is reached.

Source: Blockchain Analysis and Anti-Money Laundering (X-post from /DarknetmarketsOz)
Meanwhile Monero was the only cryptocurrency that that the US government couldn't track when they took down one of one of the biggest darknet drug markets and seized the site operator's cryptocurrencies. This is because Monero is the only major cryptocurrency properly designed to be private.
Update:
There has apparently been some recent developments when it comes to tracing Monero. You can read more about it in my comment on Reddit or Raddle. I wouldn't worry too much about it at this stage though.
Use I2P or Tor when transacting with cryptocurrency. I2P has some privacy benefits in its design over Tor:

Unidirectional tunnels instead of bidirectional circuits, doubling the number of nodes a peer has to compromise to get the same information. Protection against detecting client activity, even when an attacker is participating in the tunnel, as tunnels are used for more than simply passing end to end messages (e.g. netDb, tunnel management, tunnel testing) Tunnels in I2P are short lived, decreasing the number of samples that an attacker can use to mount an active attack with, unlike circuits in Tor, which are typically long lived. I2P APIs are designed specifically for anonymity and security, while SOCKS is designed for functionality.

However, I2P doesn't have as much funding and reseach or as big of a developer community behind it. I2P's userbase is also a lot smaller than Tor's. A full comparison about that can be found here. Monero chose I2P over Tor.
More information about Monero + I2P/Tor is available here.
Either get cryptocurrency donations or use a peer-to-peer exchange that doesn't enforce KYC (Know Your Customer) to buy Monero or Bitcoin. Unlike centralized exchanges, private sellers on decentralized exchanges won't automatically submit all their data to the government. Even if you get all of the cryptocurrency via donations and it therefore has no connection to your real identity at all you should still anonymize it via Monero so that it can't be traced from the donation wallet to the hosting provider which you want to keep hidden.
Some private sellers on peer-to-peer exchanges won't require IDs, while some might require it. If nothing is mentioned, it's worth asking the seller before you send them any money. A few even accept cash meetups and cash by mail (watch out for being scammed or mugged though). If you do go to a crypto for cash meetup, make sure it's in a public place with lots of people in case something goes wrong. LocalCoinSwap, LocalCryptos, and LocalMonero even has sellers that accept gift cards (which you could buy with cash in a physical store). However, most gift cards are only redeemable in the country they were bought in, making this an option that won't work outside of the countries the sellers are based in. The one exception to this that I know of are Steam Wallet gift cards, which work internationally.
If your method of paying for cryptocurrency involves going somewhere to buy it/a gift card/a prepaid card/a burner phone, consider leaving your phone at home since it's essentially a tracking beacon. If it's a cryptocurrency for cash meetup you might want to have it with you in case something goes wrong though.
From what I've read there are some centralized exchanges that don't require KYC, but at least some of them freeze funds if they think it seems suspicious (which I would imagine a Tor IP would fall under) and they refuse to release the funds until they have been provided with an ID.
If you decide to buy cryptocurrency using a normal payment method, a wire transfer would be the option that involves the least amount of companies getting the transaction info, though I don't think you'd have much recourse with getting your money back if you got scammed and paid via wire transfer.
Bitcoin ATMs may require ID and usually have surveillance cameras around them, but this may vary depending on where you live.
If you bought Bitcoin, use XMR.to to exchange it to Monero. If the service provider only accepts Bitcoin and not Monero, exchange the Monero back to Bitcoin so that the Bitcoin has been anonymized. Don't pay in Bitcoin without exchanging it to Monero and back first.
Prepaid cards usually require SMS verification and are sometimes limited to purchases within the country they were sold in, so be sure to read up on whatever card you're considering using. Vanilla Visa gift cards used to be the go to for VPN buyers back in the day since they only required putting a zip code into a website, but things change, so read up about activation requirements and international purchases for the card in your country before buying anything and if you get information from an unofficial source, try and make sure that it's at least somewhat recent. If SMS activation is required there are two options. One option is buying a push-button burner phone and a prepaid SIM card at a physical store using cash, activate it at a major public place and then once the prepaid card is activated shut off the phone and take out the SIM card and the battery. Another option is buying access to a dedicated number in the same country that you bought the card in at an online SMS inbox site using cryptocurrency (the free SMS inboxes that have shared phone number might be used up already). The catch 22 there is that you wouldn't have any cryptocurrency yet at this stage, so it's not really an option unless you figure something out that I wasn't able to think of. If the prepaid card can't do international purchases you could withdraw the money into an anonymously created PayPal account (requires SMS verification). Expect the prepaid card and PayPal account to almost certainly get frozen if you try to pay with it over Tor. The risk is lower when paying via a VPN IP, but it's still a notable risk, especially if it's a VPN server with lots of users and you can never verify that the VPN provider isn't logging you. An anonymously paid for self-hosted VPN on a dedicated IP address in the same country that you bought the prepaid card would be less likely to cause the card to get frozen. A residential proxy/proxy would be the least likely to get the card frozen. Just don't connect to that residential or self-hosted VPN/proxy directly using your real IP address since your ISP would see that and since you would be the only user of that self-hosted VPN it would be directly identifying. You could use the prepaid card on public WiFi, but that will give out your general location and will give the WiFi network your IP address. It will also give the WiFi network your MAC address, so be sure to set the MAC address to be random (just search something like "[operating system] random mac address on wifi" on DuckDuckGo). Then there's the issue that most browsers other than Tor Browser, SecBrowser, and Bromite are bad combating browser fingerprinting. Sure you could also customize Firefox with arkenfox user.js (formerly known as ghacks-user.js) and a bunch of add-ons to combat all the different kinds of tracking, but you'll just make your browser more unique the more you modify it.
Anonymous Internet browsing
Use Tor when doing anything in connection with the site, including when using PuTTY and FileZilla. Verify the integrity of the Tor Browser installer using PGP before running it so that you know that it hasn't been tampered with. Use a bridge if you don't want your ISP/government to see that you're using Tor. Running Tor over a VPN may seem like a good idea, but even if the VPN provider really doesn't keep logs (which is impossible to verify) using Tor over VPN can make you easier to track since that makes the VPN service a permanent entry node [1][2][3][4] and there's also VPN fingerprinting. If Deep Packet Inspection (DPI) is a concern you can use Pluggable Transports [1][2] to disguise the Tor traffic. Keep Tor Browser up to date. Never run Tor Browser in full screen. That makes you more easily trackable as websites can detect the real resolution of your screen. Don't install any add-ons or plugins, that makes you a lot easier to track. If you have logged in and then logged out of a site it can link you to other accounts you have on the same site using session cookies if you login to those accounts without hitting the "New Identity" button to relaunch Tor Browser with a clean slate. Block JavaScript when the website doesn't require it, that's the closest thing you'll come to an ad blocker. Use the Hidden Service version of sites when available, that way your Internet traffic never goes onto the clearnet and it also adds three more proxies between you and the site's server for a total of six proxies.
Since you shouldn't use an ad blocker with Tor Browser it's important that you keep your operating system up to date to minimize the risk of getting infected in case you come across some malicious JavaScript via for example malvertising when you have JavaScript activated.
If you use Windows and don't want to switch to Linux (even though you can set up dual boot or just boot it from a USB without even having to install it on your computer), use a non-admin user account and have an admin account that you only use to authorize trusted software to run, that will mitigate 94% of critical Windows vulnerabilities. You can use a tool like W10Privacy to decrease the amount of tracking in Windows 10, just be sure that the tool you use is updated to match the latest version of Windows 10 or you might brick your OS.
Email
Use an end-to-end encrypted no logs email provider located outside of Five Eyes, Germany, Enemies of the Internet, and countries under surveillance - preferably ProtonMail - when signing up for all of those services. Use a different email address for anything not related to the administration of the website. ProtonMail has a Tor Hidden Service, but signing up for ProtonMail is only possible on the clearnet address, so you'd have to go into Tor Browser's privacy settings and change "Prioritize .onion sites when known" from "Always" to "Ask every time" when you register the ProtonMail account. Change it back to "always" once the registration is complete. And yes, it is possible to sign up for ProtonMail via Tor. It's not easy finding an exit node that hasn't gotten blocked yet, and you will most likely need a secondary anonymous email account on another email provider to send a verification code to, but it is possible. Don't try using a disposable email service, ProtonMail blocks pretty much all of them so you'll just waste time and will probably get your account frozen. Once you have made an account, go into Settings > Security and then wipe and disable the authentication logs. Once that's done - before you sign up for anything - log out and wait a while then log back in, just to see if their anti-fraud system decides to freeze your account or not.
If you go for a email provider other than ProtonMail, keep in mind that it has to be there for the long haul in order to be usable. If it suddenly shuts down without notice, you're pretty much shit out of luck. So try and go for one that has been around for a while and seems like it will continue to stick around.
Comparison of alternatives:
https://privacytools.io/providers/email/
https://www.safetydetectives.com/blog/email-comparison/#3
https://www.prxbx.com/email/
Other
Use a new username that you haven't used before.
Use end-to-end encryption for all private communications. ProtonMail has built-in end-to-end encryption between ProtonMail accounts. If you want to encrypt email with PGP when communicating with non-ProtonMail users follow this guide. That will allow you to import it into ProtonMail. Just remember that the subject line will not be encrypted by PGP. PGP/MIME gives out less metadata than PGP inline and is just better in general, so use PGP/MIME. For file transfers you can also use OnionShare if the receipient also uses Tor Browser or put the file(s) into a password protected .7z file using 7-Zip with the "Encrypt file names" option enabled + a password generator set to the max number of characters that you then upload to Disroot Upload. Be aware that the lufi software that Disroot Upload runs on keeps the filename visible after the file has been deleted. If you need an end-to-end encrypted pastebin, self-host PrivateBin or use Disroot's PrivateBin. Disroot uses a privacy respecting hosting provider and claim that they don't keep logs for services that don't require an account, such as Disroot Upload and Disroot's PrivateBin.
Use DuckDuckGo instead of Google. At least when doing work related to the site. It has a Tor Hidden Service that you can easily find by searching "duckduckgo onion" or "duckduckgo hidden service" on DuckDuckGo.
Rely on open source software and privacy respecting services when it comes to processing and storing data related to the site. PrivacyTools.io, awesome-privacy, AlternativeTo, and GitHub makes it easy to find privacy respecting alternatives.
Keep software on your devices up to date to decrease the risk of it being compromised by an exploit.
And yeah, I probably went pretty deep on some of the less relevant sections, but I thought it was best to include everything.

If anyone hasn't seen Part 1 of this post, here it is.
Studies demonstrating roughly gender parity in sexual assault victimisation
Predictors of Sexual Coercion Against Women and Men: A Multilevel, Multinational Study of University Students
Here is a 2007 survey investigating sexual coercion in romantic relationships. It used a sample of 7,667 university students (2,084 men and 5,583 women) from 38 sites around the world. Participants reported their sexual victimisation experiences in the past year of their current or most recent romantic relationships. It found that 2.8% of men and 2.3% of women reported experiencing forced sex in their heterosexual relationships. (Table 1 and 2 on pages 408 and 410 respectively). A slightly higher proportion of the men reported experiencing forced sex and a slightly higher proportion of the women reported experiencing verbal coercion, with 22.0% of men and 24.5% of women reporting verbal coercion.
Prevalence and correlates of young people's sexual aggression perpetration and victimization in 10 European countries: a multi-level analysis
Here is a 2015 study about young people’s sexual victimisation and perpetration in 10 European countries. It found in a sample of 3,480 participants that the prevalence of sexual victimisation by force did not differ significantly between the sexes: 15.8% of men and 19.5% of women reported experiencing force (defined as the use or threat of physical force). Neither did the prevalence of sexual victimisation through exploiting the victim's inability to resist differ much by sex: 14.6% of men and 17.2% of women reported experiencing this form of sexual victimisation. Of the countries surveyed, Cyprus, Greece, Lithuania, Poland and Portugal had higher rates of male victimisation by force and exploitation of inability to resist as compared with female (though in Poland and Portugal, the difference was rather small).
Effect of gender and ethnicity on self reports of mild, moderate and severe sexual coercion
Here is a 2001 study by Fiebert and Osburn investigating sexual coercion among 452 Southern California students (259 females and 193 males).
At the beginning of a class period, students were asked to respond voluntarily, anonymously, and confidentially to a survey regarding sexual coercion. After completing the survey, students placed their completed surveys in an unmarked envelope.
Here are the survey questions.

1. I have gone out on a date with a man/woman because she made me feel I had to.
2. I have been forced by a man/woman to kiss him/her.
3. I have been forced by a man/woman to touch him/her sexually.
4. A man/woman has insisted, without using physical force, that I have sex with him/her even though I didn't want to.
5. A man/woman has made me have sex with him/her without a condom.
6. A man/woman has insisted, without using physical force, that I have oral or anal sex with him/her.
7. I have had sex with a man/woman because he/she threatened me in some way.
8. I had sex with a man/woman because he/she used some type of physical force such as holding down, hitting, hair pulling, biting.
9. A man/woman has threatened me in order to get me to have oral or anal sex with him/her.
10. After having sex with a man/woman, I have felt sexually taken advantage of.
11. I had oral or anal sex with a man/woman because he/she used some type of force such as holding down, hitting, hair pulling, biting.
12. A man/woman has sexually touched my body when I did not want him/her to.

They found that "A higher percentage of males than females reported having experienced sexual coercion on all items assessing mild, moderate and severe sexual coercion". The only item where a higher percentage of females than males responded affirmatively was on item 10.
Here is Table 1 in the paper displaying the percentage of positive responses to each item by gender.
Percentage of Positive Responses by Gender on Items 1-12

Item	1	2	3	4	5	6	7	8	9	10	11	12
M	29	35	23	27	24	18	10	6	7	14	5	42
F	13	19	14	23	12	15	4	5	3	27	2	38

The findings that are most useful to highlight from this paper are item 7 and 8 and the percentages. 10% of men compared with 4% of women reported having sex with a man/woman because they were threatened, and 6% of men compared with 5% of women reported having sex with a man/woman because their perpetrator used physical force.
High rates of female perpetration
Religiosity and Delinquency among LDS Adolescents
In this study, data was collected from Mormons between the ages of 14 and 19. In a sample of 636 males and 754 females, 5% of both genders reported that they "forced or pressured someone to engage in sexual activities." Though, it's important to keep in mind that "pressure" is a very loose term and "sexual activities" does not necessarily mean intercourse, so that 5% figure most probably includes many things outside of the scope of "forced sex" (rape).
Studies comparing the physical effects of sexual assault on male and female victims
Effects of Sexual Assaults on Men: Physical, Mental and Sexual Consequences
"Most research suggests that the sexual assault of men is more likely to be violent, and accompanied by more and greater corollary injuries, than sexual assaults of women (however, also see Kimerling, Rellini, Kelly, Judson, & Learman, 2002; and McLean et al., 2005). Here it is important to acknowledge that not all sexual assaults are violent, and often center on coercion of victims. However, “rapes” in the traditional sense of the word have been shown to be more violent when perpetrated against male victims. King (1995) reported that when men are raped in almost all instances some form of physical force is used against the victim, and weapons are commonly involved. Weapons are most likely to be involved when men are sexually assaulted by a stranger (Stermac et al., 2004). Kaufman et al. (1980), describing data drawn from male rape survivors seen in hospital emergency rooms, report men who are sexually assaulted are more likely than women to have nongenital injuries (see also Hillman, Tomlinson, McMillan, French, & Harris, 1990). However, they also conclude that men who are sexually assaulted are not likely to seek medical attention, unless they suffer significant physical injuries."
Studies comparing the emotional effects of sexual assault on male and female victims
Effects of Sexual Assaults on Men: Physical, Mental and Sexual Consequences (again)
"More specifically, drawing on a stratified random sample of the American population, Elliott et al. (2004) report higher scores on the Trauma Symptom Inventory for sexually assaulted men than women. On eight of the ten scales of the Inventory, sexually assaulted men report higher levels of distress than sexually assaulted women. Depression also frequently leads to attempts to self-medicate (Burnam et al., 1988; Choquet et al., 1997; Coxell et al., 1999; Iseley & Gehrenbeck-Shim, 1997; Plant, Miller, & Plant, 2004; Ratner et al., 2002; Walker et al., 2005) in efforts to block out memories or overcome feelings of low self-worth (Scarce, 1997). Self-medication includes use/abuse of alcohol, illicit drugs and licit (both prescription and over-thecounter) medications. Male sexual assault victims are more likely than female sexual assault victims to report subsequent alcohol abuse problems, although abuse of illicit drugs does not show a gender difference (Burnam et al., 1988). Additionally, researchers in both England (Plant, et al., 2004) and Australia (deVisser et al., 2003) report that sexually assaulted men are more likely than other men to smoke tobacco."
And:
"Men who are sexually assaulted commonly present a high degree of depression and hostility (Iseley & Gehrenbeck-Shim, 1997; Walker et al., 2005). Several community-based studies have shown that male sexual assault victims are, in the short run at least, more likely than female victims to present with greater degrees of depression and hostility (Carmen, Ricker, & Mills, 1984; Frazier, 1993; Goyer & Eddleman, 1984)."
Experiences of men forced-to-penetrate women in the UK
A report which explores the experiences of men who have self-identified as having been forced-to-penetrate (FTP) women. Semi-structured interviews were conducted with 30 men who self-identified as having been FTP a woman. Almost all of the participants indicated that their FTP experiences had negatively impacted their personal lives and relationships in some way. 14 men reported that they had experienced varying types of sexual dysfunction since their FTP experience(s). This included erectile dysfunction; "when I started trying to have another relationship, I found that I was having impotence problems" (Participant 7). A lack of libido or reduced sex drive, as well as a desire to avoid sex and sexual relationships was also discussed.
Linked to the above, 18 participants reported difficulties in forming new romantic relationships, often citing difficulty in trusting new partners. This is perhaps to be expected when it is remembered that FTP incidents most frequently involved partners and ex-partners.
"I find at the moment I haven’t got trust like I used to, I mean I find it a bit like er, I don’t trust like, women, in a way, like, the way I used to. I feel like as if it could happen again" Participant 3.
"It affects how I view relationships, I’m single at the moment by choice" Participant 13.
For some this inability to trust others and develop new relationships extended to include any and all relationships, not just intimate ones.
Nine participants reported that their careers were impacted, they were unable to work, or that they lost their jobs. This was typically as a result of the severe mental health impacts that they experienced.
"Now I just sort of lock myself away, I stay at home, I’m not working anymore" Participant 24.
"I’m nowhere near recovered really. I’m still under the mental health system, I’ve not worked full time since then" Participant 18.
Men are less likely to view to acknowledge their experiences of sexual assault and are less likely to report it, which likely affects data and statistics on the topic
Big Boys Don't Cry: A Critical Interpretive Synthesis of Male Sexual Victimization
This is a review of the literature surrounding male sexual victimisation. It notes that "Prevailing stereotypical gender roles and sexual scripts are in favor of women’s ability to acquire (ideal) victim status. However, quite the opposite is true for men who must reject their gender roles and sexual script in order to be considered an (ideal) victim."
"Existing expectations shape the way that people perceive sexual victimization and may therefore influence the victim’s own perception of their sexually unwanted experiences (see Figure 2). Davies (2002) suggests that men may never have considered that they could become sexual victims since prevailing gender stereotypes cause them to internalize the belief that male sexual victimization is beyond the realm of possibility. If such an event does occur, they may have trouble accepting not only that it happened to them but also that it happened at all. It is often presumed that men are able to defend themselves if they do not want sexual activity to occur and would find the experience pleasurable given their sexual opportunist nature. In addition, given the existing assumption that the presence of an erection is an indication of a pleasurable erotic experience, it is claimed that men are less traumatized in comparison to women (Bullock & Beckson, 2011). Since men often get an erection, ejaculate, or both during an assault (Bullock & Beckson, 2011), many male victims might feel as if they cannot label their experience as sexual victimization. Furthermore, the nature of male-to-male sexual victimization frequently leads to the conclusion that it is a homosexual act, suggesting that the victim must be gay (Davies et al., 2013). Additionally, men who acknowledge their sexually unwanted experience as rape feel as if they have failed to uphold the masculine ideal (Artime et al., 2014), resulting in a sense of “stolen or harmed masculinity.” Men may therefore remain silent, to avoid being viewed as unmasculine and gay."
"A stereotypical description of rape (i.e., rape scripts) may therefore lead victims to refrain from defining their experience as rape or sexual assault if the rape does not fit into this narrow definition (Peterson & Muehlenhard, 2004). Research has shown that many male victims do not seek help, or wait longer because of difficulties in self-identifying as victims (Machado et al., 2016). Machado, Hines, and Matos (2016) state that masculine gender socialization, social stigmatization, and strong endorsement of sociocultural values appear to be the main reasons why male victims do not seek help. This further increases their already high risk of developing PTSD (Larsen & Hilden, 2016), generating even more negative consequences when they do not get the help they need. Overall, these differences in the possibility of being considered a sexual victim will lead many male victims to refrain from reporting their experience or seeking help. Subsequently, this may be reflected in prevalence rates of sexual victimization being generally lower for males in comparison to females."
A systematic review of the prevalence rates of sexual violence is conducted in this report, and the authors note that all of the studies reporting high male victimisation rates use BSQs (behaviourally specific questions) as opposed to non-BSQs which use more generic terms (e.g., “rape,” “sexual abuse,” “sexual assault”) without further clarification. The authors assert that using BSQs is preferable partially because many male victims do not label their sexually unwanted experiences as rape. Not using BSQs may thus cause lower prevalence rates of sexual victimisation (especially among men), since reports of nonconsensual sex by victims who do not define their own experiences as sexual victimisation are not detected. They conclude "it is recommended that future research should consistently use BSQs".
Forced-to-penetrate cases: Lived experiences of men
This is a report investigating men who have been forced-to-penetrate women. It notes that "The majority of men did not report being compelled to penetrate a woman, either to the police or to friends and family. The reporting rate to the police of 1.7% is even lower than the reporting rate for women who have experienced serious sexual violence, which stands at around 15%. The extremely low reporting rate in compelled penetration cases suggests a clear lack of engagement by these men with the police and criminal justice process."
Thus, data based on police reports may understate male victimisation more than it does female victimisation.
Discrimination against male victims of sexual assault
Gender differences in medical students' attitudes towards male and female rape victims
A study examining attitudes towards female and male rape victims among 240 UK medical students (120 females and 120 males) using the Attitudes Towards Rape Victims Scale (ARVS). Half of the participants received the female rape questionnaire (where the statements referred to female rape victims) and half of the participants received the male rape questionnaire (the questions were the same as on the female rape questionnaire but the focal victim in the statements was male).
The researchers found that "Attitudes towards male rape victims ... were significantly more negative than attitudes towards female rape victims".
“Honey, We Don't Do Men”: Gender Stereotypes and the Provision of Services to Sexually Assaulted Males
This is an old study from 1996 (so the situation might have improved), but it is the only research study I am aware of which has sought to examine the provision of services to adult, noninstitutionalised male victims of sexual assault. This investigation found that many of the rape crisis providers and law enforcement agencies contacted held common stereotypes about male rape. The belief that men could not be raped or that they were raped only because they wanted to be was frequently endorsed.
One law enforcement representative bluntly stated "Honey, we don't do men". She laughingly asked, "What would you want to study something like that for? Men can't be raped." Another law enforcement representative said "Most males which are fondled or sodomized are males that want to be sodomized."
In addition, more than one third (37%) of the agencies initially contacted reported that they would not provide services to a male victim because their crisis services were geared specifically toward the needs of women.
Discrimination in favour of female sex offenders
Decisions and attitudes concerning child sexual abuse: does the gender of the perpetrator make a difference to child protection professionals?
Here is a 1994 research paper. An investigation was conducted into whether child protection investigators, specifically social workers and the police, are as likely to take seriously a case of child sexual abuse if it had been perpetrated by a female rather than a male. What they found was that "social services involvement and social services investigation were considered significantly more appropriate by male social workers if the perpetrator was male as opposed to female. Registration of incidents as cases of child sexual abuse was viewed as more appropriate by all participants as a group if abuse had been carried out by a man rather than a woman. Finally, imprisonment was viewed by all participants and, particularly, policemen as more appropriate for male perpetrators rather than female child sexual abusers." The only finding of theirs that runs counter to the pro-female/anti-male biases here was that female social workers viewed prosecution of the perpetrator as more appropriate if the perpetrator was female than male.
Sex-Based Sentencing: Sentencing Discrepancies Between Male and Female Sex Offenders
I find this one uproariously funny. This is an article published in the journal "Feminist Criminology" attempting to examine the utility of the evil woman hypothesis by examining sentencing discrepancies between male and female sex offenders. They used National Corrections Reporting Program data to identify sex offenders for the years 1994 to 2004 and the sentences they received for specific sex offences.
The hypothesis for their study predicted that women would receive longer sentences than men for sex offences. And they did indeed find a significant difference in sentence length between men and women, but not in the direction they expected. Men received longer sentences for sex offences than women.
At least these researchers were honest about what they found. Few feminist researchers are.
EDIT: If anyone wants to read the full text of these articles, just use sci-hub. Paste the link of the study here into this website and you can get the full text. It's how I'm accessing them.
https://sci-hub.se/

Previous Post | Prologue
Three months later, Martin Balducci held a release party for his latest feature film: The Western Gateway. It was a post-apocalyptic action piece, meant to channel the vibes of the Mad Max film franchise, but with a distinct North Texan flavor.
There was no red-carpet premiere or any sort of theatrical release, beyond a single showing for a test audience at UNT. In fact, there wasn’t much of a party, either; Balducci celebrated the film's release at his house in Arlington, and invited all cast and crew to honor the film’s uploading to Netflix’s servers.
When Dave arrived, over an hour after the party was scheduled to start, it was clear that there were several other no-shows for that evening. Dave checked his phone, to make sure the address was correct. It was, but the lack of noise and parked cars surrounding the joint didn’t help to convince him.
“Dave! What took you?” Alex said, passing a cup to Dave as he spoke. “You’d better have some of this stuff while it lasts, we’re nearly out!”
Wary of whatever the ‘stuff’ was, Dave sniffed the contents of the cup, before deciding against taking a drink.
“Sorry about that,” Dave replied, “I had trouble finding the place. What all have I missed? It doesn’t look like much.”
“Well, the film upload’s nearly finished,” Alex responded, “we’ve been watching that on and off all night, but everybody’s kinda been doing their own thing.”
Dave walked down the hallway, with Alex in tow, who continued to speak.
“Couple drinkers here, some small talkers over there, but nothing too exciting.”
“How about Sam?” Dave asked, “Did she show up?”
“She was here for a little bit,” Alex said, “she brought a bunch of pizzas into the kitchen, poured some vodka into the punch bowl, and left. Said she had to get back to work.”
“Work? Like, she was on the clock?”
“She probably wasn’t wearing a Mr. Jim’s uniform for style,” Alex snapped.
Dave did his best to not appear deflated. He followed Alex into the living room, where a computer was streaming to the television on the wall. Nothing fancy was on the screen, aside from an FTP client, that was working its magic. The text on the screen indicated, to practically nobody, that a 348-gigabyte video file was being beamed to a data center in San Francisco, and the estimated time to completion was less than an hour away.
“All that work, finally leading up to this,” Dave said, not quite to himself, “and nobody here seems to care.”
“Well,” Alex said, “for you, it may have been work, but to the rest of these guys, it's nothing. It’s more like living the dream.”
“Let me guess,” Taylor cut in, her speech slurred, “Your dream is to make movies, but you’re too comfortable, or too chickenshit to move out to New York or Los Angeles, or even Atlanta, to try to shack up with the actually somewhat successful productions that get made out there.”
“Who invited her?” Dave whispered, to Alex, who shared his dumbfounded expression. A handful of remaining party-goers picked that moment to shuffle out the door.
“Instead,” Taylor continued, her drink sloshing over the side of her cup as she swayed, “You find this cute little studio that’s right here in Grand Prairie, and it would gladly have you work there! It’s just… whenever you want to do anything other than accounting and secretary work--”
“Hey, Taylor, it’s alright,” Dave said, as he swapped cups with her, “I’m sure next time, there’ll be an acting role or a writing credit in there, somewhere,”
“That’s what he always says to me,” Taylor whimpered, as Dave and Alex helped her lay down on a sofa. Taylor fell asleep a moment later. Dave made sure her new cup made it onto the nearby coffee table, without spilling.
“You said Sam brought pizzas here?” Dave asked,
“Follow me,” Sam said, pointing toward the kitchen.
Balducci had been holed up in his office for most of the day, especially once it became clear that the turnout to this party wasn’t going to be noteworthy. He never liked hanging around at parties that one would consider lively, especially parties that he hosted. He liked boring, quiet parties even less.
Balducci thumbed through a stack of papers on his desk. They made up one of many lawsuits; this particular suit coming from a casting agent, who represented the stuntmen playing the gun-toting bandits in The Western Gateway. Words like ‘negligence,’ and ‘unsafe procedures,’ and ‘wrongful death’ popped up on every page, until Balducci got to the end, and tossed the papers into the trash can behind him. He wasn’t concerned at that moment; his lawyer only ever sent him copies.
Balducci glanced around his office, after ignoring a local oncologist’s letter, that was hiding underneath his legal documents. Posters from his past productions, as well as other projects he had a hand in, were mounted on the wall. He wondered where the next poster would go, assuming there would ever be another poster, until he noticed that the office’s walls were all completely covered. Before a greater meaning to this discovery could be realized, Balducci turned back to his desk, and gulped down the glass of brandy he had been nursing.
The laptop in his office, which was where the television feed was streaming from, indicated the data center in San Francisco had received 98% of the video file, and the estimated completion time was just ten more minutes away. Balducci poured himself another glass.
Dave ate the last slice of pizza, as Alex took frequent sips from his drink. They admired Balducci’s house, how it was rather small, but the space was well-utilized. There were few decorations; not cluttered, but not minimalist either. Or even modern; they noted how the appliances were high-end, but not new.
Dave was about to note the lack of family photos on the walls, when Alex piped up.
“Do you ever think about what’s going to happen to the company?” he asked.
“Honestly?” Dave responded, after a moment, “I do, on occasion. After this film was struck by the curse, it got me wondering, what’s next?”
“For the studio, or for you?” Alex said.
“Well, both,” Dave replied, after a moment, “I like what I’ve got going on here, but I’ve got a feeling that I could make it big going someplace else.”
“But you’re worried about losing what you’ve got, if you gamble for something bigger?” Alex asked.
“I think that’s what Taylor was going for,” Dave said, “but she was probably trying to get the company to live up to her own expectations.”
“Taylor was also shitfaced,” Alex interrupted.
“True. I think she had a point, though; from what I can tell, it seems like the company’s always right on the verge of going down the tubes. I don’t know how Balducci does it.”
“I don’t think even he knows.”
“Is that some kind of a joke?” Dave asked.
There was a pause. Near silence, aside from the front door closing behind another departing party guest. The last guest, judging by the general lack of noise.
“Not really,” Alex whispered, just in case, “This picture, the one we’re uploading tonight, it’s the sixteenth one Balducci’s directed at this studio. And I can only think of, like, three or four films that anyone would consider ‘good’. Certainly none of the films I’ve personally had a hand in.”
“Including Western Gateway?” Dave said back, slighted.
“Writing-wise, that one’s pretty good,” Alex reassured, “And the editing is solid, considering the circumstances.”
“Thanks,” Dave said.
“Anyway,” Alex continued, “out of all of these movies Balducci’s lead the charge on, hardly any of them appear to be well-made, cohesive packages. Just mindless action sequences, spliced between nonsensical dialogues, all under weak-at-best premises.”
“They’re all made that way, because I wanted to let aspiring filmmakers, like you two, to have a good head start in show business,” Balducci said, from the kitchen’s doorway.
Alex and Dave stared back, surprised and ashamed.
“Selling these films to Netflix, Youtube, and other streaming sites just let me share you guys’s work with the rest of the world,” Balducci said, unfazed, “the revenue they bring in just allows me to continue this practice more than once.”
There was another brief pause, as Alex and Dave turned their gazes toward the floor.
“Anyway,” Balducci said, “The film’s nearly uploaded. You boys wanna come to the living room to see?”
Alex and Dave agreed, and followed Balducci back into the living room.
Alex, Dave, and Balducci stood around the living room television, since Taylor was still passed out on the sofa. The FTP client’s estimated completion time bounced around between ten and twenty seconds left, until suddenly, the command line at the bottom of the screen read 100.0 percent.
Balducci picked up a wireless keyboard off a shelf mounted above the television. Using the keyboard, which was connected to the laptop in his office, Balducci closed the FTP client, and opened Netflix’s home page in a web browser.
“It’s only fitting that we actually show the movie at the release party,” Balducci said, to nobody in particular.
It took a rather considerable effort to find The Western Gateway in Netflix’s “new releases” listings; whether it was due to Netflix needing time to properly place the film in their library, or whether they simply didn’t care about promoting the film, was anyone’s guess.
While Balducci somewhat lazily scrolled and searched, Alex gave Dave a quick pat on the shoulder goodbye, and slipped out the front door. Balducci never even noticed.
Eventually, however, after refreshing the browser, a thumbnail for The Western Gateway blinked into existence toward the bottom of the web page. Balducci clicked the thumbnail, and the film began to play after another minute of loading.
The film’s opening credits began to play, over a montage of fake news broadcasts, and stock footage of riots and military action. As soon as the words “Directed by Martin Balducci” hovered into view, Balducci looked away from the screen, and glanced around the room. His eyes settled on Dave, who was the only other person in the room, and probably the house as a whole, who was still standing on his own two feet.
“Would you mind seeing me in my office for a minute?” Balducci asked.
“What, are we back in high school, or something?” Dave asked back.
“Nah, I’d just like for us to chat,” Balducci said. He took another glance at Taylor.
“I’d just like for us to sit down as we do it,” Balducci finished.
Dave agreed, and followed Balducci down the hall, back to his office.
The movie continued playing on Balducci’s laptop; Dave stared a little too longingly at the screen, where Sam was getting dressed as a part of a morning routine montage.
Balducci snapped the laptop closed without a second thought.
“So tell me, David,” Balducci said, as the two sat down in the office’s chairs, “What have you thought about your time here at Creek Crossing Films?”
“Well, it’s certainly been interesting,” Dave began.
“Interesting, how?” Balducci cut in.
“Something along the lines of, ‘oh god, oh god, we are all going to die,’ seems to fit nicely.”
Balducci stifled a laugh. Dave continued.
“Normally, when I tell my folks about something interesting in a script I’ve worked on, it has more to do with the situation I’ve put the characters in, writing-wise, and less about any production-related incidents.”
“Does ‘less’ mean ‘never’?” Balducci asked.
“Well, almost, but not quite,” Dave answered, “I wrote the winter musical for my senior year of high school, and on opening night, the lead actress nearly strangled her boyfriend with the wig he was wearing.”
“The boyfriend was… wearing the wig?” Balducci said, puzzled.
“Oh, no, her character’s boyfriend,” Dave clarified, “Said boyfriend was dressed in drag, and his wig was supposed to be ripped off as part of a big reveal, but the wig was all tangled up, it got wrapped around the guy’s neck… just, well, that was probably as bad as it ever got.”
“...that is, until you came to this studio,” Balducci said, “and on your first time working the second unit, there’s a massive explosion that kills a stunt man, and injures three more, and you’re worried it’s all your fault somehow.”
A pause.
“I don’t know if I’m taking it that far,” Dave said, “like, mentally, but that sums it up fairly well.”
“Well, according to my attorney at least, it was nobody’s fault,” Balducci said, glancing back at the lawsuit paperwork in his trash can, “At least, it's not specifically your fault. There were a bunch of unrelated factors leading up to all the damage that that explosion caused. The day laborers were hooking their wires up to that switchboard while it was powered on, the stunt men were doing their prep work while they were crowded around the car--,”
“Someone decided to soak the car in gasoline, just, on a whim,” Dave said,
“Actually, yes,” Balducci said, oblivious.
“Is that supposed to make me feel better?” Dave asked.
“It's not supposed to hurt,” Balducci responded.
There was another pause.
“Well, to answer your original question, I’d have to say my time here was… alright, at least until that explosion.”
“Would you be willing to come back for another production?”
“Honestly? I don’t think so.”
“What would it take for you to return? Or perhaps, stay here as a career?” Balducci said, grabbing a checkbook from a desk drawer.
“Well, for starters, no more explosions. But my answer is still no.”
“Are you a hundred percent sure?” Balducci asked.
“I gotta say, this isn’t exactly a great sales pitch you’re offering me here.”
“I haven’t even mentioned what I’m willing to pay you, to keep you around,” Balducci said.
Balducci ripped a check from his book, already filled out, and slid it across his desk, to Dave.
Dave glanced at the check, the writing on it nearly causing his eyes to pop out of his head.
“Three million, seven hundred fifty thousand dollars to Jim Adler and Associates?” Dave squawked.
Balducci took the check back.
“Oh, sorry,” Balducci said, apologetically, “That’s for those stuntmen. Well, some of it is, anyway.”
“You’ve already settled that suit?” Dave asked.
“By Monday morning, I will have,” Balducci said, “How did you find out about it? It hasn’t been on the news anyplace; the lawsuit I mean, not the explosion that caused it.”
“It was circling around the office for a while, rumors mostly,” Dave said, “That check you just handed me is the only hard proof anyone has actually had.”
“That makes sense,” Balducci said, “It also makes sense that you guys would speculate about that sort of thing. Nobody gets blown up, and is just, like, cool with that.”
Balducci snickered to himself, as he began writing a new check for Dave.
“Something more along the lines of this should make a bit more sense,” Balducci continued, as he slid the new check across the desk.
Dave read the amount on the check, which was still mind-boggling.
“How often would I be getting this? Every month?” Dave asked.
“Every week,” Balducci said.
“And you still said no?” Alex said, over cheeseburgers the next day.
“Not quite,” Dave said, after taking a sip from his drink, “I told him I needed to think about it some more.”
“What’s there to think about? Nearly five figures a week, just to write more movies?”
“Not just writing,” Dave pointed out, “Casting, editing, and a lot of the little non-funding-related producing things. ‘Maybe even costuming, if you are in to that sort of stuff’, according to his words.”
“Even then, still. How the hell does Balducci have all the funding stuff covered, anyway? I’m sure Taylor would be pissed if she found out how much money you would be making,” Alex said.
“According to Martin,” Dave responded, “Taylor isn’t going to know, because I’d essentially be paid under the table.”
“Okay then,”
“Also, he let slip that he’d won the lottery a couple decades ago. The man got over a quarter of a billion dollars, for writing his family’s shoe sizes on a piece of paper. He claimed the winnings anonymously, changed his name, and moved to Texas. He’s got his money spread out so many different ways, that he can afford to make any movie he wants, and settle any lawsuit he needs to, just off of the interest alone.”
“Holy shit,” Alex said, “And you still said no.”
“No, I said I would think about it,” Dave reminded, “because saying ‘yes’ to the money, means I’m running the risk of having my house burned down, or get Disney to sue my future grandchildren, or some other horrible thing I don’t want to think about anymore. Besides, I don’t have any idea where to go from here.”
“Would you do it if you had an idea?” Alex asked, “How about a script, is there a script you’ve always wanted to produce?”
“Maybe one or two…”
“So, you’d throw away the chance at making those scripts, and getting rich doing it, just because it’s a little bit risky?”
“One more time, I am not sure yet. It’s only been like, twelve hours since Martin asked me.”
“You’re on a first-name basis with the guy, it sounds to me like you’ve already made up your mind. I'm just saying.”
A pause. Dave and Alex finished their burgers.
“If I said yes, would you come back with me?” Dave asked.
“If the money is going to be as good as you say,” Alex said, “I'm coming back regardless.”
Dave gave Alex his best, and left the burger joint, tossing his trash in a can on his way out the door.
Later that night, Dave was holed up in his apartment’s bedroom, staring at a computer monitor. He expanded a single text file to fill the whole screen’s real estate, which only emphasized how little text had been written to the file.
The file was a short list of clever titles, each title followed by its respective logline – a sentence or two, explaining the film’s premise. Dave stared at every title, and pored over each related logline, fantasizing about what they could be turned into, at Balducci’s studio.
Dave knew it would be less dangerous physically, if he were to pack his things and move to Los Angeles, flesh out all of his script ideas, and shop them around to producers, in the hopes that someone eventually likes what he has written, and makes him an offer to buy the rights to the script. He also knew that moving out to Los Angeles was dangerous in every other way; the mental toll of moving fifteen hundred miles west, leaving behind everything and everyone he knew, without having a definite offer to have his script immediately produced, was daunting by itself.
Besides, some producer in California would just buy Dave’s script, and run off with it. Martin Balducci was offering to make the script, and let Dave continue to have creative control over it.
Dave picked up his phone, and dialed Balducci’s number. Dave knew what he wanted to say, but Balducci never picked up the phone. So, Dave settled for Balducci’s voicemail.
“Hey, Marty, it’s David Bartlett here. Just letting you know I wanted to accept your offer, just call me back when you get a chance. Thank you.”

I saw in another thread people asking about the rules.
I found this post on revolt(dot)Group back in March 2017, Luckily I had shared this on another site. very educational.

Some of this info may be outdated, but this will give you an idea of the politics of it all. yes, even piracy has politics.

The Warez Scene
Press Ctrl+F on your keyboard to quickly find a paragraph you need.

1. Intro
   
2. The Scene
   

2.1. The Warez Scene Hierarchy
2.1.1. Peer-To-Peer
2.1.2. Newsgroups
2.1.3. IRC Trading
2.1.4. FXP Boards
2.1.4.1. The Scanner
2.1.4.2. The Hacker
2.1.4.3. The Filler
2.1.4.4. Pub/Pubbing
2.1.5. Top sites
2.1.5.1. The Sites
2.1.5.2. The People
2.2. The Scene System
2.2.1. IRC
2.2.2. Credit System
2.2.3. Affiliates
2.2.4. Release Database
2.2.5. Nukes
2.3. The Scene Rules
2.4. What is a Release?
2.4.1. Release Types
2.4.2. How does an original release look like?
2.5. About Release Groups in General
2.5.1. The Structure of a Release Group
2.6. Scene Art
2.6.1. ASCII art
2.6.2. ANSI art
1. Intro
Ever wonder what made release groups like SKIDROW and RELOADED so popular? It's because they are Scene groups. Scene groups exists for a long time and has a rich history. These type of groups are famous for their high quality and fast releases. However, the warez scene quite often seems to fail to achieve these expectations the last couple of years. The reason for this is the next generation games and group members, who don't always follow the strict scene rules. For more info (source: http://scenegrouplist.com/), read the next interesting paragraphs. Enjoy.
• • • • •
2. The Scene
The scene or the warez scene is the pretty unknown worldwide network where people trade pirated goods, like DVD's, movies, games, applications etc. Warez refers primarily to copyrighted material traded in violation of its copyright license. It does not refer to commercial for-profit software counterfeiting. First warez is released by release groups that are specialized in publishing warez. They copy a DVD or break the security of a game, and will make it available for other people, as a so-called release. When these release groups finish a release it will be uploaded to sites. These sites are very fast private FTP-servers, and the first stadium in the distribution of a release. Eventually, at the end of the distribution, the releases are available for everyone on P2P (torrent).
The speed of this worldwide network is enormous. Within minutes a release can be copied to hundreds of other sites. Within an hour, it's available on thousands of sites and FXP boards. Within a day or two it's available on newsgroups, IRC and in the end, on P2P. It's not all one big happy family. The warez scene consists of certain groups/layers. At the top we have the release groups and the topsites. These groups are the scene core. The other groups officially are not a part of the scene. Though, most people consider them as a part of the scene. Read more about the scene hierarchyin paragraph 2.1.
The Scene isn't just a distribution network, it's far more than that. There are the scene rules which are there to guarantee good quality releases. If not, a release will be nuked. This means it will be marked as bad. Nuked releases are not spread well and the release group will get a bad status. Read paragraph 2.2 to learn more about the how the scene works.
Security is an important issue in the scene. Since their activities are illegal the sceners have to secure themselves, to be safe from the anti-piracy organisations and avoid being caught in a takedown.
2.1. The Warez Scene Hierarchy
The scene is build up in a certain hierarchy. To explain the structure of this, here is a global overview of the piracy food chain. Not all these “layers” are considered as a part of the scene by everyone. The anti piracy organizations and most of the other parties which are not in the scene them self, do consider all these groups to the scene. In fact, the release groups and the people on the top sites hate these other groups. The reason for this is that FXP boards, IRC traders, and mostly peer to peer users bring the scene in danger. The sceners (people from the scene) want to keep the releases for a limited amount of people. Since everyone who knows how to use a computer most likely knows how to use P2P software, everyone is able to download releases. This causes big losses for record labels, movie producers etc, what leads to attention of anti-piracy organizations. On their turn, this brings the sceners in danger, so that's why they disapprove these groups. FXP boards consider themselves in the scene. IRC traders and newsgroups might now even know about the scene, and P2P-users definitely don't know about the scene.
Here is the hierarchy:
o Release groups - Groups of people who release the warez into the scene. Often linked with Site Traders.
o Top sites - Very fast FTP servers with people who trade the releases from the above groups to other (top)sites.
o FXP Boards - People who scan/hack/fill vulnerable computers with warez.
o IRC Trading - Users of IRC who download from "XDCC Bots" or "Fserves".
o Newsgroups - People who download from alt.binaries newsgroups.
o Peer-To-Peer - Users of P2P (peer-to-peer) programs like KaZaA, BitTorrent, uTorrent (etc) who share with each other.
2.1.1. Peer-To-Peer
At the bottom of the piracy food chain we have the peer-to-peer users. There seem to be two groups of peer-to-peer users. The first group are kids downloading some music now and then because they can't afford CD's. Second are the older P2P users who use P2P also for downloading games, programs, movies, etc. In the media, peer-to-peer are being labeled as dangerous pirates. They are a lot easier to bust and there are quite some of them who are being sued by the RIAA for thousands of dollars. The level of security is very low, and it's easy to get access to all warez. This is why they endanger the sceners. Most P2P users don't have a clue about what a long way a release has made untill it's available for download. It has been released, spread from topsites to FXP boards, then to IRC/newsgroups and in the end it's available for the mass via peer-to-peer.
A special kind of P2P system is BitTorrent. It uses a central location which coordinates the downloads but it doesn't host any downloads. The download itself consists of several pieces offered by various users. Such a coordinated group is called a torrent. BitTorrent is widely used, although it's rather insecure. The central distribution point is called the tracker. The tracker knows which users already have the file, and which users want to download it. The users who already have the download are called seeders, and the users who are downloading are called leechers. Every user who downloads a certain file, downloads a different part of the file. When the seeder goes offline, they can still download from each other and all complete the file.
2.1.2. Newsgroups
Once upon a time when the internet was still young there were special interest groups that shared information and kept in touch by using a bulletin board type system. This system was designed to take advantage of the internet in a way an old bulletin boards couldn't; each location had a machine (news server) that would store all the messages of the newsgroups that were desired by it's users. A short time passed and the users of certain newsgroups thought that this system would be ideal to share files with each other. It's easy to access newsgroups but unless you are familiar with them, navigating and downloading files from the newsgroups takes more effort than P2P. You can download from newsgroups using a newsreader, for example: NewsLeecher and Xnews. There are also pay news servers, these are faster and can hold up the files longer than free news servers. Free news servers can be quite fast, and pay news servers are even faster.
2.1.3. IRC Trading
Not far up from peer-to-peer users we have the people who go to IRC for their warez. In general, these people intend to have a better knowledge about computers and the internet. Warez channels are often run by people who have access to a fair amount of pirated material.
There are generally two types of these channels. These can often feed by people from FXP boards or bad sites. First there are Fserve (user-to-user) channels. They mainly use the mIRC client's File Server function and some scripts to share their warez directly from their hard drives. Second there are XDCC (server-to-user) channels. These are usually run by people who are into FXP boards or in the scene. They have access to new warez. They employ people to hack into computers with fast internet connections and install XDCC servers (usually iroffer) which are used to share out pirated goods. There is a limited amount of people allowed to download a release at once, so when a release is popular you are placed into a waiting line. That way good download speeds will be guaranteed.
2.1.4. FXP Boards
FXP stands for File eXchange Protocol. It isn't an actual protocol, just a method of transfer making use of a vulnerability in FTP. It allows the transfer of files between two FTP servers. Rather than client-to-server, the tranfer becomes server to server. The PXP'er just gives a command to one server to send files to the other server. FXP usually allows very fast transfer speeds although it totally depends on the connection of the servers. Still it's usually faster since the hackers are able to hack very fast servers. The FXP boards layer in the piracy food chain is quite unknown and therefore rather safe. Though the hacker's activities are very illegal, and therefore dangerous. Security is important. The members are usually a lot smarter than IRC-traders/P2P-users and have a greater knowledge about computers and internet.
The boards usually run a vBulletin forum with custom hacks. The boards usually don't work with a credit system. Though the admins do a user cleanup once in a while. The board's members consist of scanners, hackers, and fillers. They each have their own tasks:
2.1.4.1. The Scanner
The Scanner's job is to scan IP ranges where fast internet connection are known to lie (usually universities, company's, etc.) for vulnerable computers. We're talking about brute forcing passwords from programs, or scanning on ports for certain programs which contain a bug. The scanner will often use slow previously hacked computers for his scanning (known as scanstro's), using remote scan programs. Once the scanner has gotten his results, he'll post this at the board. This is where the Hacker comes into play.
2.1.4.2. The Hacker
Hackers are the people who break into computers. There are many easy-to-exploit vulnerabilities. Hackers get in to a computer using an exploit to get in via a program's bug. An exploit is a script which uses the bug to get in the PC. The program/exploit he uses (of course) depends upon the vulnerability the scanner has scanned for. When in, the hacker runs his rootkit (a modified version of Serv-U usually). This rootkit is the server where other people can download from. Most likely he will also install remote administrator software (ussually Radmin), so he can get in to the computer easily. Once the server is installed and working he'll post the admin login data to the FTP server on his FXP board. Depending on the speed of the compromised computer's (in other words a pubstro or stro) internet connection and the hard drive space, it will be used either by a filler or a scanner.
2.1.4.3. The Filler
Now if the pubstro is fast enough and has enough hard drive space, it's the filler's job to get to work filling it with the latest warez. The filler gets his warez from other FTP servers hacked/filled by other people. Fillers sometimes have site access, and FXP releases from there to their pubstro. These people who are in sites and in FXP boards are considered corrupt, and if other sceners find out, they will be scenebanned (banned from all his sites). It is said that it happens quite often. Once he's done FXP'ing his warez, the filler goes back to the board and posts leech logins for one and all to use. Fillers (with site access) all try to post a release the first. It's kinda like a race, who ever wins it get the most credits. The speed of these pubstro's depend on how fast the hacked PC is. Hackers from these FXP boards are rather good, and are able to hack 100 mbit/s.
2.1.4.4. Pub/Pubbing
Pubbing is not so important anymore nowadays. These are the scan/hack/fill methods from the old days when many university and business FTP servers had write access enabled on anonymous FTP-servers. So instead of breaking into a computer, they would just upload their warez and give the IP address to their friends. This was very popular but died out for obvious reasons. It works like this; there is someone who scans for FTP servers with anonymous logins with write-access. Once found a pub would be tagged (a folder with the name "tagged.by." is created). The idea was that if a pub was already "tagged" other pubbers would leave it alone. This apparently worked for a while, with people respecting other people's tags and leaving the pubs alone. But it certainly stopped working in the long run.
A method against retagging is dir locking. This is used in pubbing to stop people which are not allowed to get into the directory of the tagger. There are a couple or dir locking tricks. The first and easiest is to make a maze. When you make a maze you just make a lot directories and other people would never know in what map your stuff is since you would have to try them all out. Second is UNIX tagging. That's about a the magical character, the ÿ (alt+0255) which is an escape character on UNIX machines. When give a directory a name containing that character, the name will be displayed different then when you typed it. The creator can get in by typing in the original name. Last is dir locking on NT systems. More about this and other dir locking here.
2.1.5. Top sites
Next on the list and pretty much at the top or near the top are the site traders. Site trading is basically sending releases from one site to another. Release groups publish their releases on these sites, so they are the first stadium in the distribution of warez. From there on a release will be spread all over the world.
2.1.5.1. The Sites
These sites have very fast internet connections. 10 mbit/s is considered the minimum, 100 mbit/s good, and anything higher pretty damn good. The sites have huge hard disk drives. 200 Gb would probably be the minimum, and they can get up to 5 terabytes. These sites are often hosted at schools, universities, people's work. These sites are referred to as being legit. This means that the owner of the computer knows that they are there and being run, which is the opposite of pubstro's. Fast connections mean a lot to some people. If you have access to a 100 mbit/s line (and are willing to run a warez server there), there are people who would quite happily pay for and have a computer shipped to you just for hosting a site that they will make absolutely no profit from. Commercial use of site access is not something common, most people do it just for fun, not to make money. Standard site software are GlFTPd and DrFTPd. As well as running FTPD, the sites run an eggdrop bot with various scripts installed. The bot will make an announcement on an IRC channel when a directory is made or upload completed. It will also give race information, since just like on FXP boards, the site traders try to send a release as quick as possible to another site. That way he will earn credits. The more credits, the more he can download. The speed between topsites can reach about 15 mbit/s.
2.1.5.2. The People
There are basically three ranks in site trading: siteops, affiliates and racers. Siteops (Site-Operators) are the administrators. There are usually between two and five siteops per site. One is often the supplier of the site, another the person who found the supplier and guided them through the installation of the FTPD. The other will be friends and people involved in the scene. One or more of the siteops will be the nuker. It is his job to nuke any releases that are old or fake. Affiliates are the release groups who post their releases there right after they are finished. Racers are the people who will race releases between sites. Usually they will have access to a number of sites and will FXP a release as soon as they're released. FXP'ing a release will gain credits. The ratio is usually 1:3, so FXP'ing 3 Gb will get them 9 GB credits on the site. The race is to upload the most parts of the release at the fastest speed.
2.2. The Scene System
In the scene hierarchy section (paragraph 2.1) we already explained what a topsite is. Here we'll provide some more detailed information about topsites and their system, and the scene system. Security of course is a very important issue. Topsites are very private. A typical topsite configuration will only allow users to login from a certain host (or IP range), with SSL encryption on all FTP sessions. FTP bouncers are commonly used to hide the topsite's real IP address, and to share network load. Most users will connect through proxy's. That way the sites won't see their real IP-addresses.
2.2.1. IRC
All site members are present in the site's IRC channel. These channels are mostly located on private or very secure IRC servers, and you'll need to connect via SSL. Apart from SSL there are more security measures. You cannot just join the channel, you have to invite yourself, by using a command line when you are connected to the site. That way people who are not a member of the site, will not be able to join since it's secured with invite-only or with a channel key (password). The channels are often protected with FiSH. FiSH is a IRC addon which encrypts the messages in a channel. That way people who don't have the proper fish key, won't be able to read the messages. In that IRC channel, the members and site ops can talk to each other. Also there is a site eggdrop bot present, which will make an announcements when a releasegroup publishes a new release on the site, or announces when a members starts to upload a release. Also most sites will have an announce channel. This channel automatically displays the latest releases just after they're prepared. More about that below.
2.2.2. Credit System
The site works with a credit system. Site-ops and commonly affiliated are exempt from this system, they have a free leech account. This credit system works according to a ratio. Most common is 1:3, this means when you upload 3 Gb, you can download (or FXP) 9 Gb. When a member doesn't pass the minimum monthly required amount of upload, he'll automatically be deleted. Credits can be lost by uploading a bad release which gets nuked. Nuke multiplier affects the amount of lost credits.
2.2.3. Affiliates
There are basically three ranks in site trading: siteops, affiliates and racers. Siteops (Site-Operators) are the administrators. There are usually between two and five siteops per site. One is often the supplier of the site, another the person who found the supplier and guided them through the installation of the FTPD. The other will be friends and people involved in the scene. One or more of the siteops will be the nuker. It is his job to nuke any releases that are old or fake. Affiliates are the release groups who post their releases there right after they are finished. Each affiliate has access to a private, hidden directory on the topsite. This directory is used for uploading new releases before they are made available to other users .When a new release has finished uploading on each of the group's sites, a command is executed to simultaneously copy it into a directory accessible by other users, and trigger an announcement in the top site IRC channel. This command is called the PRE-command. "To pre" refers to executing this command. Pre-releases may be also relayed to external pre-announce channels to inform other couriers/site members/users from FXP-boards that a new release is available for racing. The warez scene relies on strict release standards, or rules, which are written and signed by various warez groups. Racers are the people who will race releases between sites. Usually they will have access to a number of sites and will FXP a release as soon as they're released. FXP'ing a release will gain credits. The ratio is usually 1:3, so FXP'ing 3 Gb will get them 9 GB credits on the site. The race is to upload the most parts of the release at the fastest speed.
2.2.4. Release Database
When a group pre's a release, the release will automatically be registered in the pre-database. This is huge database which contains all the releases ever release into the scene. This release databases records release names and their release date & time, although fields vary from database to database. Examples of other common fields include genres, sections, and nuke details. Release databases are maintained to provide release groups with a service for checking existing release titles, to avoid a dupe (duplicate). Also users are able to check whether or not, for example, a game was already released, the release date, the status (nuked or not) and more. Release databases are updated by automatic processes that either recurse selected topsites searching for new releases (spidering), or catch pre-release announcements from site channels.
2.2.5. Nukes
If a group publishes a release which already has been released by another release group, it's a dupe (duplicate). Then the release will be nuked. This means that it's marked as a bad release. Release groups try to avoid nukes, since this will give them a bad reputation. Except for dupe, releases can be nuked for other reasons too. There are 2 types of nuke:
o Global Nuke:
o Nuked because of the release itself. It is nuked because something is wrong with the release, for example: sound errors, dupe, freezing video, bad rip, etc. If a group will find out there is something wrong, they can request a global nuke.
o Local Nuke:
o Nuked because of the environment. Individual sites will nuke for breaking their rules, for example: no repacks allowed, no games with languages other than English and Dutch, etc. So there is nothing wrong with the release. Because of these releases are nuked locally, they can still be traded on other sites.
2.3. The Scene Rules
The scene rules are the standards in the warez scene for releasing warez. These standards are the minimum requirements for a release. The scene rules are defined by groups of people who have been involved in its activities for several years and have established connections to large groups. These people form a committee, which creates drafts for approval of the large groups. In organized warez distribution, all releases must follow these predefined standards to become accepted material. The standards committee usually cycles several drafts and finally decides which is best suited for the purpose, and then releases the draft for approval. Once the draft has been signed by several bigger groups, it becomes ratified and accepted as the current standard. There are separate standards for each category of releases. The scene rules can be updated anytime, though it is most likely that the rules won't change more than 1 or 2 times a year.
Why these rules? The scene rules may seem a little strict, but they certainly are not there to bother rippers. There are several reasons why these rules exist:
The rules enforce high quality releases only, so no worries about corrupted files, an error or other bad stuff. Because the releases are divided into small parts you don't have to worry about re-downloading the whole release if something goes wrong. You can control that everything has been downloaded correctly by checking against the SFV-file. Hence you will always know whether you've gotten a complete uncorrupt release of what you were downloading. The rules lead to a standardized way of sharing, which the people who download obviously benefit greatly from. You will learn to recognize a good release and be spared the inconvenient trouble/surprise of poorly ripped movies by amateurs. Scene releases always contain all the information about how it's ripped, what the quality is etc. This way you always know what you're downloading. You can find rule sets here.
2.4. What is a Release?
Original releases are rips of movies, programs, games and music, all released by groups specialized in creating these kinds of releases, so called release groups. A release is the full package of a ripped game, movie etc. These releases are all created in a standard way, according to the scene rules. That way the tag (directory name) and the included info file directly give you a lot of information about the release type, the source and so on.
First there is the actual content. Most big releases with the size of a CD or DVD are released as an image, mostly in .ISO or .IMG format. Basically an image is a complete backup of a CD/DVD. They can be burned (Nero, Alcohol 120%) or mounted (Alcohol 120%, Daemon Tools). The content it's often packed into compressed files for easy spreading. Also it contains an info file which will tell the downloader all about what's in the release, how it's created and what the quality is. More about how a release looks like here.
To ensure the quality of a release, there are the scene rules which are set up by the release groups. These scene rules exactly tell how a release should be prepared for the scene. This is the big advantage of scene releases, you'll always get high quality.
2.4.1. Release Types
All those scene releases have to be ordered in a clear system, so it's easy to look something up. Therefore the releases are categorized in the categories below.
The most important categories are:
o TVRip: A rip from a television show
o Movie: Movie in video format
o Apps: Applications
o Games: PC games
o Console Games: Games for consoles
o DVDr: DVDs
o MP3: Music albums/singles/vinyls/livesets/etc
o 0day: 0day refers to software, videos, music, or information released or obtained on the day of public release.
There are even more categories but they are less important. Such as: VHS (A VHS-videotape rip), PSP-movies, XVCD and previous generation console games like PSX (PlayStation 1), DC (Dreamcast games). MDVDr, XXX and Anime sometimes are also defined as a category. In fact it's a movie/DVDr, but since they are a little different from regular movies they are sometimes considered as unique categories. The same goes for MDVDr (Music DVDr) which is different from regular movies but it's still DVDr, and the same story for MViD (Music Video) but then video.
2.4.2. How does an original release look like?
The way a release is build up is in some ways dependent on what section it belongs to. Common, for all releases except music, is that the release (i.e. the game, program, movie etc.) is always archived in a number of RAR-archives. This has been done to facilitate the actual download of the release, and in some cases is also due to tradition.
A release always contains:
o A main directory:
o All the files from a release are placed into 1 directory. The name of this directory is equal to the release name. There are certain rules concerning the release names. This is done so that all necessary information will be included in all releases. Uniformity creates a clear distinction – imagine if all groups would have their own ways of naming releases. This is also done to ensure the release on different kinds of platforms. Some of these can't cope with special letters, as å, ä, ö or blank spaces. To prevent the risk of getting an error only a certain set of symbols are allowed. These are:
o ABCDEFGHIJKLMNOPQRSTUVWXYZ
o abcdefghijklmnopqrstuvwxyz
o 123456789-_.
o SFV-file (.sfv):
o SFV stands for Simple File Validator and is used to check files if they became corrupt after transfer. It does this by doing a CRC (cyclic redundancy check). After the check it displays which files contain CRC-errors and therefore are corrupt. It's also used on FTP servers/sites to check the progress of downloads or uploads.
o NFO Info-file (.nfo):
o An NFO file is a text file with information about the release. The files are designed by ASCII artists and can be read with Damn NFO Viewer or simply with notepad.
o WinRAR-file (.rar):
o A RAR file is a data compression archive format. The actual content is packed into a RAR-archive. Usually they are split to multiple RAR volumes with a certain size (15 or 50 mb is standard). Scene releases are packed into RAR files, but they are not compressed.
Not all types of releases are created in the same way. There are a lot of resemblances between them, but there are also some differences. Some are essential for that type or release, other things are the way they are because of tradition. Let's have a look at the individual release types:
o MP3:
o The MP3 releases are the only ones which aren't tagged into RAR files. MP3 releases are tagged with _ to replace the spaces, instead of . with most types of releases. Most MP3 releases contain .JPG scans of the front/back/inside covers of the CD. MP3 releases contain MP3 files, and also M3U files. M3U playlist file (.m3u):
o An .m3u file basically is just a text file that lists all MP3 files. If the .m3u file is loaded to a media player, the player plays the list of media files in the order they are listed in the playlist.
o Movies – DVDr – TVRip:
o These releases are all in RAR archives. Most common, they are split into 15 mb RAR files. For DVD5 50 mb is standard, and for DVD9 100mb. These releases (can) contain:
o Sample in a subfolder "Sample":
o This folder contains a sample of the movie. This way it's easy to check the quality of a release. The size of the sample is most of the time the same as the size per RAR, so 50mb if it’s a DVD5.
o JPG Cover in a subfolder "Cover":
o This folder contains the scan(s) of the cover of the source, most common in .JPG format.
o Subtitles in a subfolder "Subs":
o This folder contains the sub(s) of a movie. This is only for DiVX, XviD etc and not for DVD. The subtitle files are text files which can be loaded onto the movie, using programs like BS Player. When a DVD is more than 1 disc, there are sub folders in the main folder: DISC1, DISC2 etc. Same goes for CD: CD1, CD2 etc.
o PC Games – Console Games – Apps:
o Nothing new about this, they contain the .SFV file, .NFO file and are in rar files. Most games and applications are tagged with . and most console games are tagged with a _, but 0day apps are a little different though. Most of them don't contain a .SFV file, but a .DIZ file instead. Also apps and games can contain subfolders like CD1/CD2.
.DIZ file file_id (.diz): o File_id.diz is a plain text file containing a brief content description of the archive in which it is included.
2.5. About Release Groups in General
A releasegroup simply is a group of people which releases warez such as movies, games applications, or music on the internet. IRC is the group's medium to stay in contact with each other. The size of a group varies, some groups have just 5 people, others maybe 20. Mostly the members of the group don't know each other in real life. Trust is a highly important issue. Since the group's activities aren't legal, the team members have to be able to rely on each other. If one member gets caught, the other ones are in big trouble too, so security has high priority. This means that for example they talk on private IRC servers or through a bouncer, and they connect to their sites through proxy's. In the group, every team member has his own task.
2.5.1. The Structure of a Release Group
o Leader: The leader decides the main directions for the group. The leader is not a dictator, he won't decide everything by himself. He also has to keep the group together, and keep the individual members satisfied.
o Supplier: The supplier is the group's source. He often has pre access to the game/movie/etc, but this is not necessary. It's also possible that this is someone who sneaks into the cinema and films the movie. The top groups have pre access. Their supplier might work at a DVD plant, a DVD review magazine, or a DVD rental store. The supplier gives the game/movie/etc to the other team members.
o Cracker: The cracker breaks the security. Not all groups have a cracker. Crackers are required to release games, applications and alike.
o Encoder: The encoder rips and converts the movie so it's suitable for the web. Encoders are just in movies/DVDr groups.
o Packager: The packager packs the release and adds the essential files and information.
o Courier: The courier pre's and spreads the release all over the world via FTP.
This is just a global overview, it's not the same for every group. Music releases for example are often quite simple to create and multiple tasks can be done by 1 person.
2.6. Scene Art
Scene art are digitally produced images. Of course they are not just created by release groups. As a result of the artscene's early affiliations with hacker and software piracy organizations, the digital art is quite attached to the scene. There are two types of art types used for the scene. First here is ASCII art and second there is ANSI art.
2.6.1. ASCII art
ASCII art is an artistic medium that are graphics pieced together from the 95 printable characters defined by ASCII. ASCII art is used in the release group's NFO file. The standard viewer for NFO files is Damn NFO Viewer, but you can also view them with Notepad.
NFO files were first introduced by the release group THG (The Humble Guys) with their release of the PC game Bubble Bobble. This NFO file was a replacement of the more common readme.txt files. Nowadays the NFO file is like a signature of the group, so it's important to have a cool and good-looking nfo. A typical modern day NFO file is elaborate and highly decorated, with usually a large logo at the top with all the release-related information below.
2.6.2. ANSI art
As computer technology developed, monitors were available that could display color. Eventually, text artists began incorporating this new level of flexibility to the existing medium of ASCII art by adding color to their text-based art, or animating their art by manipulating the cursor control codes. Quite simply, this is what is commonly referred to today as ANSI art.
The majority of the early created ANSI art were distributed as coded executables called loaders or intros/cracktro's. A crack intro, also known as a cracktro, loader, or just intro, is a small introduction sequence added to cracked software, designed to inform the user which release group or individual cracker was responsible for removing the software's copy prevention and distributing the crack. Cracking groups would use the intros not just to gain credit for cracking, but to advertise their bulletin boards, greet friends, and to give themselves recognition.
Credits - Original post: https://revolt.group/index.php?/topic/67-the-warez-scene/
In the event that this wasn't enough reading for you, or for more up to date information on the warez scene, you can go here.(Thanks to @cuddle-buddy for the link)

PROOF: http://imgur.com/r39SSf7
Compare to photos of me at the last page of: http://electionprotectionaction.org/uploads/MOVE%20Act%20nov%205th%20article.pdf plus at http://electionnightmares.com/archives/438 or this example: https://www.laprogressive.com/its-the-ballot-count-stupid-florida-deja-vu-in-tucson/ among many others...
This is long, yes, but with supporting documents...proof will be noted some of the links.
There’s a small group of activists and computer geeks who have been following election problems since 2003. I’m one of them. We’ve had our successes but honestly, things are getting worse. The latest trend scares me: people in “closed primary” states (where you have to be a Dem to vote in the Dem primary for example) are finding themselves switched from Dem to something else without their permission and often with very crude at best signature forgeries on the false voter registration documents. This is new – it tells us that election manipulation has been going on too long, not enough people care and now we’re seeing “in your face” examples. I’m going to go into the history of the issue and what we need to do to change things.
If it takes me a week or a month or whatever I’m going to answer every question in this thread!
Urgent: one of the people I’ve worked with over the years is John Brakey based in Tucson AZ. The AUDIT-AZ election oversight group he founded is now in the thick of it as Arizona now has two election challenge lawsuits going, one filed by John and one by the DNC (Democratic National Committee). John’s suit seeks to overturn the Arizona election and have a do-over while the DNC wants the court, as a cheaper remedy, to throw out all the Arizona delegates to the convention. John and AUDIT-AZ need funding immediately – more about their lawsuit and donation info (via PayPal) is at: http://electionnightmares.com/ - I'm pictured in there, look for the big guy with the fanny pack with the peace sign on it.
Now let me fill you in on some history of this problem...some of it stuff I was directly connected to.
I’ve been involved since mid-2003. I was brought into this movement as a former IT guy (already turned activist by then) by the work of Bev Harris and I still sometimes refer to myself as one of her earliest lieutenants. Bev was the first one to turn up serious proof of misconduct in vote counting software and systems when in January of 2013 she found an open-access FTP site (online repository of stuff) maintained by Diebold Election Systems and copied all 40,000-ish files off it over three days. This, in my opinion, really jumpstarted the debate over bad voting systems. By 2005 I spent a year in the Seattle WA area working with Bev on election investigations and reporting. Bev and I still talk and collaborate frequently.
Important: the single biggest fallout from Bev’s first reporting, still very relevant today, is that at each county running Diebold voting gear there’s ONE computer where all the precinct and mail-in votes are added up – the “central tabulator”. Bev showed (with basically stolen copies of the Diebold “GEMS” central tabulator software that as long as you deal with the election database with “GEMS” everything appears secure, but once you open the data in an off-the-shelf copy of Microsoft “Access” (a crappy database app included with MS-Office) all the security basically vanishes: you can edit every aspect of the election with no password required, no audit trail entry left and you can even edit the audit trail. When I’ve been involved in forensic exams of voting systems after an election I very, very often find evidence that MS-Access is loaded on there. In a few cases we’ve found proof it was used. Voting system software has to be approved and “certified” ahead of time and MS-Access has never been approved, at all, by any state or at the federal level. When you see that bad boy on allegedly certified voting systems it’s basically a burglary tool for elections.
At one point Diebold denied this, saying that “no human being” can alter the data in this manner...so Bev knew somebody with an honest-to-God chimpanzee and we taught HIM to do it: https://www.youtube.com/watch?v=N4-wQhtRiP8 – behind the scenes note, this was possible because the dang thing was addicted to Menthos[tm].
My reddit username originally matched my real name: James “Jim” March. In 2013 I married another political activist hellraiser, Jill Simpson and took her last name. Jill is somewhat well known as the formerly Republican whistleblower who put a hurt on Karl Rove: http://www.donsiegelman.net/Pages/topics/Players/Heros/heros_simpson.html
Jill and I met doing election monitoring in 2012 for the Obama campaign. This report on the risks of manipulation of overseas and military voter’s intent got a fair bit of coverage and remains of concern, although we don’t think it’s a top avenue of election management misconduct this year: http://electionprotectionaction.org/uploads/MOVE%20Act%20nov%205th%20article.pdf – note that pics of myself and Jill are in there, part of my proof...
In the summer of 2005 I was arrested in San Diego California for trying to observe the counting of the vote as per California law: http://www.lookingglassnews.org/viewstory.php?storyid=1685
I was released a week later with felony election tampering charges dropped: http://www.democraticunderground.com/discuss/duboard.php?az=view_all&address=104x4266418 – if you scroll through the comments you’ll see that I was controversial among some Dems as I was previously best known as a gun rights activist and lobbyist...in 2002 I was thrown out of the California NRA because I was exposing how sheriffs were selling gun carry permits for campaign contributions and the NRA told me to stop complaining about Republican sheriffs doing that. I refused. Yes, I’m still a “gun nut” of sorts. As you can see, some of the folks on Democratic Underground had...issues with all that :). They had issues with Bev Harris for another reason I’ll get to in a sec.
Back to election stuff :).
In 2006 I moved to Tucson AZ and immediately started working with John Brakey who had been tracking election problems since 2002 when he was threatened with assault by pollworkers in Pima County when he realized they were shaving votes. John and I did a LOT of work exposing Pima County’s election problems (2nd biggest county in AZ, where Tucson is) and in Maricopa County (the biggest by far, centered on Phoenix). To give one good example of how shady Pima’s election process is, check out this videotaped deposition of the head election tech for Pima County during most of the last decade and decide for yourself if he’s hiding anything: https://www.youtube.com/watch?v=yfPGU4LjN94 and https://www.youtube.com/watch?v=QzyxQszono0 – trust me, he doesn’t usually twitch like that :).
In 2010 John and I did some digging into election misconduct in Maricopa County: https://drive.google.com/file/d/0B2TKmkSNAkCfOTMzN2YzZTgtNzIyYi00MTcyLTg4YWQtMzY1NzhkMGFjZTQ1/view?ddrp=1&hl=en&pli=1 which became the basis for a lawsuit trying to reform at least some parts of the process. This report in turn was mentioned in an appellate court decision awarding fees to, among others, John and I by name: http://caselaw.findlaw.com/az-court-of-appeals/1596645.html
This was one of the few times this insanity paid anything - $8k each if I recall right? (I’ll have John chime in on this thread if possible...he’s usually not a redditor.)
The main reason I’m posting is that while I’m no longer in Arizona (I moved to Jill’s place in Alabama in early 2013), John is still fighting and in the recent Arizona primary election a whole lot went wrong that John is now suing over. One of Arizona’s problems was a pattern also seen in other closed-primary states where people’s voter registration database entries were altered to deny them the right to vote in the Democratic Party primary. You can see examples from other states here: http://heavy.com/news/2016/04/election-fraud-voter-registration-changed-suppression-party-affiliation-sanders-clinton-ca-ny-az-md-pa-what-to-do/
Specifically in Arizona, Anonymous is claiming the statewide voter registration database is hackable - vulnerable to SQL Injection along these lines: https://xkcd.com/327/ - and that Anon was able to actually test-hack the data: https://anonymousinvestigationsblog.wordpress.com/2016/03/26/anonymous-report-was-arizonas-voter-registration-database-hacked/
We also know that the number of sites where a voter could in fact vote were radically reduced from previous elections in Maricopa County, from almost 400 four years ago to about 60 now. John has evidence of misconduct at some of those voting locations (for technical reasons, not really “precincts”). We also find it very suspicious that on election day Bernie won the polling place vote by 60% to 40% Hillary but in the mail-in voting the pattern was exactly opposite – 40% Bernie, 60% Hillary. We know there’s enough security holes for Maricopa County election staff to have manipulated it and they have a long infamous history of deliberately subverting security enough to pull it off.
The Democratic National Committee has announced that they too are filing suit in Arizona. They’ll be in federal court. John’s lawsuit is in state court and because he’s challenging the actual outcome of the election (requesting the whole thing be done over!) he is “fast tracked” with his first hearing on the 19th of this month(!). He needs financial support immediately for that case.
John’s lawsuit has a lot more details at: http://electionnightmares.com/ - he is for real and I’d like you to consider hitting the “Donate Now” button. He has a real attorney who we’ve worked with before in Maricopa County. Any help appreciated and win or lose, any and all information he gathers in his suit will be shared ASAP with the public and with the lawyers for the DNC as they follow behind in federal court on a slower timescale (because they’re challenging future procedures, not necessarily the actual outcome. John’s affidavit gives a decent starting point as to his case: https://drive.google.com/file/d/0B6Fh3F6hufhDN296Vm1PNE1UY3M/view?usp=sharing
One other thing...I mentioned controversies regarding Bev. This relates to a problem I’ve seen ever since the debate over voting machines and processes started. In 2004 (a presidential election year) Bev got flooded with donations from people on the left who hoped she’d be able to “save the election”. Yeah...didn’t work exactly although blaming Bev was dumb. Reason being, if you want to save, well, let’s say the 2020 election from fraud, you need to start NO LATER THAN early 2017. It takes time to figure out where the weaknesses are, predict how the next round of hacks will go down and sue over them. Those of us in the election integrity community never EVER get funding in advance. John’s lawsuit in Arizona is very important but what’s really needed is strategic investigation and litigation intended to go to the US Supreme Court. I can tell you for a fact that when the US gun rights lobby went to the Supreme Court twice in 2008 and 2010, the planning for those cases began in 2000 with funding and resources from major organizations and budgets starting at half a mil. The US election integrity movement has never, ever been as well funded and the money that does come in happens in “pulses” every four years.
You can’t protect an entire national election in 2016 when you start in 2016. Ain’t gonna happen.
We need to switch to crowdfunded support and we need to get this idea of well-planned long-term action established. That said, among the “quick and necessary” suits this year that DO have results that can be built on, John Brakey’s case via the group AUDIT-AZ has the best chance of quick action that will in turn support suits across the rest of the election cycle. If you can support his work please consider it
Thanks and AMA!
(I’ll be answering in two-hour-at-a-time blocks at least twice a day – my finances forced me to become a long-haul trucker of all things...)
EDIT: I'll be up again at 9am EASTERN tomorrow (Sunday) for at least a couple of hours...then more across the day.

List is moving to Google Docs: See here to read and submit

The list below is now defunct

FIRST BEGAN: 8/10/2016
LAST UPDATE: 8/12/2016
CURRENT TOTAL: 586

BattlEye Bans:

• A_Potato.
  
• A_Ten
  
• AaO-HeadHunter
  
• AC.Hwanbe
  
• Accursed_
  
• AEN6077
  
• AFF-GWIN
  
• Agent_Infinite
  
• Ahmad_x_iRaQe
  
• AleAle_Malaya
  
• AlYAYAYA.
  
• AMMMMMMMMMMMMM
  
• Amotrez
  
• Andy_Kim
  
• ANgrY9mAN
  
• AOD_Darth_Vapor
  
• Arch-Priest
  
• ArcLight.Rome
  
• Ares_Alex
  
• ARG.NachooO
  
• ArneTee
  
• ArtQfWar
  
• AshiBoy.
  
• Asin.Tux
  
• Assassin_GY
  
• AssassinNick.GS
  
• Astro_Lube
  
• Astro_moy
  
• Ataraxy.GenesiS
  
• Avelion.Crew
  
• AyaseEil
  
• B.O.W_Amash
  
• B8edM8
  
• BadAss0815
  
• Bagom
  
• Bahlkong
  
• BangBangHideYo
  
• baransezer1905
  
• Bashwarp
  
• BastianIsNoob
  
• Battleyebaninc
  
• BBK-Jessekiarie
  
• Befummler
  
• BeSl_Kaku_3.0
  
• Big Dick McGee
  
• BIG.J.M.E
  
• BIG_CrimeBerry
  
• BigPePeLover
  
• BIK-WOLVES-
  
• BlackReaper45
  
• BLT-Silencer
  
• BlueMango0009
  
• Blutbad77
  
• BMG_eQuinox.
  
• Bornitto
  
• BossKampos
  
• BOT-OneOrk
  
• brigidas
  
• BrononBrobarion
  
• brotein_shake
  
• Brotien_shake
  
• Bstor
  
• Buzzx
  
• ByCy_SlaughteR.
  
• CachorroBelga.
  
• cafezinh0
  
• Calibur_
  
• capmilton
  
• CaptainPinou
  
• Carlos20milla
  
• Carne.Assada
  
• Carphorus
  
• CarTeam_BALU
  
• Caviar.Ra
  
• CC-Malankov
  
• Cedde01
  
• CF.Szawel
  
• cf_Claude
  
• CGT-s00nicKPRO
  
• chameleonfive
  
• CHELENIX__ON
  
• Chiki_Briki69
  
• Chimbopper
  
• Churrimongi
  
• Cl4wn.exe
  
• ClassicTrash
  
• CloudTheCancer
  
• CN_SAONIAN
  
• Co2._.
  
• COE_Delta9Thc
  
• ColonelEpicness
  
• ConYay95
  
• Cornichon_vert
  
• Cream.Cheeese
  
• Creative60433
  
• CS.Raiden121
  
• D.Notorious
  
• D2H13
  
• D786945unit
  
• DabOnDeezNutz
  
• Daddy-.
  
• dagitici
  
• danielrodrigu3s
  
• Dariobeatz
  
• Dark.Mind.Here
  
• Darkwing..Duck
  
• DarthSmoking
  
• Davace
  
• Davarius
  
• DayghostX
  
• Dayne--
  
• DazzaFromKazza
  
• deadkein1
  
• DeAdMaNPrOxY
  
• deanoLad
  
• DeqzRampage
  
• Dexy..
  
• DGSoloGMR
  
• Dhulai_Man.
  
• diggerthenoob
  
• Dilligasx
  
• Disturbed_9586
  
• DitschTv
  
• dkanrj23
  
• DLC.OneShOT
  
• DM.Pabloi320
  
• dobongdon0I7I0F
  
• Dogs_Army_CZ
  
• Dogs_Shooty-SK
  
• dominic.c
  
• dOsk.wD
  
• DRE_Bloodwyn
  
• DRY_Michi
  
• DRY_Yandere
  
• DryGag4Lyfe
  
• Dubbi94
  
• Duckalott
  
• Dudum_chit
  
• DunMaDi
  
• Easy-Game666
  
• Eax_Ishad
  
• EddieSickHD_
  
• EFG-BIT_CHL
  
• EFG-Schmiddi
  
• enjoi480
  
• Epsilon-Twikii
  
• Erg.IRON
  
• ES_Tr0leX
  
• ESC-BiuBiuBiu
  
• EuroVAG
  
• ExtazyDude
  
• FAKKOT_Kraken
  
• faminTTx
  
• FAO_anto756
  
• FBI-Ninja
  
• Fettsau_Doener
  
• FFI-Think
  
• FilhoDOCrazy
  
• FilthyFranksNut
  
• Fisher-Swift
  
• Fizu_Ziika
  
• flautzer
  
• Flayless
  
• flexflexenTM
  
• Fn.LacheroN
  
• FOR_PanetonE
  
• Forest-06
  
• FoxMCBotinha
  
• FR.Peytonkill
  
• FranksBJBarn
  
• FreakPat
  
• freimari
  
• FrenzyQT
  
• Frog-Six
  
• Fruit-Lemon
  
• FTP_RipperKhaOs
  
• FTW-Pirralhoth
  
• FTW_MedTek
  
• Fu..Her_Gently
  
• fudgehog97
  
• FURY.judahh
  
• Fuuk_Mi
  
• G.Calvenir
  
• g2ky_Clout
  
• G4meStephan
  
• GabeNewellHL3
  
• Gandalf_Hood
  
• Garados121
  
• GARM.DerMajor
  
• GCMC_CEDo
  
• Germany-DaVids
  
• GK_mosurfz
  
• GO.SmoKill
  
• GoldenKappa
  
• Gomegatr0n
  
• GONZA-TZZ
  
• GOR707RUS
  
• GorditoMasBonis
  
• GPV.GOonWar
  
• Granpa.ccT
  
• Grigoram
  
• GripsGaming
  
• GrobeNotGrob
  
• GSG9.Panda
  
• GSG9_Broker
  
• GSL-Pr00z1um
  
• GTC_Fettpresse
  
• GTW_Vario
  
• GUN_TheCrueL
  
• H-7.Revotheos
  
• H.L.-rush3R0
  
• Hack-e-peter
  
• Hack-Norris
  
• HairyClown
  
• HAYYY5
  
• HD-summer
  
• HD.Bear
  
• heloitsmiii
  
• Herr.Goebbels
  
• Hi11ary4Prison
  
• HighKoala
  
• Hledjolf
  
• Hlruk0
  
• HMD-JerryL4Real
  
• HMD-pang
  
• Holl0wPoint
  
• HOW-Atombre4ker
  
• HRF_NeoTendar
  
• HRF_Royaldorn
  
• Hum-Yan
  
• humboldt.grower
  
• HUNTER_GER_521
  
• I6.Hidra
  
• I9.BlaCk
  
• i_Q6ri
  
• IbiusSlithirus
  
• IbRaH1m0v1C
  
• IcWolvesVorTex
  
• ieuan557
  
• IMT.Scorpion
  
• independent_mac
  
• Inframe_Subtil
  
• Inframe_Toxic
  
• inversely
  
• Invicta.
  
• IR.gang.Saman
  
• ISG.Zangado
  
• isibert95
  
• ItzAstra
  
• iTzZikao
  
• Ivo_Holanda
  
• J3W-Midget
  
• Jack.Estrada74
  
• JakobeKell
  
• JamesRoot-4
  
• Jannik_GTX1080
  
• JAPPER.Thaksin
  
• Jason_Bournee
  
• JasonGSW
  
• Javad00009
  
• Jayahwastaken
  
• jc_Jean
  
• JeSuis-Felipe
  
• john_Raga
  
• joker1234556
  
• jonmaljon
  
• jono8120
  
• joshuaknic
  
• Juli-
  
• jumaa2016
  
• JUNEPark
  
• JvM-
  
• jynj00245169
  
• k1_CritcalGamer
  
• Katlin-
  
• KeoXys
  
• Kerttu.
  
• Kevin.LTK
  
• KiLL.0N
  
• KNUX_HEGHOG
  
• Kosaka-Honoka
  
• KotoriMyWife
  
• kotzstrahl
  
• KSK_Desty
  
• Kubera-
  
• Kuraud0-san
  
• l-Netlic-l
  
• l-see-you-guys
  
• l0vEtAn
  
• LaBoostedAnimal
  
• Lanfeust_detroy
  
• LarVa-
  
• LeAni.NTG
  
• LeNoXxQc
  
• Letagod.
  
• Lindroos.
  
• lllPacolll
  
• LM_Prede.
  
• lN1GHT_batata69
  
• LOBOSOLITARIO
  
• London_Fox
  
• LSD_PulgOsO
  
• Lucifer-Samael
  
• Lukario73
  
• LukeCageSR
  
• lukin
  
• LumberTugboat
  
• lVerttiixl
  
• M.L.G.
  
• M.R.K_J3erkay
  
• M0nk3y_D_Luffy
  
• Malkiot
  
• Marijonight
  
• mariows2
  
• MasterMind--
  
• MavericSam
  
• MCSkylineEU..YT
  
• MeeNiGunZ
  
• MegaHurtz
  
• megapizori
  
• meiya-gl
  
• MetalJackT_
  
• Methamphetamlne
  
• Metromanzao
  
• meybah
  
• MGs_PH4NTOM
  
• mircolm
  
• Mizeneu
  
• MKAYRAKLIK
  
• Mkhooor_
  
• MkW-Fede
  
• mmza
  
• modef.
  
• moohdqtr
  
• Moomoo_Lunaria
  
• Mord_horst
  
• Mori.Summer
  
• MorteBranca-
  
• Mouche_peteuse
  
• Mr.BShock
  
• mr3ofive
  
• Mr_Bruh
  
• MST.Renegade
  
• multi_x6
  
• Mungojerrie_Lee
  
• N4m3lezZ_GER
  
• NaturalSRB
  
• nerbs.WG
  
• NExUs_Maitreya
  
• NitroViper
  
• Niv----
  
• NOCS-Cirolino
  
• nOOG-
  
• Nrom.Sherly
  
• nuD-WOLVES
  
• Nx-.
  
• nx.BALOU
  
• NZ_John.Cena
  
• o.harambe_rus
  
• O.Poil2zgeg
  
• OAO_RandomShot
  
• OfficialGoat
  
• OG_blyatman
  
• OhYeonSeo
  
• OJOODHSL
  
• Olympus
  
• Omen-Cornus
  
• ONN_Apollon
  
• oooompaloooompa
  
• OP_Pummeluff
  
• Opera_Browser
  
• oShadowG
  
• oShadowGaming12
  
• other_boi
  
• P4ros
  
• Padawan-Wayne1
  
• palasco432
  
• Pamahx
  
• pasayguy
  
• peter2931
  
• PFG.SaladDays
  
• Phantomxxxx
  
• piemo12
  
• pixelhead_
  
• PIZZA_GameOver
  
• Player14560
  
• PLAYMCBS
  
• PMG_Cpt.Argen
  
• PMG_Cpt.Ghebbo
  
• PNE_Spyder
  
• PoP_Bikejoker
  
• porkboyoung
  
• Potato-Corner
  
• PoWeR_HoUsE_9zA
  
• PoX_BurneR
  
• PR-77
  
• PrB.Zenky333
  
• PrimouF
  
• Prof.Dr.CATLI
  
• Profetea.GS
  
• Prox.ima
  
• Psephophorus
  
• PSYCH_SkillZz
  
• Psycho3ngine
  
• Pulse_4life
  
• PULSE_AUT
  
• Puma_Hood
  
• Purple-Nurple-M
  
• QIQI_3-
  
• QruGTA
  
• QuillerKoo
  
• qwaszx804
  
• RADEIIITORIK
  
• Rainbowwwwwwwww
  
• raivaSIX_iiDude
  
• Rayanlebrette
  
• RAZER_LAMON
  
• RC-XD_Medic
  
• RC-XD_Templar
  
• Real._.
  
• redemption_song
  
• RetroV1rus
  
• Rexyx3
  
• RIFLERZURR
  
• Ripper.Chann
  
• RiseOftGamer
  
• ritzelGdA
  
• Roadblock75Yolo
  
• ROBCP9
  
• ron2523
  
• RoronoaCato
  
• Rossikit
  
• RubberBullets5
  
• RusskiyPro
  
• ruxtiers
  
• S.A.W_Hekmatyar
  
• Saber-Arturia
  
• Saggy_sleeper
  
• ScaparHR
  
• Secret_Mr.487
  
• Secret_Mr.898
  
• SEK-FreshFish
  
• Selket.-
  
• Seno.ZyklonB
  
• severedan1
  
• Seyfert_Black
  
• SF7-3omda
  
• SF_Ultra_Killer
  
• SG1_shepard
  
• SGT-MajorDowns
  
• ShR1MpBa1Ls
  
• SHS-Xerbarus
  
• ShurtySchlumpf
  
• SickboyV
  
• Sidez_Wonka_GER
  
• Siegeurdad
  
• SIENZA
  
• SIimShaddy31
  
• Silent_Venom_X
  
• Sir_Lolsalot
  
• Siral4500
  
• SIXFRENZY
  
• SKD-Bryann
  
• Skinomi
  
• Skrillex1337
  
• sKs.Huy
  
• sKs.PhoKing
  
• SKWaD-Diablo
  
• SlimShaddy31
  
• SLK.Kamikaze
  
• Smile_Smile_Poi
  
• snake_evil
  
• Snip3rH3ad
  
• SniperAnonymous
  
• SnusMumrikennnn
  
• SonK1d
  
• Sonyaa-Blade
  
• Sopheus
  
• Sorry-IM-Drunk
  
• Sosharu
  
• Sowleye
  
• SPA--Xterminio
  
• spadeNo
  
• Spanky.AT
  
• Sparda_01
  
• Spe3DHAWX
  
• spr1ngs.
  
• spraykill89
  
• SQT-Hyuna
  
• Sr.Gatinho
  
• SSMCTOASTY
  
• st0ked88
  
• STARS_ShiNobi
  
• Stauff2009
  
• StB-Falcor
  
• StB-Markus
  
• Stevooo7
  
• STFUPloyd
  
• Sugartjts4572
  
• suicidisawayout
  
• super9mega
  
• SuperlegoSiege
  
• SuperSayajiin
  
• Swiift_Matt
  
• sY.M4I3X
  
• T.Arman
  
• T.FireBoy
  
• T.GRUDGE.
  
• TAG.verweikard
  
• Tamerus121
  
• Tape-Face
  
• TAS_RAVEN
  
• TAW_Redsoldier
  
• TC-Alex
  
• tc91310
  
• Team_Valor
  
• TEK.Margit
  
• TeMa_Stevooo
  
• Tempest__HD
  
• TGI_Stealth
  
• TGU-Jackbzz.esl
  
• TGU-Snp-NaCl
  
• TGxMr.Salterson
  
• The.One.Rep
  
• The_Scorpionman
  
• TheBombbb
  
• thedigitalmastr
  
• TheGassMan
  
• TheNewOneOP
  
• third.EyE.
  
• ThS_Yury
  
• Tic0w2001
  
• TK_Klaws
  
• Tobinat
  
• Tomfire.AT
  
• TomJonesIsAlive
  
• Tommy-Oliver
  
• TOXICON101
  
• TPE.Good
  
• TR-MaybeOneDay
  
• TrophyGamer.AT
  
• TSB-Netcode
  
• TsuKHi.ARRG-gl
  
• TummZ-_-
  
• Turnado2
  
• Turteltaube.3
  
• UBl-FixTheGame
  
• UBl_ItsEpi
  
• UG-Destroyer
  
• ultraSsak
  
• UnaBalita
  
• Unexpectality
  
• uRoG_Elkyos
  
• Ushiha_
  
• V4L4K....
  
• VAF_PeterPan
  
• VAF_Tinkerbell
  
• Valhalla___
  
• ValkGam
  
• VCM WIZE
  
• VdubMan.L1
  
• vedj.
  
• VegasLoL_88
  
• vei-quelouco
  
• verlasces
  
• VHS.Thiel
  
• Vination_Roocat
  
• Viriena
  
• Vocaloid3_Rin
  
• VZS-TropiCal
  
• Waka_-
  
• WalkyCZE
  
• Wanderings-xia
  
• Want3D_FuRy
  
• WarDaddy97-
  
• WAS.DIGGA.WAS
  
• WAS.DlGGA.WAS
  
• WasntAFairFight
  
• Wayne0729
  
• weggebumst
  
• WeiShou.
  
• whatman
  
• Whip.Me_Grandma
  
• WhiteBear.wc
  
• Who.is.Street
  
• Wildstriker55
  
• WinterhotGO
  
• Witnessing
  
• WoD_RatedR
  
• WojtsX
  
• Wolf_886
  
• Wootka24
  
• Wow123678
  
• wrath.Heist
  
• X_K-I-L-L-E-R_X
  
• xBurbank810
  
• xfyaws
  
• XIII-KingAegis
  
• xLimbo
  
• XSmaLiFe
  
• Xtream.Master
  
• xx.DAYWALKER.xx
  
• XYH_SAN-RISK
  
• Yachty_xfilms
  
• YaMug.TAW
  
• yBrasil
  
• YOOKIE90
  
• youzi233333
  
• YuzuLehiNori
  
• Zach.Bean
  
• Zaragrim16
  
• ZardoZz86
  
• Zellenleiter
  
• Zenobody
  
• ZeroGMOde
  
• Zeus-Lightning
  
• Zurglmi
  

FairFight Bans:

• God
  
• Juli-
  
• R3tarded-kitty
  

Can't find someone?

Maybe they got banned under a different name. Search users' aliases

Hall of QQ:

• The Ban Hammer
  
• Some hacker forum
  
• Paid hax
  
• extazya is sad
  
• but my hax were up to date
  
• my cheats weren't even on
  
• hacks weren't safe after all
  
• your hack got me banned
  
• premium wallhacks and still banned
  
• your cheat got me banned
  
• but I only cheated on the first day
  
• without using shit since 2 days
  
• happy to be banned
  
• will you refund my cheat
  
• wallhacks yesterday banned today
  
• kicked and banned
  
• permaban
  
• used every hack known to man
  
• it was a false positive
  

 
To get more cheaters included in the list, please reply to this comment with a username and a screenshot or video of the ban message. If your ban has been overturned, please contact me to have your name removed. If your ban was temporary (e.g. code of conduct abuses, illegal username, etc.), then there was no error, and your name will not be removed.
It's easiest for me if you submit in the following format:
\* \[UPLAY_NAME\]\(URL_OF_IMAGE\)
The slashes will keep it from link-ifying, so I can just copy-paste into the list once I verify the image. Your post will look like this:
* [UPLAY_NAME](URL_OF_IMAGE)
Which is exactly what I need to keep adding to the list. The brackets and parentheses are needed to make links.