Difference between revisions of "Leaking"

From QBWiki
Jump to navigation Jump to search
 
(9 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
Most instances of leaking are inadvertant (e.g. discussing a single question with someone who hasn't yet played a set), and are easily dealt with by disclosing the leak to an editor so that appropriate remedies can be made. However, in recent times, threats to leak a question set deliberately, and thus invalidate the work of all the writers and editors, have become more common.  
 
Most instances of leaking are inadvertant (e.g. discussing a single question with someone who hasn't yet played a set), and are easily dealt with by disclosing the leak to an editor so that appropriate remedies can be made. However, in recent times, threats to leak a question set deliberately, and thus invalidate the work of all the writers and editors, have become more common.  
  
−
==Notable Incidents==
+
==Notable Incidents Of Threatened or Actual Leaking==
  
−
===2018 Chicago Open===
+
===2015 NAQT Packet Amnesty Incident===
  
−
[[2018 Chicago Open]] was head-edited by [[Auroni Gupta]], and spawned a late-stage production dispute that raised broader concerns about set ownership and editorial authority. During the final week before the tournament, the set was significantly incomplete (approximately 60–70% finished), prompting editors to recruit additional writers, including [[Eric Mukherjee]] (who was serving as a medical intern at the time), to help complete the set under significant time pressure. Shortly thereafter, another contributor, [[Eliza Grames]], objected to Mukherjee’s involvement and had him removed from the set due to a political dispute (despite the two of them having worked on the same sets prior). She reportedly conditioned her continued participation on his exclusion, and further indicated that she would withdraw her contributions - or potentially release questions publicly - if her condition was not met.
+
Before the advent of Locklizard, it was very common for old NAQT packets (particularly SCT and ICT) to be [[Underground packet trade|scanned and sent between teams]], because they were the only packets without electronic versions available. After NAQT determined this was happening, in Winter 2014-5 they [https://hsquizbowl.org/forums/viewtopic.php?p=296090 offered amnesty] to anyone found to be sending packets, in exchange for revealing the names of anyone who had sent them material. This caused a large uproar and ongoing bad blood between NAQT and the wider community, as being forced to "name names" was very controversial.
  
−
The situation escalated due to the timing and stakes: the set was incomplete, the tournament was imminent, and the threatened withdrawal or exposure of content would have significantly disrupted production. While the set was ultimately completed and played, the incident sparked [https://hsquizbowl.org/forums/viewtopic.php?p=348142 extensive community discussion] about the norms governing question ownership, contributor rights, and the limits of acceptable conduct. In particular, it highlighted the tension between a contributor’s right to withdraw labor and the expectation that contributors not take actions that would materially harm a set already in production.
+
===2017 NAQT ICT Incident===
  
−
===2026 Holy Leak Week===
+
:''Main page: [[Anti-NAQT sentiment#"The Barbarism of Monetization"|The Barbarism of Monetization]]''
  
−
Holy Week 2026, dubbed '''Holy Leak Week''' or the '''Week of Fools''', saw multiple instances of threatened leaking or other question security malfeasance. These incidents reinforced ongoing concerns about set security, editor conduct, and the risks posed by individuals with access to unreleased materials. These were the Multi-Set Incident (Tuesday, March 31) and the LIQBA Termination Incident (Friday, April 3).
+
In 2017, [[Ike Jose]] accused [[Eric Mukherjee]] of obtaining a copy of [[2017 ICT]] from another team despite [[Penn]] having not played it, and subsequently threatened to bar him from playing [[2017 Chicago Open]] (a tournament which Ike was head-editing, and which had no relationship to NAQT) and threatened NAQT sanctions for both [[Penn]] and [[Chicago]] (whom Ike was convinced sent the packets to Eric). Ike's vigilante attempt to enforce [[NAQT]]'s intellectual property rights led to a [https://hsquizbowl.org/forums/viewtopic.php?t=19875 larger conversation about NAQT's norms around charging for packets] (which no other collegiate quizbowl organization does); a compromise was reached in which NAQT now provides protected PDFs via [[Locklizard]].
  
−
====2026 Multi-Set Leak Incident====
+
===2018 Chicago Open===
  
−
The '''2026 multi-set leak incident''' refers to a major quizbowl misconduct case involving [[Samin Asif]] of [[Seven Lakes|Seven Lakes High School]], who violated the security of multiple tournaments. While serving as a contributor to the set [[MONSTER]], Asif accessed and publicly read questions from the unreleased set (and several others) in a Discord server without authorization. This prompted his removal from the set, reports to the Quizbowl Misconduct Committee and sanctions from NAQT. Following these sanctions, Asif escalated the situation by privately threatening to leak the set unless certain demands were met within a fixed timeframe, and by making unfounded public accusations that other contributors had similarly compromised question security.
+
[[2018 Chicago Open]] was head-edited by [[Auroni Gupta]], and spawned a late-stage production dispute that raised broader concerns about set ownership and editorial authority. During the final week before the tournament, the set was significantly incomplete (approximately 60–70% finished), prompting editors to recruit additional writers, including [[Eric Mukherjee]] (who was serving as a medical intern at the time), to help complete the set under significant time pressure. Shortly thereafter, another contributor, [[Eliza Grames]], objected to Mukherjee’s involvement and had him removed from the set due to a political dispute (despite the two of them having worked on the same sets prior). She reportedly conditioned her continued participation on his exclusion, and further indicated that she would withdraw her contributions - or potentially release questions publicly - if her condition was not met.
  
−
After the team implemented safeguards to protect the material, including initiating copyright registration and sending formal notices, Asif spitefully released [[HISTONE]], a separate set he had head-edited, thus derailing multiple already-scheduled mirrors. The episode prompted broad community backlash, leading to Asif’s removal from the Seven Lakes quizbowl team, firing from [[LIQBA]], and further sanctions from [[NAQT]].
+
The situation escalated due to the timing and stakes: the set was incomplete, the tournament was imminent, and the threatened withdrawal or exposure of content would have significantly disrupted production. While the set was ultimately completed and played, the incident sparked [https://hsquizbowl.org/forums/viewtopic.php?p=348142 extensive community discussion] about the norms governing question ownership, contributor rights, and the limits of acceptable conduct. In particular, it highlighted the tension between a contributor’s right to withdraw labor and the expectation that contributors not take actions that would materially harm a set already in production.
−
 
 
−
====2026 LIQBA Termination Incident====
 
  
−
The '''LIQBA incident (2026)''' - sometimes referred to as the '''Good Friday Massacre''' (after the day on which it occured) involved the termination of [[Billy Beyer]], head editor for the Long Island Quizbowl Alliance (LIQBA), by CEO [[Joe Feldman]] following a prolonged pattern of verbal abuse, disrespect, and unprofessional conduct toward colleagues over the course of nearly a year. After his contract was terminated, Beyer [https://hsquizbowl.org/forums/viewtopic.php?p=411451#p411451 reportedly disputed that he was bound by confidentiality obligations] and implied he might take adverse actions involving internal LIQBA materials.
+
===2026 Multi-Set Leak Incident===
  
−
Shortly after his termination, Beyer allegedly deleted internal company documents and unreleased packet materials related to upcoming LIQBA tournaments while still in possession of access. LIQBA had anticipated potential issues and maintained offline backups, preventing permanent loss of content. In response, Feldman [https://hsquizbowl.org/forums/viewtopic.php?p=411447#p411447 issued a public warning] to the quizbowl community to monitor for any unauthorized distribution of LIQBA questions.  
+
The '''2026 multi-set leak incident''' refers to a major quizbowl misconduct case involving Individual X, a high schooler, who violated the security of multiple tournaments. While serving as a contributor to the set [[MONSTER]], Individual X accessed and publicly read questions from the unreleased set (and several others) in a Discord server without authorization. This prompted his removal from the set, reports to the Quizbowl Misconduct Committee and sanctions from NAQT. Following these sanctions, X escalated the situation by privately threatening to leak the set unless certain demands were met within a fixed timeframe, and by making unfounded public accusations that other contributors had similarly compromised question security. When confronted, he leaked a separate set he had head-edited ([[HISTONE]]), thus derailing multiple already-scheduled mirrors. The episode prompted broad community backlash, leading to X's removal from quizbowl at large.
  
 
[[Category:Quizbowl basics]]
 
[[Category:Quizbowl basics]]
 
[[Category:Quizbowl lingo]]
 
[[Category:Quizbowl lingo]]
 
{{c|Quizbowl concepts}}
 
{{c|Quizbowl concepts}}

Latest revision as of 14:01, 7 April 2026

Leaking is the accidental or deliberate release of an entire question set or revealing the contents of single questions before it is clear, to someone who may play it in the future, or to someone who hasn't paid for it (primarily the case of NAQT sets). With the widespread use of of buzzpoint data/advanced stats (which display the full text of each question) and electronic packets, packet security is more important than ever.

Most instances of leaking are inadvertant (e.g. discussing a single question with someone who hasn't yet played a set), and are easily dealt with by disclosing the leak to an editor so that appropriate remedies can be made. However, in recent times, threats to leak a question set deliberately, and thus invalidate the work of all the writers and editors, have become more common.

Notable Incidents Of Threatened or Actual Leaking

2015 NAQT Packet Amnesty Incident

Before the advent of Locklizard, it was very common for old NAQT packets (particularly SCT and ICT) to be scanned and sent between teams, because they were the only packets without electronic versions available. After NAQT determined this was happening, in Winter 2014-5 they offered amnesty to anyone found to be sending packets, in exchange for revealing the names of anyone who had sent them material. This caused a large uproar and ongoing bad blood between NAQT and the wider community, as being forced to "name names" was very controversial.

2017 NAQT ICT Incident

Main page: The Barbarism of Monetization

In 2017, Ike Jose accused Eric Mukherjee of obtaining a copy of 2017 ICT from another team despite Penn having not played it, and subsequently threatened to bar him from playing 2017 Chicago Open (a tournament which Ike was head-editing, and which had no relationship to NAQT) and threatened NAQT sanctions for both Penn and Chicago (whom Ike was convinced sent the packets to Eric). Ike's vigilante attempt to enforce NAQT's intellectual property rights led to a larger conversation about NAQT's norms around charging for packets (which no other collegiate quizbowl organization does); a compromise was reached in which NAQT now provides protected PDFs via Locklizard.

2018 Chicago Open

2018 Chicago Open was head-edited by Auroni Gupta, and spawned a late-stage production dispute that raised broader concerns about set ownership and editorial authority. During the final week before the tournament, the set was significantly incomplete (approximately 60–70% finished), prompting editors to recruit additional writers, including Eric Mukherjee (who was serving as a medical intern at the time), to help complete the set under significant time pressure. Shortly thereafter, another contributor, Eliza Grames, objected to Mukherjee’s involvement and had him removed from the set due to a political dispute (despite the two of them having worked on the same sets prior). She reportedly conditioned her continued participation on his exclusion, and further indicated that she would withdraw her contributions - or potentially release questions publicly - if her condition was not met.

The situation escalated due to the timing and stakes: the set was incomplete, the tournament was imminent, and the threatened withdrawal or exposure of content would have significantly disrupted production. While the set was ultimately completed and played, the incident sparked extensive community discussion about the norms governing question ownership, contributor rights, and the limits of acceptable conduct. In particular, it highlighted the tension between a contributor’s right to withdraw labor and the expectation that contributors not take actions that would materially harm a set already in production.

2026 Multi-Set Leak Incident

The 2026 multi-set leak incident refers to a major quizbowl misconduct case involving Individual X, a high schooler, who violated the security of multiple tournaments. While serving as a contributor to the set MONSTER, Individual X accessed and publicly read questions from the unreleased set (and several others) in a Discord server without authorization. This prompted his removal from the set, reports to the Quizbowl Misconduct Committee and sanctions from NAQT. Following these sanctions, X escalated the situation by privately threatening to leak the set unless certain demands were met within a fixed timeframe, and by making unfounded public accusations that other contributors had similarly compromised question security. When confronted, he leaked a separate set he had head-edited (HISTONE), thus derailing multiple already-scheduled mirrors. The episode prompted broad community backlash, leading to X's removal from quizbowl at large.