Aliasing avas → alternate_version_available
Link to alias

Reason:

Seeing as we have bvas -> better_version_at_source I figure we should do this one too. AVAS being "Alternate Version At Source," though we use available instead.

+1 I've found myself wishing for this abbreviation a few times before.

In case anybody is wondering, ava is a character name, thus unavailable as an alias.

I'm digging the idea, but how about altva instead?

Why is the tag alternate_version_available instead of alternate_version_at_source to match with similar tags? Each tag is literally the exact same character length, so that shouldn't be an issue.

Main tag should be aliased from

alternate_version_available -> alternate_version_at_source

It would match with similar tags and then we could actually use "avas" as an abbreviation.

Because alternate versions often have different sources, left in the description or comments.

altver

leomole said:
Because alternate versions often have different sources, left in the description or comments.

Great way of sidestepping around the issue...the same could be said for better/smaller/larger versions...I could totally leave a comment or description pointing to one of those and yet their tags still end with "at_source". So my suggestion still stands unless you have a better one.

Also...you're basically contradicting yourself by +1ing an abbreviation that MEANS alternate_version_at_source then arguing that the actual tag shouldn't be alternate_version_at_source. The abbreviation should coincide with the actual tag.

Dyrone said:
the same could be said for better/smaller/larger versions

bvas is supposed to be a temporary tag. A better version of the post is placed in the source field and the post eventually gets replaced. That's why it's *_version_at_source.

alternate_version_available is a permanent tag. Different versions of the post are left in the description usually. Sometimes it's put in the source field but often there are too many alternate versions to fit there. That's why it's *_version_available.

Even if the alternate version does fit in the source it's still "available." That's why I support aliasing avas to alternate_version_available.

+1 altver, too. Or alt_ver.

leomole said:
bvas is supposed to be a temporary tag. A better version of the post is placed in the source field and the post eventually gets replaced. That's why it's *_version_at_source.

alternate_version_available is a permanent tag. Different versions of the post are left in the description usually. Sometimes it's put in the source field but often there are too many alternate versions to fit there. That's why it's *_version_available.

Even if the alternate version does fit in the source it's still "available." That's why I support aliasing avas to alternate_version_available.

+1 altver, too. Or alt_ver.

Actually, alternate version available should only be a temporary thing, to let people know there's another image at the source that can be uploaded, but unlike bvas will not replace the current one.

Mostly correct, alternate_version_available is usually a temporary tag as well but sometimes it's permanent when there are more than 5 versions of a post, see https://e621.net/wiki/show/uploading_guidelines#good.

Furrin_Gok said:
Actually, alternate version available should only be a temporary thing, to let people know there's another image at the source that can be uploaded, but unlike bvas will not replace the current one.

Exactly. Both better/alternate should be there to notify for someone to upload the version onto the site.

There are some minor exceptions to this rule which are content that cannot be uploaded onto site thanks to technical or guideline limitations. I have come around couple videos which became well over 100 MB (still managed to downscale and compress whole DVD to fit that, is still largest file on this website), there's one 8K image I believe which resolution got over 10 000 pixel limit, there are couple artists who love to make up to 30 versions of single image, (E: Leomon partially ninjad above) there's even case where artist posted lineart version of image, but colored version was made by DNP artist, etc.

So there are insane amount of edge cases which pretty much demand the tag to stay in place, but goal still is to have both tag count as close to zero as possible.

+1 for altver

leomole said:
+1 for altver

I hate this abbreviation. What's stopping an "altver" from existing ON THIS SITE? It hints not at all to the possibility that the alternate version exists on an outside page. Same with alternate_version_available...who's to say that alternate version isn't simply somewhere on the site? At least alternate_version_at_source explicitly points a user to an outside link.

Dyrone said:
I hate this abbreviation. What's stopping an "altver" from existing ON THIS SITE? It hints not at all to the possibility that the alternate version exists on an outside page. Same with alternate_version_available...who's to say that alternate version isn't simply somewhere on the site? At least alternate_version_at_source explicitly points a user to an outside link.

Because alternate versions are (or should be) linked with either pooling or parent/child relationships. Then we have inpool:true and isparent:true for searching. Wiki states that the tag should be removed if all everything is on site.

Was thinking possibility that there is alternate versions which aren't linked in source, including description and comments or in 404 source, but I guess these are pretty uncommon. I wouldn't be opposed to aliasing to "at source" instead unless there's good reason I cannot think of.

bumping because I need consensus before this happens.

My vote's to "at source" -- better to match up with the other tags, especially as they seem to have roughly the same use, even if the 'list of exceptions' is a slightly different shape, so to speak.

Should use alternate_version_at_source <- A avas. That encourages the tagger to source better. Not being able to link to every alternative version due to the five source limit is a separate issue. The tagger should at least ensure that the site(s) hosting all those versions is sourced, or source in the description, possibly with instructions, if it's necessary.

I still support alternate_version_available over alternate_version_at_source but in the interest of just getting it done I'm going to vote for avas / altver -> alternate_version_at_source as well.

alternate_version_at_source is live now.

Full list of aliases and possible aliases here.

Every tag with *available was aliased without issue. I hesitated to alias those without available, since those could easily be confused with edit. Placeholder aliases have been made until further discussion.

I'm working on changing alternate_version_available to alternate_version_at_source wherever it's linked on the wiki. Will update with a full list of changes, in case we ever decide to go back to alternate_version_available.

Wiki changes:

• better_version_at_source
• copypasted alternate_version_available onto alternate_version_at_source.