Topic: Tag alias: roid_gut -> musclegut

Posted under Tag Alias and Implication Suggestions

Donovan DMC

Former Staff

The tag has only been used 4 times in the last decade (most recently almost a year ago)
It should just be emptied and left alone

donovan_dmc said:
The tag has only been used 4 times in the last decade (most recently almost a year ago)
It should just be emptied and left alone

We make aliases for less than than like common misspelling, I don't see anything that makes this alias incorrect.

Donovan DMC

Former Staff

bleakdragoon said:
We make aliases for less than than like common misspelling, I don't see anything that makes this alias incorrect.

It isn't incorrect, it's unneeded
Aliases are not free, they take processing time and clog up wiki pages

If a tag is not used more then a few times in a decade there is no reason to alias it, especially when the term isn't common

donovan_dmc said:
It isn't incorrect, it's unneeded
Aliases are not free, they take processing time and clog up wiki pages

If a tag is not used more then a few times in a decade there is no reason to alias it, especially when the term isn't common

Wha? New usage of an aliased tag are automatically and irrevocably transformed into the alias,

If it was remotely a real concern, why we accept alias of artist name? I see those accepted by the dozen each month.

Case in point:

  • That alias was accepted for tag with 4 posts (spawning from 3 days to 3 years)
  • That alias (that has a janitor approval) is for 0 posts
  • That alias is for an artist with exactly 3 posts under the old name
  • This alias was accepted for tag with 9 posts

[edit]
It kind of bothered me so I dug it out a bit.

Algorithmic Complexity, Naive Implementation

I don't know how it his implemented but let's say it the naive implementation. A 2 steps Looking for aliases, then looking for posts with the list of aliases.

The code would look something like this:

SELECT DISTINCT posts.*
FROM TablePosts posts
JOIN TablePostsToTags postsToTags ON posts.id = postsToTags.post_id
JOIN TableTags tags ON tags.id = postsToTags.tag_id
WHERE tags.name IN (
    SELECT aliases.name
    FROM TableTagAliases aliases
    JOIN TableAliasesToTags aliasesToTags ON aliases.id = aliasesToTags.aliases_id
    JOIN TableTags t2 ON aliasesToTags.tag_id = t2.id
    WHERE t2.name = 'roid_gut'
);

Since you look at n-to-n relationship in 2 table, you get and algorithm complexity of O(n) * O(n) = O(n²)

So you'd be right BUT

The first column being indexed means we really have O(log n) * O(n) = O(n log n), which is rarely a big deal.

But I'm guessing the staff knows what they are doing, so they probably leveraged their database's power and did an optimized request.

The code could look like this:

Algorithmic Complexity, Optimized Implementation
SELECT DISTINCT posts.*
FROM TablePosts posts
JOIN TablePostsToTags pt ON posts.id = pt.post_id
JOIN TableTags t ON t.id = pt.tag_id
LEFT JOIN TableAliasesToTags att ON att.tag_id = t.id
LEFT JOIN TableTagAliases a ON a.id = att.aliases_id
WHERE t.name = 'roid_gut' OR a.name = 'roid_gut';

With the indexes we are looking at a
O(log n) + O(n) = O(n + log n), which simplify to O(n).

This is a linear search, the fastest kind of search

TLDR: That means that aliases are basically free.

Updated

I'm mostly saying no because the actual uses of this tag are not this site's definition of musclegut:

if a character has visible abs then they are not a musclegut.

post #4088681 post #5062322 post #5275159

Real roid guts[aka Palumboism or bubble gut] are also not this site's definition of musclegut. They refer to different things.

The problem arises in the fact that "musclegut" is a term that IRL can refer to palumboism. There's a pretty big difference between palumboism [a round gut with visible abs] and "musclechub" [associated with the "powerlifter build" or "bear"/"dad bod" body types, which is the definition e621 uses].

I think theoretically roid_gut can be useful to differentiate between the two, but it might need a different name. Someone may like seeing fat bellies on muscular bodies and others may prefer the defined abs of palumboism, and it'd be useful to blacklist without hiding all posts tagged with abs; a musclegut character and a leaner, muscular character could be in the same image and it would be blacklisted under musclegut abs.
post #5965690

The problem is people tag musclegut regardless of if abs are there or not. In that sense roid_gut -> musclegut is sensible.

The other solution is to clean up those tags.

bleakdragoon said:
The problem is people tag musclegut regardless of if abs are there or not. In that sense roid_gut -> musclegut is sensible.

The other solution is to clean up those tags.

It's a reasonable solution to clean it up. It's not an impossible task.
post #5316860 post #5337100 post #5258085
Posts like these aren't musclegut at all. And posts that are musclegut vs. posts that are just flat abs bellies are pretty easy to tell apart.
I'm also putting a set together for images that depict palumboism [roid_gut]. set #81653 There's quite a few that I've found out of only a few hundred posts, and growing page-by-page, so there's definitely precedent for the existence of a tag for palumboism.

Original page: https://e621.net/forum_topics/60850