Recent Forum Posts
From categories:
page 1123...next »

I find myself disappointed that this is being considered as a possible solution to the lack of mainlist slots remaining. This solution to me feels like it's been proposed without much thought into the potential consequences of it, and is essentially a bandaid that will gives us only a few months stay of execution. I also think it fails to acknowledge that should it proceed, its effectiveness will be damped by a likely influx of people with pre-existing drafts jumping at the opportunity to snap up lower number slots that would be opened under this proposal, giving us less time then we'd thought we'd get.

For this reason I am opposed to this proposal. I am also opposed to freezing the mainlist for similar reasons, and because it would, in my opinion, cause significant harm to the Wiki and the community surrounding it.

What we need is a multi-solution approach, one that takes into consideration the different factors at play and works to address them. Without that approach we'll be left kicking the can perpetually down the road, a state that will negatively impact the Wiki and stop the growth of recent years, something which I believe has been a hugely positive thing. But we can't begin a discussion on a multi-solution approach until we examine some of the factors that have lead us to this point.

1. Frequency of contests and events
I personally love seeing all the contests and events, both official and unofficial. It's truly a wonderful thing to see the community come together to create works around a shared theme or for each other in cases like Art Exchange. But it's also true that there has been a big influx in events/contests recently. This influx has contributed to the problem we currently face as many others have pointed out.

The solution here is an obvious one: to limit the number of events/contests. The specifics of this is something best left to the Contest Team, but I genuinely believe we don't need more than 3-4 contest/events a year. That number gives us breathing room, letting users recover and not get burnout, as is happening at the moment.

2. Lack of reading & reviewing incentives
Under the current system, unless a work becomes popular, is promoted heavily or is part of an event/contest, it's a coin toss as to how many readers it will attract. With an increased threshold, this means works that are underead would be unfairly unlisted or deleted. This has lead to two problems:

Problem A: Works that would be downvoted to -10 and deleted are left sitting in the low positives or negatives, taking up slots they wouldn't otherwise if they had the readership.
Problem B: Works that deserve more upvotes remain undiscovered. Most sit with anywhere from 0-30 upvotes and don't see any traction. Their only real chance at the spotlight is a front page feature or a random plug that takes off, but that's a shot in the dark at best.

To fix both these problems, we need to encourage more users to not only read more works, but to vote and comment on them. How to do do this is a difficult question. People have limited time in their days to read, and many want to dedicate that time to reading works they know they'll likely enjoy. But there are a few possible solutions:

- Reward for reading, voting and reviewing such as front page features.
- Contests or events exclusively revoling around reading, voting and reviewing works.
- Promoting these works on our socials or other locations so they're seen by a wider group of potential readers/voters/commenters.

There are likely more possible solutions, and I think regardless of what steps we take next, something to get more people reading must be addressed.

3. Critique imbalance & lack of established user participation
One of the arguments for raising the threshold is that it'll prune works that needed more time in the crit oven. I don't deny that there are likely a lot of works (some of which are my own) that could use more time to cook, and that affording them that opportunity and reposting them could see them net more readers, votes and comments. But the problem with this solution is an imbalance with critique, something that isn't the fault of anyone but rather a natural consequence of time.

For newer authors without established friends in the community, they're often left recieving critique from other new authors, many of whom are still learning to write for the website and how to critique. This limits how effective critique can truly be for this group. And while the occasional established author, paired with resources like Deer College's Moth Squad, help to mitigate this somewhat, it still leaves newer authors in the dark. This in turn leads to works being posted when they're not ready. While they're not worthy of deletion, they also don't stand out, leaving them sitting in the low positives or negatives.

Established authors on the other hand have often formed friend groups who they use for writing advice and critique. They keep to themselves for the most part, thus taking with them valuable critique knowledge and the experience of writing in the SCP format, leaving newer authors without the opportunity to have experienced eyes look over their works and to see how experienced critters critique.

If we want to fix the works being posted that need more critique, we need to incentivise these established users to return to places like Deer College. Programs like Reviewer's Spotlight work to an extent, but more can and should be done if we want to see an improvement in this area.

4. Harsh Critique
Somewhat related to the above point, but harsh critique and the lack thereof, is another point I've seen being raised. If more works recieved harsher critique, both before and after posting, it's believed that this would stop works that need more time from being posted early, and if they are, see them reach the deletions threshold. I don't deny that harsh critique is a good thing, but only to a point. Harsh critique is not inherently useful because it's harsh. What is useful is honest and actionable critique.

