SCP-3309

SCP-3309
By: (user deleted)
Published on 13 Apr 2018 18:17

What this is

A bunch of miscellaneous CSS 'improvements' that I, Croquembouche, use on a bunch of pages because I think it makes them easier to deal with.

The changes this component makes are bunch of really trivial modifications to ease the writing experience and to make documenting components/themes a bit easier (which I do a lot). It doesn't change anything about the page visually for the reader — the changes are for the writer.

I wouldn't expect translations of articles that use this component to also use this component, unless the translator likes it and would want to use it anyway.

This component probably won't conflict with other components or themes, and even if it does, it probably won't matter too much.

Usage

On any wiki:

[[include :scp-wiki:component:croqstyle]]

This component is designed to be used on other components. When using on another component, be sure to add this inside the component's [[iftags]] block, so that users of your component are not forced into also using Croqstyle.

Related components

Other personal styling components (which change just a couple things):

• RSO Component — Rounderhouse

Personal styling themes (which are visual overhauls):

• Magnus Web Format — DrMagnus
• Flopstyle CSS — Lt Flops
• Blankstyle CSS — HarryBlank
• Placestyle CSS — Placeholder McD
• Jakstyle — JakdragonX

CSS changes

Reasonably-sized footnotes

Stops footnotes from being a million miles wide, so that you can actually read them.

.hovertip { max-width: 400px; }

Monospace edit/code

Makes the edit textbox monospace, and also changes all monospace text to Fira Code, the obviously superior monospace font.

@import url('https://fonts.googleapis.com/css2?family=Fira+Code:wght@400;700&display=swap');
 
:root { --mono-font: "Fira Code", Cousine, monospace; }
#edit-page-textarea, .code pre, .code p, .code, tt, .page-source { font-family: var(--mono-font); }
.code pre * { white-space: pre; }
.code *, .pre * { font-feature-settings: unset; }

Teletype backgrounds

Adds a light grey background to <tt> elements ({{text}}), so code snippets stand out more.

tt {
  background-color: var(--swatch-something-bhl-idk-will-fix-later, #f4f4f4);
  font-size: 85%;
  padding: 0.2em 0.4em;
  margin: 0;
  border-radius: 6px;
}

No more bigfaces

Stops big pictures from appearing when you hover over someone's avatar image, because they're stupid and really annoying and you can just click on them if you want to see the big version.

.avatar-hover { display: none !important; }

Breaky breaky

Any text inside a div with class nobreak has line-wrapping happen between every letter.

.nobreak { word-break: break-all; }

Code colours

Add my terminal's code colours as variables. Maybe I'll change this to a more common terminal theme like Monokai or something at some point, but for now it's just my personal theme, which is derived from Tomorrow Night Eighties.

Also, adding the .terminal class to a fake code block as [[div class="code terminal"]] gives it a sort of pseudo-terminal look with a dark background. Doesn't work with [[code]], because Wikidot inserts a bunch of syntax highlighting that you can't change yourself without a bunch of CSS. Use it for non-[[code]] code snippets only.

Quick tool to colourise a 'standard' Wikidot component usage example with the above vars: link

:root {
  --c-bg: #393939;
  --c-syntax: #e0e0e0;
  --c-comment: #999999;
  --c-error: #f2777a;
  --c-value: #f99157;
  --c-symbol: #ffcc66;
  --c-string: #99cc99;
  --c-operator: #66cccc;
  --c-builtin: #70a7df;
  --c-keyword: #cc99cc;
}
 
.terminal, .terminal > .code {
  color: var(--c-syntax);
  background: var(--c-bg);
  border: 0.4rem solid var(--c-comment);
  border-radius: 1rem;
}

Debug mode

Draw lines around anything inside .debug-mode. The colour of the lines is red but defers to CSS variable --debug-colour.

You can also add div.debug-info.over and div.debug-info.under inside an element to annotate the debug boxes — though you'll need to make sure to leave enough vertical space that the annotation doesn't overlap the thing above or below it.

…like this!

.debug-mode, .debug-mode *, .debug-mode *::before, .debug-mode *::after {
  outline: 1px solid var(--debug-colour, red);
  position: relative;
}
.debug-info {
  position: absolute;
  left: 50%;
  transform: translateX(-50%);
  font-family: 'Fira Code', monospace;
  font-size: 1rem;
  white-space: nowrap;
}
.debug-info.over { top: -2.5rem; }
.debug-info.under { bottom: -2.5rem; }
.debug-info p { margin: 0; }

▷ Show Code ◁

@import url(https://fonts.googleapis.com/css2?family=Montserrat:wght@600;700&display=swap);
 
/* Centered Header Sigma
 * [2021 Wikidot Component]
 * By Lt Flops (CC BY-SA 3.0)
 * Forked from:
   * Penumbra Theme by EstrellaYoshte
 * Also based on:
   * Centered Header BHL by Woedenaz
**/
 
/* ---- VARS ---- */
 :root{
     --titleColor: hsl(0, 0%, 95%);
     --subtitleColor: hsl(60, 62%, 85%);
     --lgurl: url(https://scp-wiki.wdfiles.com/local--files/component:pride-highlighter/lgbtqp_logo.svg);
}
 
/* ---- SITE BANNER ---- */
 #header,
 div#header{
     background-image: none;
}
 
 #header::before{
     position: absolute;
     width: 100%;
     height: 100%;
     content: "";
 
     background-image: var(--lgurl);
     background-position: center top;
     background-repeat: no-repeat;
     background-size: auto 9em;
     opacity: .33;
}
 
 #header h1,
 #header h2{
     float: none;
     margin-left: 0;
 
     text-align: center;
}
 
 #header h1 span,
 #header h2 span{
   /* Hide the Existing Text */
     display: none;
}
 
 #header h1 a::before,
 #header h2::before{
   /* Style the New Text */
     font-family: "Montserrat", "Arial", sans-serif;
     text-shadow: none;
}
 
 #header h1 a::before{
     position: relative;
     bottom: .15em;
 
     color: var(--titleColor);
 
     font-size: 115%;
     font-weight: 700;
}
 
 #header h2::before{
     position: relative;
     top: .1em;
 
     color: var(--subtitleColor);
 
     font-size: 130%;
     font-weight: 600;
}
 
 #header h1 a::before{
   /* Set the New Text's Content From Variable */
     content: var(--header-title, "SCP FOUNDATION");
}
 
 #header h2::before{
     content: var(--header-subtitle, "SECURE - CONTAIN - PROTECT");
}
 
