I'd like to inquire as to why standard accounts are limited to two tags when searching and if this can at all be changed? I find it rather inconvenient when I'm searching for images prior to uploading -- IE: for dupes. -- and I find it more inconvenient when I'm searching for images to view/saving.
Oh, sorry for double post; and a follow up suggestion / question: would it be possible to hide the deleted posts from the search results? It'd help reduce the amount of clicks for pagination, and it'd also probably help reduce a bit of transfer between user and server(s).
Per the last point, I think albert's said it's actually less taxing on the servers to either 1) show the deleted placeholder or 2) remove deleted thumbnails but don't move everything up to fill the holes, than to do what you're saying (that is, less taxing than to go ahead and fill the holes in, reducing the total number of results by the # of deleted).
You'd have to ask someone knowledgeable about the technical side why. I also don't know if maybe something in the code has changed since I heard this, which was quite some time ago.
Doesn't make too much sense for me, too; and I'm a freelance / professional php developer >_> I don't see how it'd be more taxing on the server by simply adding an additional "and" clause to the query, that says something along the lines of "and deleted=0" or something like that... But I guess I've never coded distributed delivery platform like danbooru to comment on that one... Orz.
Is the tag limitation also due to the same reason?
I think this topic should serve as the answer you're looking for in reference to multiple tags.
Still, it's not all bad. Gives both you and myself another good reason to keep up the contributing to get a privileged account I suppose, and that's always a good attitude to encourage.
I'm fairly sure the limit is 6 tags now, and it applies to everyone. It also only applies 6 related or excluded tags (the most expensive to query). You can use as many metatags as you want.
The main reason the limit was in place was to make page caching simpler. Once you get into the exponential blowup of allowing 3 or more tags, caching just isn't feasible anymore.
For finding duplicate pics, the most efficient way is http://haruhidoujins.yi.org/db-search.php instead of hoping that the pic is tagged the way you think it is tagged.
piespy said: For finding duplicate pics, the most efficient way is http://haruhidoujins.yi.org/db-search.php instead of hoping that the pic is tagged the way you think it is tagged.
On that page:
Maximum image dimensions: 2500x2500
Unfortunately for me, some times images I upload gets tagged with "absurdres" tag... I'll let you figure out why it doesn't work ;)
Unfortunately for me, some times images I upload gets tagged with "absurdres" tag... I'll let you figure out why it doesn't work ;)
Well, a thumbnail is fine too. Faster to upload as well. My server has limited memory resources and I don't want to crash it by trying to process too large images. But everything is scaled down to 128x128 for matching anyway, so even if you scale your image down that much it'll still give the exact same match.
jxh2154 said: That restriction is new to me. It runs on moe.imouto too, where 2500 is a "slightly small" image. Is it just a danboo thing?
It's a "piespy's image search sucks" kind of thing. Danbooru has no limit (that I know of). And the queries that Danbooru and Moe.imouto do with the "Similar" links query the image thumbnail only, not the full size image. That never gets larger than 150x150 anyway.
piespy said: It's a "piespy's image search sucks" kind of thing. Danbooru has no limit (that I know of). And the queries that Danbooru and Moe.imouto do with the "Similar" links query the image thumbnail only, not the full size image. That never gets larger than 150x150 anyway.
Ah, I knew there was no res limit on danbooru, but I thought he was saying that your search wouldnt take danboo/moe images over that size. I see what you mean though.