I know many people, myself included, have sometimes held back on critiquing, voting or commenting on a work when we shouldn't have. Perhaps we only novoted, or didn't mention something to avoid upsetting the author. Once again, no one is at fault. It's human nature for us to avoid upsetting other people. But if we want to see the kind of change we need, we must start encouraging more honest critique and actionable critique. Is it's not honest, and if the critique isn't actionable, then it does nothing to help and at its worst could make people leave the site.

How to make this kind of change if difficult to say, but I believe it needs to happen if we want to see mainlist slots fill up slower.

5. Popular authors vs newer/unknown authors and promotion
It's a fairly obvious truth that if you ask users what they'd rather read, more often then not read the work of an popular author over the a new/unknown author. This isn't because the community is bias against newer/unknown authors, but rather if you have limited time to read, you want to read something you'll like. An popular author has already gotten a reputation for works of a certain quality, making reading theirs far less of a gamble. There is also the element of author style and that if a user likes an authors style and/or their previous works they become a more obvious choice to read.

This makes thing harder for newer/unknown authors, plain and simple. While it is possible for a first time author to publish something that gets 100+ in the first week or more, it's an outlier. Most new/unknown authors will struggle to get reads unless they get lucky with a front page feature, sustained plugging from other users or extensively promote it themselves. Pairing that with the site's subpar discoverability means there are many works that could reach 50+, 100+ or higher that are sitting below 50. This proposal will mean many of these works never get a chance, as they'll be deleted or unlisted if they're below 20 upvotes.

These works deserve better. Their authors deserve better. We can and must start making it a more even playing field between the popular and newer/unknown authors. And its not something that's a difficult task either. On IO I do what I can to share works both popular (1730, 682, etc) and works that are new or need some love. Front page features also help in this regard to an extent, but many of the features have already been read and voted on by a large number of users. Possible ways to make things more even include:

- Contests where users with only a few works or who have a low total upvote count are the only ones who can participate. Alternatively, an event were users submit works under a certain upvote threshold for people to read, the winner being the work that gets the most upvotes during the events duration.
- A spot on the front page for low upvote works that people can submit works to. For example, works that are at least +15 but no more than +30.
- Site news having a section where 1-2 works below 50+ or similar are given a brief highlight.


In sum: I oppose this proposal. I believe that the only way to truly fix this problem is a multi-solution apporach that takes all the factors that contributed to the lack of slots and addresses them.

Staff discussed the appeal; the consensus was to decline. Kufat, Ari, afto, storm voted to decline.

Ban remains in place; PM sent.

Re: AI Record - Elias Solemn by ZynZyn, 13 May 2026 07:13

Noting that new site member wzttrToqewzttrToqe (account age and site membership 2 days) recently coldposted the following page, which has multiple indicators of AI-generation: https://scp-wiki.wikidot.com/scp-9132 page title "The host of a theatre"

Revision 0 retained:

Excerpts of note:

Mobile Task Force Omega-19 (“Curtain Call”) was formally disbanded following Incident 9132-Δ; the six surviving members remain under indefinite psychological observation at Site-77’s secure psych wing, where three have begun scripting their therapy sessions without prompting.

It is emphasized that SCP-9132 does not violate rules. It rewrites them the moment they are uttered, documented, or even thought. Every Foundation action—lockdown announcements, test logs, internal memoranda, and the text you are currently reading—carries the potential to become scripted dialogue. Personnel are reminded: the instant you acknowledge the stage, you have already accepted a role.

Documented archetypal variants include:

- Amphitruo-variant (oldest verified form): Three-handed mask fused to antique Roman armor; capable of intangibility except for one perpetually shifting weak point; forces victims to recite original scripts under threat of energy detonation; demeanor loud, childish, and oscillating between manic laughter and sudden tonal shifts that suggest multiple voices speaking through the same mouth.
- Plautus-variant: Tribal mask locked in a permanent smirk with leaf motifs; exhibits aggressive, animalistic behavior; repeats the phrase “I am Chaos” while launching relentless attacks.
- Silenus-variant: Large-mouthed mask with protruding zigzag structures; surrounded by a water-like evaporation aura; floods enclosed spaces and summons grasping aqueous appendages to drown or restrain targets.