/* ---- SEARCH ---- */
 #search-top-box{
     top: 1em;
     right: 0;
}
 
 #search-top-box-form input.button{
     margin-right: 0;
}
 
 #search-top-box-input,
 #search-top-box-input:hover,
 #search-top-box-input:focus,
 #search-top-box-form input[type=submit],
 #search-top-box-form input[type=submit]:hover,
 #search-top-box-form input[type=submit]:focus{
     border-radius: 0;
     box-shadow: none;
 
     font-size: 100%;
}
 
/* ---- TOP BAR ---- */
 #top-bar{
     right: 0;
     display: flex;
     justify-content: center;
}
 
 #top-bar ul li ul{
     border-bottom: 1px solid hsl(0, 0%, 40%);
     box-shadow: none;
}
 
/* ---- LOGIN ---- */
 #login-status{
     top: 1.1em;
     right: initial;
 
     color: hsl(0, 0%, 87%);
}
 
 #account-topbutton{
     border-color: hsl(0, 0%, 87%);
 
     font-size: 100%;
}
 
/* ---- PAGE TITLE ---- */
 .meta-title,
 #page-title{
     text-align: center;
}
 
/* ---- BREADCRUMBS ---- */
 .pseudocrumbs,
 #breadcrumbs{
     text-align: center;
}
 
/* ---- MOBILE DISPLAY ---- */
 @media (max-width: 767px){
     #search-top-box{
          top: 1.85em;
          width: unset;
    }
 
     .mobile-top-bar{
          position: relative;
          left: 0;
          display: flex;
          justify-content: center;
    }
 
     #login-status{
          top: 0;
          right: 0;
    }
 
     #header .printuser{
          font-size: 0;
    }
 
     #header .printuser img.small{
          margin: 0;
 
          transform: translate(6px, 4px);
    }
 
     #my-account{
          display: none;
    }
 
     #account-topbutton{
          margin-left: 2px;
    }
}

• 

  close

  Info

  ---

  X

  SCP-3309: Where We Go When We Fade, Fade Away
  By: Lt Flops (Author Page) & PhamtomGuy (I currently only have one other article. I encourage you to read it here: SCP-3969)
  Published on 13 Apr 2018

  ---

  Inspired by the Pataphysics Department by Rimple.

  With coding help from Westrin.

  ---

SCP-3309

SCP Series 4 » SCP-3309

