Edit | Leave a Comment | Favorite
More Like This: (Beta Temporary Feature)
User Comments:
goldoa commented at 2013-05-24 22:28:16 » #1327172
My apologies about that Daijin. I was not trying continue my "silly battle" when replying to Jerl, but rather to address his (or her) point about searchability (albeit in my own long-winded, rambling way).
While a "hard alias" is clearly unfeasible, is a normal one still possible? At the very least, I'd like for casual visitors to find the artist they're looking for. I'd already put in a request for one, but it hasn't been accepted yet.
0 Points
Flag
My apologies about that Daijin. I was not trying continue my "silly battle" when replying to Jerl, but rather to address his (or her) point about searchability (albeit in my own long-winded, rambling way).
While a "hard alias" is clearly unfeasible, is a normal one still possible? At the very least, I'd like for casual visitors to find the artist they're looking for. I'd already put in a request for one, but it hasn't been accepted yet.
0 Points
Flag
Jerl commented at 2013-05-24 23:02:11 » #1327181
There is no "normal alias".
There is only "hard" aliases, which are set in the aliases tab and which automatically change tags, and "soft" aliases, which aren't really aliases at all, but are rather a term referring to the act of changing one tag into another.
Soft aliases are not automatic. While we can use the mass tagger to change a lot of tags at once, this only happens once. If posts come in with danbooru's tags, they won't be changed again until someone sees them and fixes them, even if they were previously soft aliased. In other words, we or the site's users would be forced to make sure it keeps up to date. We can't trust the users to do this, and we have more productive things to do.
0 Points
Flag
There is no "normal alias".
There is only "hard" aliases, which are set in the aliases tab and which automatically change tags, and "soft" aliases, which aren't really aliases at all, but are rather a term referring to the act of changing one tag into another.
Soft aliases are not automatic. While we can use the mass tagger to change a lot of tags at once, this only happens once. If posts come in with danbooru's tags, they won't be changed again until someone sees them and fixes them, even if they were previously soft aliased. In other words, we or the site's users would be forced to make sure it keeps up to date. We can't trust the users to do this, and we have more productive things to do.
0 Points
Flag
goldoa commented at 2013-05-24 23:42:56 » #1327196
Really? On Danbooru, the system, as I understand it, allows aliased tags to be forwarded along to the "proper" tags, i.e. someone searching "hisasi" would still end up with all the results tagged as "hisashi_(nekoman)".
So, are you saying that because many of the tags are coming from an external source that this is not as easy here as it is there, since Danbooru doesn't import tags automatically from elsewhere?
P.S. Because I forgot to in my last post, I just wanted to clarify that the comments that I "spammed" on Hisasi posts were on pictures that I had uploaded minutes before and that I did not do so on any existing posts.
0 Points
Flag
Really? On Danbooru, the system, as I understand it, allows aliased tags to be forwarded along to the "proper" tags, i.e. someone searching "hisasi" would still end up with all the results tagged as "hisashi_(nekoman)".
So, are you saying that because many of the tags are coming from an external source that this is not as easy here as it is there, since Danbooru doesn't import tags automatically from elsewhere?
P.S. Because I forgot to in my last post, I just wanted to clarify that the comments that I "spammed" on Hisasi posts were on pictures that I had uploaded minutes before and that I did not do so on any existing posts.
0 Points
Flag
Jerl commented at 2013-05-25 00:19:23 » #1327215
Keep in mind that Danbooru and Gelbooru run completely systems, even coded in completely different languages. Danbooru is coded in Ruby on Rails; Gelbooru is coded in PHP. They don't use the same code base at all.
Danbooru only has one alias system, and Gelbooru has only one alias system. Both alias systems change incorrect tags, and redirect searches for them to the correct tag.
Danbooru can set up aliases, change, or break aliases however they want. They can decide one day that they want to use tag_a, and then the next day decide to switch to tag_b, and then finally on a third day decide to completely break the alias or change it to tag_c.
On Gelbooru, it is different. Approving aliases has the potential of causing the site to become unstable, or even force us to rebuild the entire tag index. It usually takes days to completely rebuild the tag index, and until it's rebuilt, searching doesn't work properly at all.
Because of this, we cannot approve aliases except in very extreme situations. Our assistant administrator was actually yelled at for starting to approve aliases after he got promoted, because it's so destructive to the site's operations.
Our effective inability has nothing to do with the fact that we import images from Danbooru. For the aliases that we have approved, it works exactly as expected. Searches for the incorrect tag are automatically redirected to the correct tag, and all posts, including those we import from Danbooru, have their tags changed to the correct tag as they come in. This all works fine.
The problem is that we can't approve any more aliases without a damn good reason. This tag isn't really worth potentially screwing up the entire site for a few days, so this isn't going to happen.
So, this means that we can't use aliases, and must rely on doing everything by hand.
Like I said, we only have the one alias system. "soft aliases" are not a system built into the site. They aren't an actual thing that exists in code at all; it's simply a term for changing all of tag_a into tag_b. In the beginning, this was done entirely by hand. Whether you were a user, gardener, or moderator, you had to actually load each post by hand, type in the tags, and click submit for every single image. We now have a mass tagger which enables us to do this with a push of a button, but pushing the button only makes it happen once. The button needs to be pressed every time new posts come in with the tag.
0 Points
Flag
Keep in mind that Danbooru and Gelbooru run completely systems, even coded in completely different languages. Danbooru is coded in Ruby on Rails; Gelbooru is coded in PHP. They don't use the same code base at all.
Danbooru only has one alias system, and Gelbooru has only one alias system. Both alias systems change incorrect tags, and redirect searches for them to the correct tag.
Danbooru can set up aliases, change, or break aliases however they want. They can decide one day that they want to use tag_a, and then the next day decide to switch to tag_b, and then finally on a third day decide to completely break the alias or change it to tag_c.
On Gelbooru, it is different. Approving aliases has the potential of causing the site to become unstable, or even force us to rebuild the entire tag index. It usually takes days to completely rebuild the tag index, and until it's rebuilt, searching doesn't work properly at all.
Because of this, we cannot approve aliases except in very extreme situations. Our assistant administrator was actually yelled at for starting to approve aliases after he got promoted, because it's so destructive to the site's operations.
Our effective inability has nothing to do with the fact that we import images from Danbooru. For the aliases that we have approved, it works exactly as expected. Searches for the incorrect tag are automatically redirected to the correct tag, and all posts, including those we import from Danbooru, have their tags changed to the correct tag as they come in. This all works fine.
The problem is that we can't approve any more aliases without a damn good reason. This tag isn't really worth potentially screwing up the entire site for a few days, so this isn't going to happen.
So, this means that we can't use aliases, and must rely on doing everything by hand.
Like I said, we only have the one alias system. "soft aliases" are not a system built into the site. They aren't an actual thing that exists in code at all; it's simply a term for changing all of tag_a into tag_b. In the beginning, this was done entirely by hand. Whether you were a user, gardener, or moderator, you had to actually load each post by hand, type in the tags, and click submit for every single image. We now have a mass tagger which enables us to do this with a push of a button, but pushing the button only makes it happen once. The button needs to be pressed every time new posts come in with the tag.
0 Points
Flag
1 2