Sorry about that, I needed a few minutes to get everything in place.
PASSWORD: azure.cesium.salmon.21
Image Source: The first image is available from the United States Library of Congress's Prints and Photographs division.
Sorry about that, I needed a few minutes to get everything in place.
PASSWORD: azure.cesium.salmon.21
Image Source: The first image is available from the United States Library of Congress's Prints and Photographs division.
While I appreciate the attempt at verisimilitude by requiring an actual password to access a supposedly 'secure' doc, but it actually shatters suspension of disbelief. The reader is forced to check the discussion board to find out the password, which is more SoD breaking than just having it open.
Per your's and Moose's advice, I think I found a tasteful way to add the password into the actual article without breaking immersion. Better? Doesn't help?
This is incredibly obnoxious and I am downvoting until such time that it's removed. I maintain that SCP articles should be written in such a way as to make them printable. This is not printable.
I respectfully disagree with Raven and balance that vote with my own.
The mainlist is ostensibly a digital archive, in-universe. As evidenced by the 001 over page, among others. I wouldn't want to see this become common, but as a one-off it's a novel gimmick that fits the setting.
Concurring with wishun about it being reasonable to have occasional times where the article isn't immediately printable, but rather a digital archive. Another good example, presently rated at +276, is Mack's own SCP-895.
Concurring with Mackenzie. Rest of article is really good, but the password is just too much. Downvoted, will be changed if removed.
Cancelling vote, until I decide one way or the other.
Confirming that Image 1 is compliant and image 2 is taken by the author.
The article's tone is fluctuating a lot. I think one of the key words responsible of that should be "fleshy".
Besides that, I think this is a meh for me.
No vote
Made some changes to help make the tone more consistent. Also replaced the word "fleshy" with something a bit more clinical.
Ok, now it looks better. But what is exactly The real SCP still avoids me. I know that there is SCP-A, but i sdon't know its shape. I know there is SCP-1, but you made it with an uknown shape on porpuse. Now, what's exactly this SCP? Ok, you started abotu a lot of mixed WWII-era ships and aircrafts, but what about the Biological tissue? You started telling me metal, and from suddenly it became organic.
SCP-1246 is the actual ship
SCP-1246-A is the crew
SCP-1246-1 is the "captain" or the "controller"
As I was writing this out, I found that separating the other two was more fluid than referring them as "SCP-1246's crew" or "SCP-1246's captain".
Uh, your button leads to http://scp-wiki.wikidot.com/incident-log:1264-d-2 instead of http://www.scp-wiki.net/incident-log-1264-d-2
Might wanna fix that
To be specific, the former page does not exist.
http://scp-wiki.wikidot.com/incident-log-1264-d-2 would also work.
I fixed it. Didn't consider that changing the URL of the log page would affect this page.
h
I got through the whole article without ever knowing what 1264-A looks like. Am I assuming that they look like humans, except for X, Y, and Z? Also, you're bordering on the edge of excess detail, which is especially a problem when clarity is also an issue.
The incident log is kind of 'meh', and there's no reason for it to be Level 4. Maybe Level 2. Level 3 if I missed some implication of the log. Level 4 is usually "SUPER DUPER IMPORTANT STUFF OMG" and a lot of that is even Level 3, and all this was was a log of some random incident with a bit of dialogue that doesn't reveal much. (Correct me if I missed something.)
However, the overall idea is kind of neat, and I like some of that excess detail. Also, the trick with the password popup is entertaining, as I and others mentioned before. (Not everybody is gonna like it, but you can't please everybody. Also, FWIW, I don't see any problem with having the password on the page itself, and having some nonsense about how your user has been approved, which you basically already have anyway. We can pretend that in-universe it's ~computer magic~)
I think you could have more interesting elements in this piece, as well. The incident log stands out as a missed opportunity.
So on balance, +1, but I encourage you to take a second look at some of those issues.
I was leaving all the detail for SCP-1246-A in the autopsy, hoping that it would satisfy those clarity issues. I guess I could put in some quick details about SCP-1246-A in the actual description, but like you said, I need to put it and not overkill the article with detail. I could bump down the clearance to level 3, I see no problem with that. It does reveal things that I don't mention in the article (SCP-1246-1 is pretty deceptive and SCP-1246 can self-repair). Let me try and think of a way to subtly put that password in the page…currently nothing comes to mind, suggestions? (EDIT: see if that is any better.)
Echo and I tried to spice up the incident log with that addendum…but I guess it is still falling short, hmmm. I need to lean back in my chair and think. (EDIT: check the incident log with the changes I made, am I headed in the right direction?)
Thanks for the feedback, moose.
Saying that they otherwise appear to be human (if that is indeed the case) would help a lot.
It does reveal things that I don't mention in the article (SCP-1246-1 is pretty deceptive and SCP-1246 can self-repair).
This isn't especially interesting, though. I mean, it adds character, but it isn't any sort of big reveal that would need some kind of protection. It isn't really disturbing, horrifying, no religious or cultural implications, no real consequences for the information getting out that wouldn't also be felt if the main SCP description itself was leaked… etc. Why would the Foundation hide this information?
Actually, there's no reason not to put that in main article. In fact, it's kind of relevant information that seriously belongs in the main description, now that you mention it. Not necessarily the interview, but the fact that it can self-repair and is deceptive.
NP. Hope it helps :)
edit: also -
(EDIT: see if that is any better.)
Works pretty perfectly for me.
450 naval contact mines will be positioned around, over, and under SCP-1264.
Either that or 450 naval mimes. Y'know, whatever works.
I liked the password bit. Surprised that hasn't been used on other SCPs.
Sorry, how did we get this into containment? I may have missed something, but last we saw this in the article it was still roaming free (incidentally, before the Foundation caught this, and maybe even afterwards, this is totally Keter).
I will try to answer both of these questions. As for the classification, I was kind of torn on whether to actually classify as keter. Though it murders lots of people, it does not pose a threat to civilization itself and can't really cause that much destruction if it got out…with the exception of destroying the occasional fishing trawler every now and again. My point is, this thing really doesn't have a high frequency of incidents. It's been cruising the ocean for sixty years or so…and has only been seen by a number of ships somewhere in the double digits. That is my perspective, but I am totally not against changing the classification if I am wrong here.
The second part…I was trying to insinuate in the epilogue that it was eventually outrunned and outgunned. Once dead in the water, they hauled it out to the most remote spot in the ocean and strapped it down. If this needs to be elaborated on, I can certainly do that.
Many keters (682 for instance), don't pose much of a threat to civilization as a whole. We only know of the ships that saw it and lived to tell the tale. This thing has a pretty huge body count, and actively seems to hunt down and kill people. And it's not just doing it with stealth or preying on defenseless civilians (Well, it is, but it's powerful enough to go toe-to-toe with almost anything we have).
That's not really well conveyed. I would make that a bit more explicit.
Threat isn't how classification works, though. E: in my headcanon
Safe: Lock it in a box
Euclid: Lock it in a box and watch it for funny tricks
Keter: Oh my god, have a thousand automated turrets around this bloody box, which better have another box around it because he's gonna break out of the first.
That's not quite accurate. Something utterly uncontainable isn't going to be Keter unless it actually does bad stuff if it gets free.
The classifications are combination of the two. In a 'real' Foundation, there would be a containment classification and a threat classification. What we use is attempting to show two variables on a single scale. It's a trade off between realism and not really having a need for excessive detail, that sometimes results in misunderstandings like this.
butts
Usually the potential of the SCP escaping containment on its own and requiring excessive measures to contain it is grounds for classification as Keter.
I would consider the use of 450 naval mines and 160 kilotons of anchor rather excessive.