NOTICE FROM THE FOUNDATION RECORDS AND INFORMATION SECURITY ADMINISTRATION

---

The file you wish to access, “SCP-3309,” describes an unpredictable narrativic anomaly intersecting with multiple subnarrative layers. Narrativic inoculation is required, as this document contains several embedded narrativohazards.¹ Personnel without inoculation against such anomalies may experience a narrative paraphrasing event.

Are you sure you wish to continue?

Narrativic inoculation disseminated.

Sometimes we don't fade until it's too late.

Until we've withered, withered, to the bone. And at the end, there's nothing left. It's forgotten. Memories, hopes, dreams; we're all forgotten. How can we know that people even have these memories, these hopes, and these dreams? Who could forget us if there was nothing there to begin with? We fade from the minds of others, but not from our own. We live with it until we can't live any longer. Until we forget there was ever any way we could live in peace. And then, that's when we fade away.

Fade, fade away.

Inoculation completed! You may continue.

Item Number: SCP-3309

Object Class: Keter

Special Containment Procedures: All documentation on anomalies affected by SCP-3309 is to be preserved in a paraphrased format and kept within the RAISA Archive database. After the containment of an instance, all personnel assigned to the affected anomaly must undergo amnestic treatment and transfer to unrelated projects.

---

Description: SCP-3309 is a phenomenon in which catalogued anomalies spontaneously disappear. Items affected by SCP-3309 have included anomalous objects, entities, locations, and conceptual structures. Anomalies affected by this phenomenon appear to lack a causal relation; SCP-3309 activity is indicated by a note of unknown origin (designated SCP-3309-1).

Between 24 and 36 hours before the disappearance of an anomaly, SCP-3309-1 appears appended to the item's file. Documents undergoing SCP-3309 become wiped from all known file systems, including Protected Site-01 and RAISA Archives. Afterward, the anomaly itself becomes effectively neutralized or otherwise disappears.

The contents of SCP-3309-1 are as follows:

If you are not the author and you want to rewrite this article, you may reply to this post asking for the opportunity to do so. Please obtain permission from the author.

SCP-3309 affects backups created for disappearing documents. SCP-3309 also affects the documents of anomalous items encountering SCP-3309; about 71% of disappearing documents are connected to other, unaffected anomalies. This leads to a weakening in the Foundation's anomaly containment network, potentially escalating to an ADK-Class “Complete Anomalous Destabilization” Scenario.

---

Footnotes

1. Narrativohazard: A cascading hazard affecting elements of a narrative and its mode of transmission, often leading to their mutual destruction. Definitions of a narrative differ among cultures but typically describe a story and its medium.

N.B.: Anomalies such as SCP-2747, SCP-5309, and SCP-5875 fall under this categorization.

---

ADDENDA MATERIALS

---

I. Ethics Committee Tribunal

   ▷ TS/3309/EYES ONLY

Since its prime emergence, SCP-3309 has affected an average of 40 anomalies per month. Researchers assigned to SCP-3309 have identified an emerging pattern and developed a list of criteria:

• Affected items are documented as having been contained with excessive containment procedures, such as chambers constructed from heavy-duty titanium alloy. This indicates either a misunderstanding of the anomaly's nature or an unprofessional level of care taken to contain it.
• The affected item itself is powerful enough to threaten a K-Class “End-of-the-World” Scenario. Documentation outlines only partial consequences of the anomaly, and any Provisional Containment Procedures typically align with that of the first criteria.
• The affected item's documentation — including any added supplements — is poorly written, improperly formatted, or filled with logical and grammatical errors.

Based on these observations, the containment team has proposed Project: TAPERED SPEAR. TAPERED SPEAR outlines the adaptation of these criteria for use against high-risk anomalies to neutralize them. As this contravenes the Foundation's mission, an Ethics Committee special tribunal has contested the execution of TAPERED SPEAR.

The results of this tribunal are as follows:

PROJECT: TAPERED SPEAR

TRIBUNAL RESULTS

---

FOR: 21
AGAINST: 20
ABSTAIN: 2

OUTCOME: TAPERED SPEAR is authorized. SCP-3309 is pending secondary reclassification to THAUMIEL-Class.

---

II. Project: TAPERED SPEAR

   ▷ TS/3309/EYES ONLY

Preliminary testing of SCP-3309 to determine the suitability of a Thaumiel reclassification has officially begun. Attached is an experimentation log, the results of which will determine a final decision.

PROPOSAL EXCERPT

---

