About: MoAD Conflict   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

The MoAD Conflict was a disagreement over naming rights between two alliances claiming the MAD acronym. On August 3 Mercenaries of Absolute Destruction leader The Russian posted a recruitment thread on the CN boards for "MAD". Mutually Assured Defense, which had been using the acronym for 8 months, took note of the thread. Later that evening, leaders of the two alliances began private negotiations, which ultimately failed. On August 4 the MoAD ambassador to Darkfall entered Mutually Assured Defense's embassy there to seek help in the conflict from Darkfall, with whom MoAD was considering a merger. Mutually Assured Defense took the trespass as proof that two MADs would be too confusing, and that its own sovereignty would be put in jeapordy if MoAD ever made an enemy. With negotiations going

AttributesValues
rdfs:label
  • MoAD Conflict
rdfs:comment
  • The MoAD Conflict was a disagreement over naming rights between two alliances claiming the MAD acronym. On August 3 Mercenaries of Absolute Destruction leader The Russian posted a recruitment thread on the CN boards for "MAD". Mutually Assured Defense, which had been using the acronym for 8 months, took note of the thread. Later that evening, leaders of the two alliances began private negotiations, which ultimately failed. On August 4 the MoAD ambassador to Darkfall entered Mutually Assured Defense's embassy there to seek help in the conflict from Darkfall, with whom MoAD was considering a merger. Mutually Assured Defense took the trespass as proof that two MADs would be too confusing, and that its own sovereignty would be put in jeapordy if MoAD ever made an enemy. With negotiations going
dcterms:subject
dbkwik:cybernation...iPageUsesTemplate
abstract
  • The MoAD Conflict was a disagreement over naming rights between two alliances claiming the MAD acronym. On August 3 Mercenaries of Absolute Destruction leader The Russian posted a recruitment thread on the CN boards for "MAD". Mutually Assured Defense, which had been using the acronym for 8 months, took note of the thread. Later that evening, leaders of the two alliances began private negotiations, which ultimately failed. On August 4 the MoAD ambassador to Darkfall entered Mutually Assured Defense's embassy there to seek help in the conflict from Darkfall, with whom MoAD was considering a merger. Mutually Assured Defense took the trespass as proof that two MADs would be too confusing, and that its own sovereignty would be put in jeapordy if MoAD ever made an enemy. With negotiations going nowhere, on August 5 Mutually Assured Defense issued a public ultimatum to MoAD demanding they change their name. The ultimatum carried a deadline of 8:00 pm Cyber Nations Time on August 7, lest there be war. At approximately three hours before the deadline, MoAD presented a document to Mutually Assured Defense proposing the name Mercenaries of Absolute Death and Destruction, which would carry the acronym MADD. In the ensuing discussion it became clear that the proposed new name was chosen by MoAD "out of spite" to "try and piss off" Mutually Assured Defense. 8 minutes before the deadline, Mutually Assured Defense rejected the proposal and gave MoAD/MADD until 10:30 CN time to come up with a "reasonable" proposal. Within an hour, the MoAD/MADD government officially proposed the name CN Mercenaries, which was accepted by Mutually Assured Defense and thus ended the conflict without loss of life or infrastructure.
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software