Topic: Thought's on a tag for unfixable better_version_at_source posts

Posted under Tag/Wiki Projects and Questions

For the approximately two and a half months I've been here, replacing posts tagged with better_version_at_source, or bvas for short, I've encountered a few posts here and there, which coulnd't be replaced for various reasons such as original image at source being larger than 15000 by 15000 pixels, or 100Mb's (site limit in case some doesn't know).

It has come to the point though, that there's quiet the amount of them now, and I, and probably a few other, will have a hard time keeping up with what and what isn't fixable.

Would just like to know others thoughts of a tag, which can be used on bvas posts that can't be fixed, such as Unfixable_better_version_at_source, or something more compact/smaller.

Updated

Nicklo6649 said:
For the approximately two and a half months I've been here, replacing posts tagged with better_version_at_source, or bvas for short, I've encountered a few posts here and there, which coulnd't be replaced for various reasons such as original image at source being larger than 15000 by 15000 pixels, or 100Mb's (site limit in case some doesn't know).

It has come to the point though, that there's quiet the amount of them now, and I, and probably a few other, will have a hard time keeping up with what and what isn't fixable.

Would just like to know others thoughts of a tag, which can be used on bvas posts that can't be fixed, such as Unfixable_better_version_at_source, or something more compact/smaller.

Like ubvats?

Updated by anonymous

Stiban said:
Like ubvats?

That would essentially be the shortened version of it, like bvas/bvats is short for better version of source. Problem is, that wouldn't be the one popping up on posts if it were to be used, but rather the full version of it, e.g unfixable_better_version_at_source, which is a pretty long tag, and could probably use some redo to be made smaller. I just don't know what else it could potentially be.

Edit: I also just noticed that there's a dedicated forum thread already, and have moved it over there now. link

Updated by anonymous

Nicklo6649 said:
That would essentially be the shortened version of it, like bvas/bvats is short for better version of source. Problem is, that wouldn't be the one popping up on posts if it were to be used, but rather the full version of it, e.g unfixable_better_version_at_source, which is a pretty long tag, and could probably use some redo to be made smaller. I just don't know what else it could potentially be.

Edit: I also just noticed that there's a dedicated forum thread already, and have moved it over there now. link

Maybe e6_reduced, e6_limit, max_limit, max_size, or e6_size? Something simple that conveys generally what it means, wouldn't be used in circumstances outside of this, and is short so you can filter images with the tag out quickly and easily. The wiki page would say more on exactly what it means, something like "This tag is only applicable when the size of the source media is larger than the maximum e6 can handle, either in dimensions (15000x15000 pixels) or size (100 mb) so a smaller version is archived here on e6."

Could make it so that it infers better_version_at_source, as well unless you just want one tag to replace BVAS so you don't have to filter out images with it and can, instead, just search for BVAS and update/tag appropriately.

Just my two cents, anyway.

Updated by anonymous

AnotherDay said:
Maybe e6_reduced, e6_limit, max_limit, max_size, or e6_size? Something simple that conveys generally what it means, wouldn't be used in circumstances outside of this, and is short so you can filter images with the tag out quickly and easily. The wiki page would say more on exactly what it means, something like "This tag is only applicable when the size of the source media is larger than the maximum e6 can handle, either in dimensions (15000x15000 pixels) or size (100 mb) so a smaller version is archived here on e6."

There's a ton of other reasons for the lower quality not being able to be replaced, such as artist only wanting preview versions uploaded here (the artist Marblesoda is a good example here) so the only one being suitable would probably be e6_reduced, though it's basically the same as bvas, so that wouldn't really be a good one.

AnotherDay said:

Could make it so that it infers better_version_at_source, as well unless you just want one tag to replace BVAS so you don't have to filter out images with it and can, instead, just search for BVAS and update/tag appropriately.

Just my two cents, anyway.

My idea was it to completely replace the bvas tag on those posts which can't be fixed, to make precise searching easier. And I appreciate those two cents.

Updated by anonymous

Nicklo6649 said:
My idea was it to completely replace the bvas tag on those posts which can't be fixed, to make precise searching easier. And I appreciate those two cents.

BVAS is self explaining tag, so if there is post that has better version at the source, it should be tagged with it, were it possible to upload the content here or not.

If you hit the tag limit on searching with having the new tag as secondary tag to BVAS, you can use your blacklist for help to exclude those posts from view and toggle them back on at the left side panel when searching.

Also if it is seperate tag included on top of BVAS, this would also make it possible to use with AVAS for example, posts which have alternate version available but which cannot be uploaded here for various reason, were it base limit or with something like post #874746 where colored version is done by artist who is DNP.

Updated by anonymous

Mairo said:
BVAS is self explaining tag, so if there is post that has better version at the source, it should be tagged with it, were it possible to upload the content here or not.

If you hit the tag limit on searching with having the new tag as secondary tag to BVAS, you can use your blacklist for help to exclude those posts from view and toggle them back on at the left side panel when searching.

Also if it is seperate tag included on top of BVAS, this would also make it possible to use with AVAS for example, posts which have alternate version available but which cannot be uploaded here for various reason, were it base limit or with something like post #874746 where colored version is done by artist who is DNP.

Good point, I can see what you mean. If possible, could I get to know your opinion on the tag itself, and wether you think it’s a good idea or not?

Thank you for the response.

Also, I know I made the link look small (in case you didn’t see it, but I actually posted this in the tag suggestion thread a little after, since I didn’t know we even had one before, which I do apologize about.

https://e621.net/forum/show/181201?page=16

There’s already some responses, and I’m thinking that we should copy these responses over, or link this now then?

Updated by anonymous

How about simply unobtainable_source to go alongside bvas since that seems to be the way the staff would want it, but if just one tag would be used unobtainable_source would still work just fine, I feel. If they wanted it with BVAS they could have it implicate BVAS.

That seems to say what it needs to say, at any rate and isn't so specific with sizes or the like since there's more reasons than I initially realized to not get a source.

Updated by anonymous

AnotherDay said:
How about simply unobtainable_source to go alongside bvas since that seems to be the way the staff would want it, but if just one tag would be used unobtainable_source would still work just fine, I feel. If they wanted it with BVAS they could have it implicate BVAS.

That seems to say what it needs to say, at any rate and isn't so specific with sizes or the like since there's more reasons than I initially realized to not get a source.

Problem is new users. It’s not descriptive enough, and make it sound like the source itself it somehow not obtainable. I know common sense should be able to figure it out, but not many users use that here unfortunately, so I believe it would have to be more clearer, like unobtainable_version_at_source, or best_version_allowed, which is mentioned on the thread I linked, and switched to.

Updated by anonymous

  • 1