Addendum 9132-6: Final Status Report

Containment is not failing. Containment is theater.

Global incidents of unscripted public performances resulting in mass disappearances have increased 340% in the past eighteen months. The entity no longer requires a physical vessel to operate; collective human attention now appears sufficient to sustain manifestations. Selected recent events include:

Compare with user's only forum comment: https://scp-wiki.wikidot.com/forum/t-17872357/scp-9132#post-8027689 post title "author"

hey guys I'm the creator of the scp 9132 i have ben working on it for a long time since i was trying to create a mix of cosmic horror and theatrical horror i hope you enjoyed the read and it was heavily inspired by the entity O Anfitrião

User has no other edit history (not a sandbox member). Permanently banned, PM sent. Kufat supporting.

AI Record - wzttrToqe by ZynZyn, 13 May 2026 07:10
Re: Username Log by ZynZyn, 13 May 2026 07:06

as i said when this came up in 19cord, i'm currently doing much more reading than i have in many years as a member of tagging, and the stuff that i've been reading for my work has been overwhelmingly mediocre. this doesn't much get to me — i'm not particularly bothered if there's a lot of mediocre stuff on the wiki that nobody reads — but i view the problem of reader burnout as an extension of the problem of series filling up too fast, and if the threshold can solve that problem, i figure that's an additional point in its favor.


poet

So uh. I'm leaving a second comment here. Feel like it wouldn't make sense to combine it into the first one because it is addressing a completely different topic. But. Anyway!

I think we're going about this from the wrong angle. Slots are a concern. The timing of 10kcon is a concern. However from reading O4 and talking to people in 19cord, and from reflecting on my own time as a reader here on the wiki over the past several years, I think we may also be suffering from a much greater problem, fundamental to the purpose of the site as a whole, that this proposal also seems to be addressing; and, frankly, in my opinion, seems to be being haphazardly mixed into this apparent discussion on 10kcon and slots:

Not enough people want to read articles.

I think it's understandable that the focus has been on the slots rather than on reader burnout. After all, slot exhaustion is very concrete. It's easy to measure. It's easy to calculate a line of best fit implying "at this rate, we will run out of slots at X time." It's very hard to dismiss.

Reader burnout, on the other hand, is precisely the opposite. It's abstract. It's incredibly hard to measure, being made up of the aggregate of thousands of peoples' opinions, many of whom wouldn't respond to a hypothetical reader survey, or might not even have accounts on the site. Any group of people voicing their concerns can be dismissed as a vocal minority speaking only for themselves and nobody else. It's very easy to dismiss.

From my very limited and haphazard polling of users in 19cord, I've noticed a few common threads:

  • The idea that most of the stuff on the wiki sucks, or is 'mid', or is otherwise uninteresting.
  • The idea that it's difficult to find high-quality content to read on the wiki.
  • The idea that one can only find things worth reading through recommendations from others, as opposed to checking the site one's self.

So, I'd like to ask everyone here. What do YOU read on the SCP Wiki? How often do you find articles that you find truly compelling? Do you read more than you did before? Do you read less? I invite all of you to reply to this comment with your answer. Obviously, this is just a convenience sample. But, like. We can use it as a basis for collecting further data, if needed.

Personally, to start things off, I've found that most of what I read is technically well-constructed, but a lot of it just. Isn't very interesting to read. I find myself having to pull myself through it, to stop myself from just clicking off and doing something else. I think I used to find reading SCP wiki articles more interesting, I think in part because many of the ideas that are commonplace in articles (memetic agents, reality benders, amnestics, reality anchors, normalcy orgs, etc.) just aren't new to me anymore. They've gone from fascinating, sometimes horrifying thought experiments, akin to the central gimmick in an episode of Star Trek… to just, like, mundane parts of the setting. Oh, and, also, I think shortform is deceptively difficult, and a lot of articles on the site do not meet the high bar required of it. In a work of shortform, you're effectively trying to build reader investment and interest in a package much smaller than what you'd have normally. You have to make it way more punchy than it would be otherwise, or layer far more meaning into every word of the article.

Anyway, rant about works on the wiki aside, I think this "+20-after-a-year deletion threshold" (or, hell, even +30) could, in principle, adjust the incentive structure of the wiki to encourage more readership. Authors will be more inclined to put more effort into their articles, to actually put themselves into the headspace to think about where their article might be a year from now. In theory, this will result in the average article being better, which will lead to readers having a better experience on the wiki, and thus reading more.

