- stormfallen's proposal
- login
- 7000
- deletions
- JS accomplishments
- JS guide rewrite
- promos
- AI Images draft
- #site17 Helpers' Guide
- SoP wiki stuff
Bureau of the Archivist, minor curiosity X-25521-DU
Research priority 7 (minimal)
Automated translation text as follows:
Item #: SCP-001
Object Class: None
Special Containment Procedures: The continued existence and operation of the SCP Foundation, an organization dedicated to preserving normalcy and preventing the use of anomalous phenomena, is the primary containment method for SCP-001.
Description: SCP-001 refers to the historical tendency of civilizations which extensively utilized anomalous phenomena to catastrophically collapse, with a scale of destruction proportional to the civilization’s use of said anomalies.
Archivist’s note: Curiosity discovered on uninhabited planet 6544-FL, engraved into amorphous silicon dioxide structure. No further evidence of sapient life detected.
Item #: SCP-XXXX
Object Class: Safe
Special Containment Procedures: SCP-XXXX is installed on a flash drive and kept in a standard anomalous storage locker. Testing is prohibited.
Description: SCP-XXXX is a
Item #: SCP-7XXX
Object Class: Euclid
Special Containment Procedures: The building containing SCP-7XXX has been purchased by a Foundation front company and is used as office space for low-clearance clerical work. Access to SCP-7XXX is limited through one security checkpoint on each floor of the building.
Rev J, 2020-08-23: Standard disinformation protocol X-522 “Covid-19 Pandemic work-from-home policy” is to be used to explain the absence in formerly-present Foundation clerical staff. Access to SCP-7XXX is limited through one security checkpoint on each floor of the building. Researchers are to be offered ear protection to reduce any discomfort from SCP-7XXX-1’s vocalizations.
Description: SCP-7XXX is a spatial anomaly affecting a freight elevator shaft located in a former office building in Boston, Massachusetts, United States of America. Objects which reach where the bottom of SCP-7XXX would be are instantaneously translocated to its top. The shaft has no visible floor or ceiling, instead visually appearing to extend infinitely in both directions. Despite the looping property, activity at one of SCP-7XXX’s doors is not seen where the door would be located in iterations above or below the actual shaft.
SCP-7XXX does not contain an elevator car.
Rev J, 2020-08-23: SCP-7XXX-1 is Foundation Researcher Jason F. Lyman. On 2020-06-11, SCP-7XXX-1 fell into SCP-7XXX from the third story door while performing routine experimentation on the anomaly. SCP-7XXX-1 remains alive despite lack of sustenance, and has not been observed to cease screaming since it entered the anomaly. The cause of this has yet to be determined. SCP-7XXX-1 cycles through SCP-7XXX approximately every 0.84 seconds.
Addendum 1: At Ethics Committee direction after multiple failed attempts to retrieve SCP-7XXX-1, an attempt was made to provide it with a means to self-terminate. Several lethal weapons were introduced into SCP-7XXX
Investigation into using SCP-7XXX as a means to artificially extend the lifespan of high-priority personnel is pending.
When a new user joins Junior Staff
- Ask captain(s) to post in JS Appointments Thread, or ask permission to do it yourself.
- Add them to Master Staff List
- Add them to Meet the Staff listing
- Add them to JS listing of team hub(s), and listings for any sections they joined
When an existing JS joins a new team
- Ask captain(s) to post in JS Appointments Thread, or ask permission to do it yourself.
- Add new team(s) to JS’s listing in Master Staff List
- Add them to JS listing of team hub(s), and listings for any sections they joined
When a JS leaves staff
- Remove from Master Staff List
- Remove from Meet the Staff
- Remove from all team hubs
When an OS joins a new team
- (not yet implemented) Ask captain(s) to post in Team Changes Thread, or ask permission to do it yourself.
- Add new team(s) to OS's listing in Master Staff List
- Add new team(s) to OS's listing in Active Staff List
- Add them to OS listing of team hub(s), and listings for any sections they joined
stormfallen’s “accomplishments”:
- Updating 05 rosters as staffing changes happen
- Periodically checking rosters to ensure consistency and accuracy
- Updated Contact Staff after a considerable backlog of needed updates had accrued
- Writing up first posts for new Staff Team Changes thread and revised Junior Staff Appointments thread
- Reminding captains to update JS promotion thread :knife:
- Staffposting on rulebreaking Ideas and Draft Critique threads, and forwarding those in need of edits to moderators
- Routine surveying of recent forum posts for rulebreaking comments and bringing them to staff attention
- Answering queries in #site17 and #helpdesk
- Porting messages to and from SOSS and various community spaces (forums, #site17, SCPD, 19cord)
- Drafted guide for staff and active helpful users for #site17 and #helpdesk
- Researched licensing issues around AI-generated content, and working with LordStonefish to draft a Licensing statement regarding the allowance of said content on the Wiki
Things I hope to do by the end of January:
- Draft a “quick reference” guide for which pages need to be updated on 05 when each specific type of roster change happens
- Draft a discussion thread for “What should new staff know/what did you wish you knew?”
- Threaten Viv to update the JS thread at least three more times :knife:
This is a generalized guide to clearly explain the role of Junior staff, what they can and cannot do, and cultural expectations of Junior Staff. Please note that each team may have different expectations of their Junior Staff. A member of Junior Staff should consult with their team captain first and, if the captain's word disagrees with this document, to take their captain's word. For purposes of consistency, captains are discouraged from deviating from this document unless an explicit reason is provided and listed in their specific structure pages.
The purpose of the Junior Staff position
- Support/Trial Staff
- Junior Staff places conscientious and talented individuals in a position of support and authority, assisting staff with site duties. This is a way to gauge whether a user has the temperament, teamwork skills, critical thinking ability, and activity levels necessary for a higher staff role should they wish to advance.
What Junior Staff can do
- Promotions
- Junior Staff can eventually be recommended for promotion and promotions are given votes every three months. Junior Staff should defer to the team captains to determine exact requirements, if any, for promotion.
- Access to 05command and Staffchat
- All Junior Staff are allowed membership to 05Command, and may participate in policy discussions unless the discussion is explicitly restricted to other levels of staff. Junior Staff may create and post in non-disciplinary threads with permission from a full staff member. Junior staff may post in Disciplinary threads with permission of a Disciplinary team member. In both cases, they should denote their level and who gave permission. All Junior Staff are allowed access to the majority of staffchat, with the exception of #sensitive-staff-discussion, #AdCap, and administrative channels.
- Junior staff posts
- Junior Staff may make Junior Staff (JS) posts when speaking in staff capacity (e.g., explaining forum rules, clearing up policy misunderstandings). Note that Junior Staff posts should be made as directed/supported by an Operational Staff member or above, preferably one from the same team as the Junior Staff. Junior staff posts cannot be made to call stops to conversations.
- Calling out inappropriate user behavior
- Egregious rule-breaking may be addressed by JS whose team duties encompass the situation at hand. JS should notify another staff member (ideally their team captain or team supervisor) whenever they address rule-breaking in order for the case to be resolved officially. Any callouts of rule-breaking or repeated inappropriate behavior must be addressed by a junior staff post and an accompanying report to 05command. Addressing rule-breaking material not immediately relevant to one's team should only be done with permission from another (op staff or higher) staff member. Any disciplinary threads created by a junior staff member must first receive the approval of a member of the disciplinary team.
What Junior Staff cannot do
- Junior staff cannot vote on deletions, nor witness summary deletions.
- Junior staff cannot participate in any staff votes unless otherwise stated, and are explicitly forbidden from voting on promotions and bans.
- Junior staff cannot remove images from new articles, as image policy enforcement is considered on the same level as a deletion vote.
The cultural expectations of the Junior Staff position.
- Familiarity with rules and guides
- Junior Staff are expected to have working knowledge of rules and policies regarding user behavior, with specializations depending on individual teams. At minimum, a Junior Staff member should be familiar with the site rules, guide to newbies, and the anti-harassment policy.
- Sensitivity to community
- Junior Staff should be aware of what is considered acceptable and unacceptable behavior. They should refer to their mentors to develop a sense of how to help contribute to the culture and community development of the site. Their behavior should be held to a higher standard than non-staff members of the site.
- Posting on 05command
- Junior Staff should be aware that they may not understand or know all policy or greater context of existing policy. Junior Staff are recommended to only post in/create threads that are explicitly relevant to the team they are assigned to, and/or cases in which they were involved, with the approval of another staff member on their teams. Posts should be relevant, well-worded, and professional in tone. Junior Staff are expected to refrain from posting in threads that involve disputes between them and other users. Inappropriate use of 05command can be grounds for removal from their position.
This document was specifically created to address multiple confusions and discussions concerning what junior staff members can or cannot do, what their permissions are, what is expected of them and what they can expect from their superiors. In particular, several discussions asked if junior staff have any place making junior staff posts, accessing 05command, posting on threads in 05command, how they are promoted and how often they can be promoted, and how much authority they may be allowed on the site.
This document was created with several teams in mind: Wikiwalk, Licensing, and soon-to-be Images team had different roles for juniors than the other teams. Similarly, Forum Crit junior staff had a tendency towards more junior staff posts and weighed their junior staff posts with higher weight than other teams. Each team operated most effectively for their team, and so this document was designed to allow flexibility to those teams as necessary while encouraging consistency and clarity to prevent further confusion.
For the future, and in continued revisions, I would hope that this document be further edited, made more rigid or flexible, and be referred to often in order to clearly define the role and purpose of the junior staff position.
Please note that the junior staff position, as created by the previous admins before me, was originally exclusively a position of pre-operational staff, or "trial" operational staff and was never intended for the purpose of "helper" staff. However, as time went on, several team captains decided to deviate from this position as the need for junior staff but the unwillingness to give operational-level authority grew for specific teams that had very large projects to tackle. This document allows for their flexibility.
Lastly, the discussion for this document was given a two-week window before being put up. Click the link for that document. I would recommend future edits take the full consideration as to the purpose and history of the junior staff on the site thus far in continuing forward.
-SoullessSingularity, SCP administrator
Operational Staff Candidate | YES | NO | ABSTAINS | PROMOTED? |
---|---|---|---|---|
35 | 1 | 2 | YES | |
37 | 0 | 1 | YES | |
34 | 0 | 4 | YES | |
32 | 0 | 6 | YES | |
28 | 0 | 10 | YES | |
29 | 0 | 9 | YES | |
35 | 0 | 3 | YES | |
22 | 11 | 5 | YES | |
37 | 0 | 1 | YES | |
35 | 0 | 3 | YES | |
32 | 0 | 6 | YES | |
24 | 8 | 6 | YES | |
33 | 0 | 5 | YES | |
36 | 0 | 2 | YES |
Moderator Candidate | YES | NO | ABSTAINS | PROMOTED? |
---|---|---|---|---|
34 | 1 | 2 | YES | |
17 | 11 | 9 | YES | |
36 | 1 | 1 | YES | |
37 | 0 | 0 | YES | |
36 | 1 | 0 | YES | |
35 | 0 | 3 | YES |
Administrator Candidate | YES | NO | ABSTAINS | PROMOTED? |
---|---|---|---|---|
Cassandra_Prime does not match any existing user name | 37 | 0 | 0 | YES |
34 | 1 | 2 | YES | |
37 | 0 | 0 | YES |
The following was researched and written by LordStonefish and
stormfallen.
TL;DR: The Licensing Team does not allow the use of AI-generated images, such as https://thispersondoesnotexist.com/, to be used on the Wiki. Text-generating software such as Botnik is still allowed, so long as the software and all input text are compatible with CC-BY-SA 3.0.
Longer reasoning:
The status of AI-generated content varies greatly by jurisdiction. According to the World Intellectual Property Organization, in the US, Australia, Spain, Germany, and other jurisdictions, content created by a computer is not subject to any kind of copyright. The US Copyright Office has will only accept work from human beings, because of Feist Publications v Rural Telephone Service Company, Inc. 499 U.S. 340 (1991), where only “the fruits of intellectual labor that are founded in the creative powers of the mind” are protected under copyright. Australia has a similar case in Acohs Pty Ltd v Ucorp Pty Ltd. These nations hold that any work made by software can’t be copyrighted because a person didn’t make it. The CJEU take a similar but distinct stance in C-5/08 Infopaq International A/S v Danske Dagbaldes Forening which says that a work is original or not if it reflects the “author’s own intellectual creation.” These territories would likely allow the release of AI generated work under CC.
The only EU country that doesn’t hold to this is Ireland, which joins the UK, Hong Kong, India, and New Zealand in favoring the programmer as the copyright holder. The output can’t be released under CC unless the programmer allows it. The PRC just had a court case reaching similar conclusions, the media company Tencent was allowed to sue a plagiarist for copying an article from its AI-generated newswire.
Because our community operates in a range of jurisdictions, the Licensing Team's rule of thumb is to follow the most restrictive measure within reason. As such, the team does not believe it is currently possible to release AI-generated images under CC-BY-SA 3.0.
Uses of human-aided text generation, such as Botnik, are permitted under the exception that they are primarily the work of the author and not the software. Bald, unaltered, clearly noted uses of procedurally generated text as a narrative element, while unable to prosecuted, should be frowned upon and an effort made to ask the author to rewrite the section.
Further research:
- https://www.wipo.int/edocs/mdocs/mdocs/en/wipo_ip_ai_2_ge_20/wipo_ip_ai_2_ge_20_1_rev.pdf
- https://www.wipo.int/export/sites/www/about-ip/en/artificial_intelligence/conversation_ip_ai/pdf/ngo_creative_commons.pdf
- https://www.wipo.int/export/sites/www/about-ip/en/artificial_intelligence/call_for_comments/pdf/ind_guadamuz.pdf
- https://creativecommons.org/faq/#artificial-intelligence-and-cc-licenses
On-site guides: refer users to these first, and make sure to tell them if they have multiple tabs:
- http://scp-wiki.wikidot.com/comprehensive-guide-hub
- http://scp-wiki.wikidot.com/chat-guide - has tabs
- http://scp-wiki.wikidot.com/site-rules
- http://scp-wiki.wikidot.com/system:join - has tabs
- http://scp-wiki.wikidot.com/guide-for-newbies
- http://scp-wiki.wikidot.com/faq - has tabs
- http://scp-wiki.wikidot.com/how-to-write-an-scp - has tabs
- http://scp-wiki.wikidot.com/how-to-post-your-art-to-the-scp-wiki
- http://scp-wiki.wikidot.com/forum/t-10629348/new-draft-forum-policies
- http://scp-wiki.wikidot.com/forum/t-13282684/required-reading:how-to-use-this-forum-ideas
If a user needs to contact staff:
- http://05command.wikidot.com/contact-staff
- http://05command.wikidot.com/anti-harassment-main
- http://05command.wikidot.com/disciplinary-main
- #site11 for tech help
- #site34 for licensing help
- http://scp-wiki.wikidot.com/forum/t-14018096/rewrite-request-thread
User requests sandbox access:
- In order to invite you to the sandbox, we'll need your age and Wikidot account name
- .user $username
- Is this you?
- I've added you to the waitlist. Expect an invitation in your Wikidot inbox ( https://www.wikidot.com/account/messages#/invitations ) within 24h; if you don't have one within two days, please come back here. Wikidot's been worse than usual lately.
If a user is underage, don't inform them before getting their Wikidot account!
Site application issues:
- Ask for username
- (TODO) checking their app
- http://05command.wikidot.com/forum/t-1823153/username-log
- http://05command.wikidot.com/forum/t-14112105/applications-maturity-ban-log
- Check if age on profile matches age given in application
- Check for membership of blacklisted/greylisted sites:
- RPC: membership not allowed until they leave. (TODO: tell them why?)
- Backrooms: inform them that the head admin has been banned from SCP for harassment, and their application was denied to make sure they were informed of this. Their next application should be accepted.
- One of the admins on the Backrooms was involved in a major harassment case against SCP wiki members (http://05command.wikidot.com/forum/t-886884/anti-harassment-team-log-of-bans#post-4986204). We will not be asking people who want to join the SCP wiki to remove their Backrooms membership at this time, but we will have to ask you to be mindful of this context, and refrain from discussing the Backrooms in SCP wiki or chat.
- you’re a member of the backrooms wiki, and an admin there was involved in a big anti-harassment case here (the link: http://05command.wikidot.com/forum/t-886884/anti-harassment-team-log-of-bans#post-4780036). As such we have to request that you do not discuss backrooms on chat or on the scp site. You were declined to give us an opportunity to appraise you of the situation and the severity of it all. You’re allowed keep your membership if you choose, we just had to warn you of all this
- (TODO)
IRC issues
- (TODO)
Archetype | Class Skills | Skill Ranks | Saves | Weapon & Armor | Magic Talents | Summon Equipment | Bound Equipment | Arsenal Trick | Armor Training | Bind Implement | Boost Equipment | Quick Summons | Infinite Arsenal | |||||||||||||
1 | 5 | 10 | 15 | 20 | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16 | 18 | 20 | ||||||||||||
Blaster | X | X | C | C | C | C | X | |||||||||||||||||||
Bloodbinder | C | C | C | C | C | C | C | C | C | C | C | C | C | C | C | C | C | C | X | X | X | X | ||||
Bonewright | C | C | ||||||||||||||||||||||||
Collector | C | X | X | X | X | X | X | X | X | X | X | |||||||||||||||
Darkshaper | C | C | X | X | X | X | X | X | X | X | X | X | X | |||||||||||||
Ferrous Emissary | X | X | C | C | C | |||||||||||||||||||||
Inventioneer | C | (X) | X | C | C | C | C | C | X | X | X | X | ||||||||||||||
Lingchi Warrior | C | X | X | X | X | X | X | X | X | X | X | |||||||||||||||
Living Weapon | C | C | C | C | C | C | C | C | C | C | C | C | C | C | C | C | C | C | X | C | C | |||||
Martial Armorist | C | (X) | ||||||||||||||||||||||||
Soaring Blade | C | C | C | C | C | C | C | C | C | C | C | C | C | C | C | C | C | X | X | |||||||
Spirit Blade | C | (X) | X | C | C | C | C | C | X | X | X | |||||||||||||||
Symbiotic Knight | C | X | X | X | X | X | X | |||||||||||||||||||
Vajrahasta | C | (X) | X | X | X | X | X | X | X | X | X | |||||||||||||||
Void Wielder | X | X | C | C | C | C | ||||||||||||||||||||
Warden | C | X | C | X | X | X | ||||||||||||||||||||
Warleader | C | X | X | X | X | X | ||||||||||||||||||||
Whitesmith | X | X | X | X | X | X | X | X | X | X |
-
Archetype | Class Skills | Weapon & Armor | Magic Talents | Weave Energy | Evasion | Combat Feats | Favored Element | Dodge Bonus | Elemental Defense | Elemental Movement | Improved Evasion | Energy Body | ||||||||||
2 | 6 | 10 | 14 | 18 | 3 | 9 | 15 | 5 | 11 | 17 | 7 | 13 | 19 | |||||||||
Admixture Savant | C | X | X | X | X | X | X | (X) | (X) | (X) | X | X | X | |||||||||
Arcanophage | X | X | X | X | X | X | X | X | X | X | X | X | X | X | ||||||||
Arcanopulser | C | (X) | X | X | X | X | X | X | X | X | X | X | X | X | X | X | ||||||
Earth Warrior | X | X | X | C | C | C | X | X | X | X | ||||||||||||
Electrokinetic | X | (X) | (X) | (X) | (X) | (X) | C | C | C | C | C | C | X | X | X | |||||||
Elemontalist | C | C | C | X | C | C | C | X | ||||||||||||||
Flame Warrior | X | X | X | X | X | X | X | X | X | X | ||||||||||||
Geomancer | X | X | X | X | ||||||||||||||||||
Martial Elementalist | C | X | X | X | X | X | ||||||||||||||||
Metal Warrior | X | X | X | X | X | X | X | X | X | X | ||||||||||||
Natural Warrior | X | X | X | X | X | X | X | X | X | X | ||||||||||||
Soul Adept | C | X | X | X | X | X | X | X | X | X | X | X | ||||||||||
Tenebrous Stalker | X | (X) | (X) | (X) | (X) | (X) | X | X | X | X | X | X | X | X | X | X | ||||||
Twinsoul Elementalist | X | X | (X) | (X) | (X) | |||||||||||||||||
Water Warrior | X | X | X | X | X | X | X | X | X | X | ||||||||||||
Wind Warrior | X | X | X | X | X | X | X | X | X | X |
-