pluggedbus said: No matter where I look, it is no longer there.
I think the last time we looked into it, it was not available to normal accounts, no. I don't know if this is on purpose or not.
Posted under General
pluggedbus said:
So, you're saying that the use of blacklisting tags on normal accounts just magically vanished without administration noticing?
There's no need to be hostile. He's a moderator. It's possible that albert (the site owner) chose to remove it and didn't notify anyone.
Last time something like this came up, albert said blacklists don't work for normal accounts, since they're kinda hard on searches apparently. It was in here somewhere: forum #2593.
From what you're saying they're working for you though, just you can't add or remove any since the option was taken out of the settings? Is that right?
Well anyway, I guess it's up to albert to answer this question.
Normal accounts are now served cached pages, which is incompatible with server-side blacklisting.
Server-side blacklisting is not Danbooru's friend. If you have 10 blacklisted tags, that means Danbooru is searching on 10 tags every time you look at a page. And tag searches are one of the most database-intensive parts of the site.
That's not stopping anyone from writing a Greasemonkey script to hide their own set of blacklisted tags. It should be trivial to pull the tags from each image and hide it if it matches some search criteria. The downside being you could potentially end up with pages with no visible posts.
albert said:
That's not stopping anyone from writing a Greasemonkey script to hide their own set of blacklisted tags. It should be trivial to pull the tags from each image and hide it if it matches some search criteria. The downside being you could potentially end up with pages with no visible posts.
i don't see the problem here,
If you blacklist 'foo' with greasemonkey and all the results have foo as a tag, you won't see anything.
If you blacklist with danbooru's feature the tag 'foo' and all the results have foo as a tag, you won't see anything.
Also, you're right; blacklisting should be done client-side and not server-side.
I don't know how to use greasemonkey's script, but i believe it would only need a regex to match
<img alt="tags1 foo tags2"> and simply replace the <img> tag with the alt textual description.
Maybe someone from here is able to do this? Or maybe someone has a better idea; whatever the case, server-side blacklisting is not a good thing.
:-)
The downside being you could potentially end up with pages with no visible posts.
Isn't that what server-side blacklisting does anyway? I mean, if I search for loli, having loli blocked, I get almost 400 pages of nothing. And if I search something with a bunch of loli images, I'll get like 4 images per page and a bunch of empty.
The only problem I can see with Greasemonkey is that (from what I've used of it) it first loads the whole page and THEN runs the script, so you still see all the images, and then they disappear, making it annoying to browse. Sounds better than not having blacklisting at all though!
I used to have an Opera user script that hid the tags I had blacklisted on the old danbooru, similar to its own script, except it also counted what it hid and told you why the posts were hidden and let you unhide them according to each tag that was blacklisted.
I don't know how Greasemonkey works, but the Opera script could hide the posts as the HTML was loaded, before you even see them, and it doesn't load the thumbnails for the hidden posts either (unless and until you unhide them manually).
I should probably try to make it work again with the latest version of danbooru, I wasn't aware that blacklisting tags was so hard on the server and I'd be perfectly fine doing it in my browser instead. It would be easier to do if the CDATA in the HTML were placed before the actual posts, though.
Would the wiki be a good place to post such a script when it's done, for the other Opera users?
I never had a problem with the old blacklisting scheme where you got the odd blank page. I've cleared my blacklist some time ago anyway because
a) the blacklist was permament (there is no longer a button to show hidden images)
b) since I'm supposed to be moderating I thought it a good idea to be able to see what I was moderating
c) Been a long time since I've seen a yaoi flood.
wanchan said: b) since I'm supposed to be moderating I thought it a good idea to be able to see what I was moderating
I'm under the impression the blacklist does not apply to the images in the moderation queue. Is this wrong? I guess I'd need to keep an eye out and see if tags I know I have blacklisted are showing up. I swore I'd seen some I know I have blacklisted though. Besides, I approve who knows how many dozens or hundreds of images a week so I'm busy enough as is... and unlikely to approve anything with tags on my blacklist anyway, because they're usually crappy images.
Well, blacklisted tags are no longer under my settings, but to be honest, everything I had blacklisted I couldn't view anyway. Is there really anything that offensive to people among the worksafe images? Of course, not all of the worksafe images are actually worksafe.. (basically it depends on the uploader and viewers to tag the image as explicit or not.)