Posted under Tag Alias and Implication Suggestions
The bulk update request #10185 is pending approval.
create alias mal0 (1393) -> malo (4073) # duplicate of alias #62136
create alias mal0_(species) (402) -> malo (4073)
Reason: Aliasing mal0 and mal0_(species) to malo. There's no zero, and three versions of this tag.
Edit: oh. uH... see topic #38395 too, i guess.
slocheze said:
The bulk update request #10185 is pending approval.create alias mal0 (1393) -> malo (4073) # duplicate of alias #62136
create alias mal0_(species) (402) -> malo (4073)Reason: Aliasing mal0 and mal0_(species) to malo. There's no zero, and three versions of this tag.
Edit: oh. uH... see topic #38395 too, i guess.
I'm gonna have to disagree with the first, just because Mal0 actually does refer to a very specific thing: MalO V.1.0.0. Hence, I think the Mal0 is a better fit than MalO.
Wait, didn't this all get aliased to the SCP number?
alphamule said:
Wait, didn't this all get aliased to the SCP number?
I was under the impression that mal0 was left and kept as a species tag so that OCs with designs riffing off of the original could be tagged without messing with the character's tag. but now it's classified as a character tag and there's a separate mal0_(species) tag.
bird-tm said:
I'm gonna have to disagree with the first, just because Mal0 actually does refer to a very specific thing: MalO V.1.0.0. Hence, I think the Mal0 is a better fit than MalO.
If you Ctrl+F on SCP-1471 - MalO ver1.0.0, you get no matches for "Mal0" but 5 for "MalO". Same goes with Capone by Fantem, which from what I can tell is the earliest fanwork about the original SCP, and uses "MalOs" as plural common noun.
dba_afish said:
I was under the impression that mal0 was left and kept as a species tag so that OCs with designs riffing off of the original could be tagged without messing with the character's tag. but now it's classified as a character tag and there's a separate mal0_(species) tag.
I don't know when the tags were made and when, but yeah. malo and mal0_(species) are species tags, and mal0 is a character tag. Looking right now, 6 of the 789 mal0 posts are tagged mal0 -scp-1471-a, and 7 of the 192 mal0_(species) lack scp-1471-a.
The bulk update request #10191 is pending approval.
create alias malo (4073) -> scp-1471-a (5715) # has blocking transitive relationships, cannot be applied through bur
change category malo_0.9 (58) -> character
create alias malo_1.0 (8) -> scp-1471-a (5715)
change category malo_1.1 (27) -> character
change category malo_1.1-b (5) -> character
create alias malo_v2.0 (7) -> malo_2.0 (7)
change category malo_2.0 (7) -> character
create alias scp-1471-a_(da.nilkaz) (550) -> da.nilkaz_(modeler) (962)
create alias scp-1471-a_(cumminham) (256) -> cumminham_(modeler) (676)
create alias scp-1471-a_(scrag) (203) -> scrag_(modeler) (252)
create alias scp-1471-a_(scrag) (203) -> scrag_(modeler) (252)
create alias scp-1471-a_(monolitwec) (40) -> monolitwec_(modeler) (58)
create alias scp-1471-a_(furromantic) (4) -> furromantic_(modeler) (1011)
create alias scp-1471-a_(pabu) (5) -> pabu_(modeler) (1) # has blocking transitive relationships, cannot be applied through bur
create alias malo(li) (42) -> scp-1471-a (5715)
create alias scp-1471-a-37 (38) -> scp-1471-a (5715)
create alias scp-1471-a-1088 (1) -> scp-1471-a (5715)
create alias scp-1471-a-52 (1) -> scp-1471-a (5715)
create alias scp-1471-a-135 (1) -> scp-1471-a (5715)
create alias scp-1471-a_(imacowolf) (3) -> scp-1471-a (5715)
create alias scp-1471-a-96 (19) -> scp-1471-a (5715) # has blocking transitive relationships, cannot be applied through bur
Reason: Honestly, SCP-1471-related tags needs a whole restructuring and cleanup.
'MalO' is the name of the program, which is designated '1471'. All instances of the entity are simply designated '1471-A'
Having the 1471-A character tag and a malo species tag doesn't make sense either. It should be one or the other.
BUR above does the following:
I know there's a few threads on this topic, but with this being the most recent.. figured this would be the best spot for this.
The bulk update request #10192 is pending approval.
remove implication scp-1471-a-96 (19) -> scp_foundation (8704)
Reason: BTR fixes for BUR #10191
I can't for the life of me figure out the BTRs for these two
create alias malo (3464) -> scp-1471-a (4717) # has blocking transitive relationships, cannot be applied through bur
create alias scp-1471-a_(pabu) (5) -> pabu_(modeler) (1) # has blocking transitive relationships, cannot be applied through bur
I did a metasearch and everything
dirtyderg said:
I can't for the life of me figure out the BTRs for these two
create alias malo (3464) -> scp-1471-a (4717) # has blocking transitive relationships, cannot be applied through bur
create alias scp-1471-a_(pabu) (5) -> pabu_(modeler) (1) # has blocking transitive relationships, cannot be applied through bur
I did a metasearch and everything
https://bitwolfy.com/projects/bur_debugger/
alias #62136
alias #67816
dirtyderg said:
The bulk update request #10192 is pending approval.remove implication scp-1471-a-96 (19) -> scp_foundation (8704)
Reason: BTR fixes for BUR #10191
I can't for the life of me figure out the BTRs for these two
create alias malo (3464) -> scp-1471-a (4717) # has blocking transitive relationships, cannot be applied through bur
create alias scp-1471-a_(pabu) (5) -> pabu_(modeler) (1) # has blocking transitive relationships, cannot be applied through bur
I did a metasearch and everything
snpthecat said:
Also if you're wondering what a Blocking Transitive Relationship (BTR) is, it is a BUR exclusive warning (when trying to alias through a BUR) that appears if the antecedent tag has any pending/active implications/aliases. A good tool to verify if you will encounter a BTR / find what is causing a BTR is MetaSearch
If you spot the word Active or Pending when you search the antecedent tag, you are guaranteed a BTR
snpthecat said:
Also if you're wondering what a Blocking Transitive Relationship (BTR) is, it is a BUR exclusive warning (when trying to alias through a BUR) that appears if the antecedent tag has any pending/active implications/aliases. A good tool to verify if you will encounter a BTR / find what is causing a BTR is MetaSearch
If you spot the word Active or Pending when you search the antecedent tag, you are guaranteed a BTR
I totally forgot that BTRs include pending requests, not just active ones ๐
Updated
"Malo" isn't unique and should be disambiguated.
Even the SCP's Malo isn't that clear as to which such a tag would refer to:
malo_0.9
malo_1.0
malo_1.1
malo_1.1-b
malo_2.0
malo_v2.0
To say nothing of all the various scp-1471* tags referring to the same creature.
dirtyderg said:
- Alias model character tags to modeler contributor tags.
Model character/species tags should be aliased to the character/species, so people that type in scp-1471 get the character/species rather than random unaffiliated modelers in the autocomplete list.
Updated
oh no i went to bed this thread popped off
dirtyderg said:
'MalO' is the name of the program, which is designated '1471'. All instances of the entity are simply designated '1471-A'
Having the 1471-A character tag and a malo species tag doesn't make sense either. It should be one or the other.
"SCP-1471" by LurkD, from the SCP Wiki. Source: https://scpwiki.com/scp-1471. Licensed under CC-BY-SA.
For โโโโโโโโโโโโ. Never settle for those awkward feelings of being alone ever again. MalO is an exciting and interactive experience that will keep you engaged and intrigued. The anxiety of social situations can be nerve-racking, but after just a few hours of MalO you will soon forget all about those painful emotions of disappointment. Be part of the new craze that is quickly becoming the next social substitute. Remember, the more you participate, the more MalO will engage you. Your experience is completely up to you. Absolutely NO ADS. Enjoy!
Looking at the app store description of SCP-1471, you're right. The syntax is ambiguous if "MalO" is the program or the entity. The tale Capone does use the plural "MalOs" like a species, but its told from the perspective of William, a civilian who doesn't know about the Foundation and SCP designations.
Take whisperfoot's SCP oc SAMI. She doesn't have the exposed skull of the regular SCP-1471-A, but she is a canine borne from a digital program like SCP-1471-A. Should that define the MalOs? A canine that is technically a digital creature/hallucination but doesn't always appear as one? Because if so, I found a spotted hyena MalO in post #1919014 and post #1919016.
dirtyderg said:
- Rework variant characters like malo 0.9 to character tags. This should be fine, they're separate characters inspired by 1471-A and the artist can choose to call them MalO if they want.
The malo tag with version numbers are original species (except for that MalO v2.0 tag, its for some small vtuber) treated as antecedent and descendant species of "malo 1.0". malo 0.9 (this one being a canine/caprine hybrid) and malo 1.1 are made by keadanger and have been used by a few other artists from the looks of it.
watsit said:
"Malo" isn't unique and should be disambiguated.
Oh damn, those aren't bony wolf waifus at all. The fact no-one's made malo_(disambigation) when this has been a clusterfuck for years is an anomaly in of itself.
If "SCP-1471-A" and "MalO" are synonymous, the argument that malo should be a species tag would extend to scp-1471-a being a species tag.
dirtyderg said:
- Alias model character tags to modeler contributor tags.
The modelers category popped up when I was away for a bit, so I'm not familiar enough with it to weigh one way or the other.
dirtyderg said:
- Alias away variants of 1471 that are just slight variations in design, age, size, etc. that don't warrant a separate character tag.
watsit said:
To say nothing of all the various scp-1471* tags referring to the same creature.
To be clear, the scp-1471-a-{#} are OCs. The SCP-939 tags are like that, because even in the original story, the individuals are given a numbered appendix, like SCP-939-101. (Note: not all SCPs follow the same appendices to their designation: some use numbers like "-1" (or start at "-2"), some use letters like "-A" (which can intrude upon the Jokes, which are "-J") or "-ฮฑ", some use words like -LYRE and LORD, or esoteric characters like "-โ" ("nabla"). That's not even to mention the nomenclative anomalies that can't referred by the SCP-#### standard.)
The real problem with the SCP-1471-A-# tags is that some have actual name names as well, like SCP-1471-A-37/Marsh (MarshTheMalO). Which gets aliased to whom: the number or the name?
I put it like this in our wiki on SCP-1471-A:
Due to the intangible perspective-based nature of SCP-1471-A, it is ambiguous if they are a singular pluripresent entity, or multiple instances created with each individual exposed to SCP-1471. As a product of this (and SCP-1471-A's popularity), there are several fan characters of people's own "MalOs", being regarded as a species.
With the SCP Foundation's loose canon nature and the ambiguous syntax from the original story, SCP-1471-A could be a character, or a species. It's left up to that the reader thinks, and that's a bitch.
But given the scp-939-{#} and scp-1471-a-{#} tags, I'm starting to lean towards recategorizing scp-1471-a as a species tag.
dba_afish said:
I was under the impression that mal0 was left and kept as a species tag so that OCs with designs riffing off of the original could be tagged without messing with the character's tag. but now it's classified as a character tag and there's a separate mal0_(species) tag.
I think malo was the originally intended target. mal0_(species) came around a while later (Personally, I'm for an alias to that). Previous discussion about SCP-1471 always went into the direction "First, deal with the implication to SCP-1471-A", because of the unnecessary bloat it caused. That implication got dealth with by aliasing scp-1471-a toscp-1471 , but something seems to have gone wrong. Was that because of the issues with contributer tags?
Also, there is skulldog_(species) . The wiki mentions malo, but I'm not convinced that the connection is intentional. The wiki of malo doesn't mention skulldogs in any way, so the similar design might just be a coincidence.
watsit said:
"Malo" isn't unique and should be disambiguated.Even the SCP's Malo isn't that clear as to which such a tag would refer to:
malo_0.9
malo_1.0
malo_1.1
malo_1.1-b
malo_2.0
malo_v2.0
I remember from previous discussions that even SCP fans aren't familiar with all these versions. Are we sure they are "canon" or are they just fan-made? Also, can we reliably tell them apart? If not they might be better suited as part of the wiki entry instead of being tags.