From the reader side, this system will encourage readers to vouch for works they found truly good. Like, imagine you're a reader, and you've discovered a true hidden gem, several months old, sitting at +15, and it actually speaks to you. Now, not wanting it to be deleted, you actually feel compelled to promote it — to get it over the +20 mark. Hell, this is, I think, even an argument for making the timeline much shorter (say, a month, rather than a year), because it is easier for one to conceptualize "huh, this thing is gonna be gone in 30 days if I don't shout about it from the rooftops!" than 365 days.

On the other hand, there are quite a few negatives with this plan:

  • How will retroactive enforcement of this policy work? Like, isn't it unfair that articles could be immediately subject to this "+20-or-delete" threshold without giving readers a chance to see and evaluate them with it in mind, or authors to revise them with it in mind?
  • How do we stop low-rated but nonetheless compelling, highly polarizing, highly engaging articles from being deleted? Statue That Doesn't Move comes to mind — it has a low rating, but it sparked a hell of a lot more discussion than most articles, and, as far as engagement and readership goes, that's what really counts.
  • How does this new incentive structure impact the risk of vote brigading?
  • …Do we actually need to delete things to improve readership? What if we could simply improve discoverability or improve the wiki's incentive structure in other ways?

Edit: Realistically, after mulling it over, I think the biggest benefit of this "+20-after-a-year deletion threshold" is simply the fact that it acts as a deterrent against people posting things that aren't very good, and acts as incentive for readers to promote things they really like. Like, the deletions themselves make little meaningful difference, because, by the time you go and delete the middling +15 year-old article… hardly anyone's reading it anymore anyway. And, like, if readers are measuring the quality of articles by their vote count, then, why not just… ignore any old article with a low rating? Why not simply create curation systems in place to enforce this? I mean, we already have those, in the form of Top Rated This Month, Top Rated This Year, Top Rated Of All Time, et cetera.

Overall I think this deletion threshold change could work. However, I don't know for sure if it's the best option, when the main benefit of this deletion threshold approach in particulalr is specifically to incentivize people to prevent it from ever being used in the first place. Perhaps there is a more direct approach we could use.

Anyway, my other main goal with posting this message is to get people to consider this issue from the standpoint of the SCP Wiki reader experience. Anyway yeah.

Okay so I have caught up on this thread and would like to give my two cents now. I fully support option A1 for a variety of important reasons. The first one that comes to mind is that the current rate of posting to the mainlist is unsustainable in every sense of the word, this is not a temporary problem limited to the date at which 10kcon occurs and will continue to have sweeping consequences if left unaddressed. As is shown in the danjon post above, a maintenance of our current momentum will have our remaining slots filled in June of this year. I would like to emphasize this would be an unprecedented kcon turnaround of *less than a full year* which would lead to insane burnout in our overworked contest team which I feel the need to remind everyone is less than ten individuals. In my opinion changing curation standards is the most reasonable way to shift our behavior, to be frank I think the discussions of freezing the mainlist are a nonstarter that would simply kick the can down the road the second the mainlist is unfrozen. The consequences for the community are as obvious as they are detrimental. Not only would there be a mass exodus of authors (and readers) there would also be a backlog of mainlisters waiting to be posted which would spell the death knell of the wiki as it is drowned in content and we are forced to host the first back-to-back kcon experience.

In contrast, changing our curation standards is simple, has far more popular support, and actually mediates this existential problem long term. To put it very plainly we can have too much of a good thing and the dose makes the poison. Our current curation standards were set up over a decade ago and were well suited to a fundamentally different social environment on the wiki, as it has grown these curation standards have guided us into a corner and I think it is high time we change them for the long-term health of the community. Minus ten to deletion was not passed down on high from god and it makes sense that we should change our curation standards with changing times.

I would also like to caution us against reviving the -ARC system which was killed by staff in no uncertain terms 5 years ago and for good reason. Namely that we are not an archive and attempts to use the wiki as one dilutes the purpose of the website in a multitude of ways. In the event an article is deleted under this new system there is nothing stopping users from reuploading it on any number of archiving services like Ao3. There is no compelling reason to archive works that for all intents and purposes have very little cultural impact and will likely be read by very few users when buried in an archival format that most users avoid in general.