PROPOSAL: Use SCP-3309 to neutralize SCP-4463: A complex water-based spatial anomaly capable of flooding North America within 50 years.

---

DESCRIPTION: SCP-4463 is a water-based anomaly affecting parts of the Chihuahuan Desert in the state of Arizona. SCP-4463 describes the gradual transformation of a substantial area of the desert into an equal area of wetlands.

Since the 1990s, desertification of southeastern Arizona has occurred at a rate of 2 km² per month. This desertification increased at a rate of 0.5% per year until 2008, when 1 200 km² of previously arable land had been rendered incapable of bearing healthy vegetation. In response, the government of Arizona considered this phenomenon an ecological disaster and enacted plans to reverse the spread of desertification. This occurred as a response to mass protests by members of the Pascua Yaqui Tribe in the neighbouring Tucson region beginning in November 2006.

In August 2008, 60% of desiccated topsoil per square metre began transformation into water by an unknown anomalous effect. At present, 45% of the previously desertified area has transformed into wetlands, preventing any native animal or human development in this territory.

---

FURTHER ACTIONS TAKEN: SCP-4463's file was updated to contain heavy grammatical errors and significant inconsistencies among related effects of the anomaly. Various fabricated addenda and an unrelated image depicting a large ocean wave were also added.

---

RESULT: SCP-4463 was erased from all Foundation databases within a 28-hour period. After further research and observation into the former location of SCP-4463, its risk had been nullified, and the area again became desertified.

After continued debate and experimentation involving 19 different anomalies, SCP-3309 has passed the second stage of voting within the Ethics Committee special tribunal. SCP-3309 has been additionally classified as Thaumiel and authorized for use in TAPERED SPEAR. The first round of post-reclassification research involving 49 anomalies is under way.

RESEARCHER NOTE

---

I don't understand how one round of testing could burden a man like this. I think I saw my first white hair this morning — or an entire patch of white hairs?

Fading to dust — how does that feel? Would it burden my senses the way an illness might? Or might it leave me numb? I think, if I had to go out, I would want to continue feeling, even into my final moment. To know I'm still here, as everything else fades away.

There's something wrong.

I've locked myself in my office. I'm going numb. This isn't what I would have wanted. But the end doesn't much care about one man's wants and needs, does it? There is nothing, nothing.

Did we ever find out where those neutralized anomalies went? Surely it can't be so straightforward, to do what we did — to see justice without repercussions. That's unlike us. But it feels like everyone, everyone except me, forgot what happened.

Is it that simple? Have we simply forgotten?

I don't want to be forgotten.

---

—Researcher Adamo Smalls
Memetics and Infohazards Division

---

III. [ ]

His heart is a crater, and we have filled it.

Researcher Smalls did not attend the latter parts of our testing this evening. He no longer appears on any of our itineraries, and his name has been expunged from my project files. If there has been an immediate project alteration or a change in schedules that I was not informed of, please let me know immediately.

—Researcher John Calzaroli

John, are you all right? Yes, there was indeed a 3-hour schedule change, but no “Researcher Smalls” has ever been involved with this project. I can assure you — no one named Researcher Smalls has worked with us.

Please, John, take a break; the stress must be getting to you. I know that testing has been cutthroat these past few weeks. I feel it, too.

—Dr. Robert Woods

You're mistaken. You must know the man. He's the most exceptional memeticist we have.

But, if you truly claim there is no Researcher Smalls, well, there must be something more to this. SCP-3309 erases anomalies and the files associated with them. We haven't discussed where exactly these anomalies go, and I'm sure we've all had our questions. As far as I remember, Smalls was assigned to SCP-3309 when it was first discovered.

Are we certain personnel aren't also being deleted?

[ACCOUNT DELETED]

What the hell?

—Dr. Robert Woods

FROM: [ACCOUNT DELETED]

[MESSAGE DELETED]

---

[END OF FILE]

---

/

SCP-3309

The Abyss Gazes Back

---

‡ Licensing / Citation

Cite this page as:

"SCP-3309" by Lt Flops and PhamtomGuy, from the SCP Wiki. Source: https://scpwiki.com/scp-3309. Licensed under CC-BY-SA.

For more information, see Licensing Guide.
Licensing Disclosures

Filename: buttons.png
Author: Lt Flops
License: Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0)
Source Link: SCP Foundation

Filename: rss_icon.png
Author: Lt Flops
License: Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0)
Source Link: SCP Foundation

For more information about on-wiki content, visit the Licensing Master List.