Process DMCA request

2023/12/2023-12-28-fuhrerredux.md

@@ -0,0 +1,83 @@
+While GitHub did not find sufficient information to determine a valid anti-circumvention claim, we determined that this takedown notice contains other valid copyright claim(s).
+
+---
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am authorized to act on the copyright owner's behalf.
+
+**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
+
+No
+
+**Does your claim involve content on GitHub or npm.js?**
+
+GitHub
+
+**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
+
+I am authorized by the original owners of the Hearts of Iron IV mod, Fuhrerredux, to submit a report against the following repository for clear theft of their work.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
+
+Context to Situation - They were separated from the FX (Fuhrerredux) team following a series of disagreements over adherence to multiple guidelines. This division transpired over several months, signifying that it was not an abrupt occurrence. Subsequently, they initiated what they referred to as an "insurgency" and produced a new modification utilizing our code in its entirety, without providing any attribution. Moreover, they appropriated four unreleased trees for four specific tags, published them as their own, and presented them as original creations. However, it was easy to find out the truth behind this, by examining our publicly accessible GitHub repository.
+In a "troubling" turn of events, they resorted to fabricating discord messages, attempting to portray us as engaging in inappropriate behavior (being paedophiles and nazis). Additionally, they engaged in disruptive activities, such as raiding various servers, including the [private], [private] and and [private] servers, where they baselessly accused us of inappropriate conduct. Their actions extended to misleading influencers into believing these baseless allegations. Furthermore, they conducted raids on servers using alternate accounts, which we had banned for posting inappropriate content on our servers beforehand. We were unaware that these accounts were their alternate. Notably, they also shared graphic content that was child pornography. These activities persisted until they faced consequences.
+During this tumultuous period, they formed a partnership with an unreleased mod called [private]. We were able to persuade [private] to terminate this partnership, after addressing their concerns about our team's reputation. In response, their team, specifically their owner, resorted to making false claims of inappropriate behavior against [private] as well. One of their [private], who had prior experience with [private], knew that these accusations were unfounded and took it upon themselves to rectify the situation. Although this [private] was subsequently removed from their team, he apologized to our team and rectified the damage caused by these false claims.
+Both the [private] and the [private] expressed remorse to us, as well as to [private], and made public statements to that effect. However, a few days later, a developer who had separated from [private] copied [private] unpublished code and incorporated it into the mod that falsely accused us of inappropriate conduct, naming it "Blue Dusk." This led to significant tensions within the [private] team, resulting in a considerable amount of drama. The [private] of Blue Dusk even claimed the [private] of the insurgent mod to be contemplating self-harm due to concerns for their safety, although it became evident that this threat was not carried out, as they continued to communicate on various servers. The response from the other [private] involved was rather uneventful.
+We believed the drama had subsided to a certain extent until recently, when our mod was either subjected to a DMCA takedown or mass reporting. The specifics remain unclear, but we suspect it was a DMCA takedown, as the swiftness of the action was unusual. Approximately ten minutes after we noticed our mod's takedown, they began inquiring about it in their server, making them the prime suspects at the time. Within a few hours, they also initiated a DMCA takedown on "[private]" further aggravating the situation. It is apparent that they may not fully comprehend the legal implications of a DMCA takedown, including the potential for perjury charges, as they appear to be primarily seeking attention and causing disruption. The following day, they pursued another DMCA takedown against "[private]," a mod with which our [private] team had maintained positive relations. Throughout these events, they continuously harassed all mod teams involved and even engaged in stalking of individual team members. It is noteworthy that they previously acknowledged the falseness of their claims before resuming their disruptive activities.
+
+Original Work - https://github.com/fuhrerredux/fuhrerredux-mod
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+The entire repository
+
+https://github.com/Wickedonezzz/FR-IceBound
+
+The repository is based upon a clear act of theft with the original mod only to have more built upon it in a lackluster and weak manner.
+
+**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**
+
+Yes
+
+**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
+
+Access only to [private] of the team; [private] provide a more secure idea to us due to their role in our Hearts of Iron IV mod
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+N/A
+
+**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
+
+No, we have not
+
+**Is the work licensed under an open source license?**
+
+No
+
+**What would be the best solution for the alleged infringement?**
+
+Reported content must be removed
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+No, we do not
+
+**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.**
+
+**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
+
+**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.**
+
+**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**
+
+**So that we can get back to you, please provide either your telephone number or physical address.**
+
+[private]  
+[private], [private]  
+[private]
+
+**Please type your full legal name below to sign this request.**
+
+[private]