Back to the proposal at hand, I also think it has a variety of positive impacts on community health aside from making it where our contest team doesn’t go postal and kill all of us. It also encourages people to actually fight for any hidden gems they may believe in instead of letting them coast unnoticed for literal years. Not only that but it gives authors an opportunity to workshop that idea and give it a second chance on the wiki where it might fare better. Honestly as a regular reader of the wiki it has become very obvious that our population of people posting has far outpaced an infrastructure that was built with a more critical and small userbase in mind. It only makes sense that we shift how we do things in an effort to course correct before we end up slamming into a brick wall.

I have more I could add in a further post on some of these topics (especially when it comes to other solutions I believe we should be implementing as well) but I've fleshed out a lot of my opinions in the public staffcord thread and I believe this is a decent enough summary of my positions on the matter.

Right now my biggest problem with this proposal is that it's difficult to discuss on its own merits when it's proposed as a solution to slots filling up quickly. In my opinion it puts undue pressure on this idea and incentivizes swift action with broader consequences (i.e. trying to maximize articles deleted rather than trying to reflect the community's standards of quality). I think the idea of adjusting the deletion threshold does have merit in its own right, as readership and authorship patterns have changed. But it is not a good solution to the slot crisis.

My personal preference is to simply let the slots run out; there are plenty of other ways to write for the site and restrictions breed creativity. We'd see some incredible new takes on our GoI formats, tales, Foundation formats, and such. But that said, there is clearly a lot of community opposition to that solution that I don't think we should discount. As such, I've come around to creating a sort of temporary "side-list" of SCPs that will be moved into Series XI when it opens up after the kcon slots are assigned. This is still a very temporary solution and is completely kicking the can down the road, but it buys us time to figure out a better solution without the time pressure we are currently facing. And then we can discuss deletion threshold changes on their own merits.

Edit to add: If we're going to change the threshold I don't think we should do a full year. Realistically the vast, vast majority of articles are going to settle into the general range they'll live in within a month or two, so a secondary threshold shouldn't go much further than that. Requirements for author role in 19cord and access to draft critique standards will need to be adjust as well in response to this if the threshold is above +10 as well.

I really don't like kicking the can down the road like this. But, with what Prismal said about a permanent solution to a temporary problem, I'm coming around to something like this as a temporary solution to a temporary problem. We'll have more time to figure out a more permanent fix in the meantime if we do this.

i don't like this idea for pretty much all of the reasons you've listed, though the flooding of slots post-10000 would at least be blunted if we do the very popular (and, in my opinion, very sensible) thing and start opening more than 1000 slots at a time after 10000.


poet

May or may not elaborate on this more later, but I'd like to throw this suggestion into the ring for yall to dissect: What if we only removed the articles from the mainlist temporarily? To this end, I propose the following:

  1. Unlist all articles over a year old and below a certain vote threshold. In a more general sense, we should come up with some easy-to-calculate heuristic for determining if a slot is "unlist-worthy" — ideally, articles that both readers and authors alike wouldn't mind being booted off the site. I'll call these Group U ("Unlisted") articles
  2. Allow authors to put new articles into Group U articles' former slots. These new replacement articles will be called Group R ("Replacement") articles.
  3. Run 10kcon as normal.
  4. Move all Group R articles to Series 11. We can decide slot assignment via upvote count, similar to kcon rules, or use some other method (e.g. random, or resolving disputes by lottery). We've been working on better infrastructure for calculating and tallying up slot assignments, so if we did do a kcon-style "highest upvotes gets first pick", it hopefully won't be as arduous as past cons.
  5. Relist all Group U articles in their original slots.

There are many knobs we can tweak here to determine how this process goes:

  • The vote threshold, time threshold, or overall algorithm we use to decide whether an article falls into Group U.
  • How unlisting actually works (do we unlist them? or do we just make them "foundation-format" articles temporarily, under a consistent URL scheme that doesn't conflict with the mainlist?)
  • The rate at which Group U are re-listed (in principle, we could gradually re-list them over the course of a year or two to avoid 300 slots suddenly being filled up immediately after 10kcon. However, this would complicate slot assignment, since "reserving" S11 slots for Group R articles would delete the whole purpose by making those slots unavailable. Some Group R authors would have to accept taking a S12 or S13 slot etc.)

Positives:

  • Nothing actually gets deleted.
  • We get 300+ more slots before 10kcon, potentially more if we find we need to tweak the threshold.
  • In effect, this solution will sacrifice 11kcon for the sake of 10kcon, since potentially hundreds of additional slots will fill up after 10kcon compared to normal. However, this is an improvement over sacrificing 10kcon, due to:
    • The fact that (I would assume) 10kcon's plans are far more fleshed out than 11kcon's.
    • Moving 10kcon closer to the present would upend every single already-planned event that was supposed to happen before it, and that people have, to some extent, already planned for. Conversely, events between 10k and 11k can (presumably) be more easily shuffled around.
    • We now have more time to think through what changes we can make to the site, and even test them. Any effects they have will be multiplied by this increased time period.
    • We now have more time to implement changes to stem the tide of new articles. This is useful, because it potentially gives us the option to not have to apply them retroactively.
    • The monumentality of the 10k event (big round number make monkey brain neuron activate!!!).
  • We can, if necessary, combine this with another solution (e.g. a rate limit).
  • Most of the work of moving the articles and renaming the numbers can be automated.
    • While any automated tooling would have to be tested to prevent breakage, a generic, automated tool for moving/editing pages would give us latitude to do that testing ahead-of-time, effectively amortizing the effort it'd take to implement this solution over a longer stretch of time.
    • Every action this automated tool would perform is reversible, meaning that while we should be careful, we don't need to be extremely careful:
      • We would need to rename pages to move Group U pages out-of and back-into the mainlist; and we would need to rename Group R articles to move them to S11. This can be trivially reversed by just renaming the page again to its original slug.
      • We would need to edit the slot #s in Group R pages once they move from their original slots to S11 slots. This can be trivially changed by just reverting the revision that changed the slot #s. That said, there are admittedly a few edge cases to consider here — image URLs with hard-coded SCP numbers in them, for example.

Negatives:

  • Does not actually free up any slots over the long term. We are "kicking the can down the road," so to speak.
  • Group U articles lose around a year's worth of visibility. Granted, we could mitigate this somewhat more by moving these articles to "foundation-format" articles rather than unlisting them wholesale.
  • Would be quite a hassle to move all the slots. I could theoretically automate this, but this wouldn't save much, because such a solution would need to be battle-tested to ensure it doesn't break and cause damage. Amending this to just say it'd take quite a few person-hours to get this done. I don't think it's unmanageable, but it's certainly not trivial.
  • Group R articles' backlinks will break.
    • We could potentially mitigate this by having Group U articles move to S11 slots, and have Group R articles stay in Group U's former slots — presumably, because they're very low-visibility articles that few people are interested in, fewer backlinks of Group U's will break. Of course, this also makes it less obvious how we decide where to put them, and also could go against the authors' wishes if the specific number is important.

Anyway uh. Yeah. What do you think? I must admit, I don't like this idea. However, every other idea I've seen proposed, I don't like even more. So uh. Yeah. I'm warming up to raising the deletion threshold to +10 or +20 some more. My main concern was the community's response (lowkey, as a reader I won't be missing all the barely-positively-rated articles. there's literally more than 20000 works on the site) so the fact that on O4 ppl seem to be, on average, speaking out in favor of the threshold increase makes me more inclined to support it. I still share Prismal's and UncannyClown's reservations on it being unfair to spring such a drastic change in policy upon hundreds of articles that were never created with it in mind, but, eh. Idk. This is a shit statue fanfic writing community at the end of they day. Having your article (that, let's be honest, nobody's read in the past month) being taken off the site ain't that big a deal.

“Casting out” I think is a little strong, as everything will be maintained, with only a url suffix

that's how it'll be perceived, though. there's already people in the 04 thread saying that they would look at such a list as an undesirable "lesser works" list, and we can say that such a perception is the fault of the beholder, but that is how we would be influencing people to look at the list via our selection criteria. an -arc list made up of pieces subject to the secondary curation threshold is necessarily a list of pieces that remained either obscure or unpopular for a long period of time, and the general perception (at least among people who support the threshold) is that this happens mostly for good reason. i don't think that users would look at an -arc list as a list of equally desirable and successful scp articles, and i think archival is worth doing anyway if we're doing retroactive application, but i think we've got to acknowledge that we're absolutely not casting these pieces as equally worthy when we remove them from the mainlist for their failure to meet a certain curation threshold. we at least owe the people we'd be doing this to some level of honesty.


poet

Yea, it’d be about 10%, weighted more towards the last three series according to danjon’s graph.

I think 30 is pretty reasonable, even considering the amount, given that deletions will not be considered and votes, content, and discussion will be maintained. “Casting out” I think is a little strong, as everything will be maintained, with only a url suffix.

Further, this singles out and makes more visible these works. If there’s any concern there is stuff in these margins that should have seen more love, then they’ll have a better chance to do so. For those who believe what’s here isn’t worth keeping on site, the added prominence may see more falling into deletions, and this specific subset of articles shrinking.

I’d be open to suggestions for alternative naming conventions with the caveat and emphasis that they retain SCP branding in all respects. I think ARC is perfectly serviceable, as we are long, long past the point/community that held onto works to deride them. That association simply isn’t there for anyone outside the oldest of oldheads

ETA to clarify:

they retain SCP branding in all respects

One thing I think best to keep in mind about readership is that the kinds of people in this thread, and even those in the O4 discussion, and further yet, those that frequent chat on the daily are but a small subset of all readers on this site. There are hundreds of active, casual readers that form a significant chunk of votes cast site-wide.

To more casual audiences, SCP is the draw. This is known.

There are of course plenty of casual readers that enjoy tales, goi formats, reading randomly, etc, but by and large our site’s namesake is bar far the most popular. An ARC mainlist would allow for affected SCPs to keep that same level of notability as the mainlist to the massive, massive audience that doesn’t obsessively frequent the site.

this idea makes retroactive application more palatable to me personally, though i think 30 is far too drastic — that encompasses, what, 10% of all scp articles ever as of the last time we talked about this? i'm not comfortable casting that much stuff out under pretty much any circumstance, even with a blunting mechanism like an -arc list (we'd also have to call it something else because the -arc label is too loaded but that's a minor consideration).


poet

It has all of the benefits of deletions cap raising (clearing space to offset 10k, removing underperforming works from the mainlist) with none of the drawbacks (arbitrarily changing deletion standards, “destroying art”).

Everything is not only maintained but given prominence. Keeping it as a distinct series alongside the Alt mainlists.

It retains all feedback and discussion — if critique and improvement is a concern, a deletions proposal should also require sending all feedback to the authors writ large. With Option A, that’s dozens of pages of comments from a mere 300 works. An ARC mainlist retains all feedback.

Codifying these as ARC I think might help these works in a way Underread and Underrated never could. Even with years on the sidebar, people didn’t really give it much attention beyond the small subset of the community that appreciated it as a service/curation method.

I would argue though that perhaps what kept U&U from being effective in drawing attention to these works is its very name. It’s a naming convention that actively works to make the contents therein feel underwhelming.

An ARC list, held in the same place as Js and EXes, keeps them as successful SCPs in all but URL. To the casual reader, they’re just as inviting, just as valid, as a mainlist to browse and enjoy.

Ngl you're probably right. I'm back and forth on +30 but I get the philosophy.

While I do think the idea of a higher threshold theoretically could work, I feel that the 1 year grace period would only help with 10kon (assuming it applied retroactively), and do little to nothing to delay the gap between future Kcons. For example, if the main list fills up three months before 11Kon, then we're just at this point again, as the low-performing articles in Series 11 would be only eligible for deletion in 3 months to almost a year, assuming a gap of 1 year exactly between Kcons.

If we were to implement this proposal, I think the grace period would need to be much shorter. Something around the range of 1 month in order to keep a healthy flow of articles. I think there's other additional steps that could be taken to help mitigate the core issue, but it's probably best to stay on topic for now.

As stands, I'm in favor of Option B but with a vastly shorter turnaround time, as mentioned above. If that's not an acceptable answer, then I move for no action at all, as I feel the current options don't do enough to solve the issue at hand.

I'll probably have a more in depth comment later but from what I've seen a mainlist freeze is massively unpopular with basically everyone not on staff. I really don't think we should seriously consider a freeze for more than a week or two.
Edit: I cannot stress this enough there are people in 19cord saying that they might leave the site if the mainlist is frozen. Please do not freeze the mainlist.

Edit: I misread the part about archiving I think that's a bad idea that does nothing to help this problem except free up slots, which isn't even the main reason to do this.


Smells like success.

page 1123...next »
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License