Danbooru

Danbooru 2 Issues Topic

Posted under General

This topic has been locked.

Hen-Ecch said:

Does the url "source" search operator not work property? Even the example in the cheat sheet doesn't seem to work. As in: source:http://pixiv.net as an example

Why do you think it doesn’t work properly? source:http://pixiv.net returns two posts. Most have www. in there, so source:http://www.pixiv.net returns more. Nowadays it’s mostly https, so there’s source:https://www.pixiv.net too.

What are you trying to search for, what did you expect to happen and what happened instead?

kittey said:

Why do you think it doesn’t work properly? source:http://pixiv.net returns two posts. Most have www. in there, so source:http://www.pixiv.net returns more. Nowadays it’s mostly https, so there’s source:https://www.pixiv.net too.

What are you trying to search for, what did you expect to happen and what happened instead?

I see. I was actually wanting to exclude Twitter posts from a search I was doing. I wasn't sure what variations would work. Looks like it's more flexible than I assumed

How do I show the FontAwesome symbols again? I'm still seeing blocks, but when the custom CSS is not immediately loaded, the said symbols are visible. (Again, using Chrome, also seen on Chrome on mobile and Firefox.)

Using the bookmarklet on the full sized image page from NicoNicoSeiga places the post link in the source field instead of the raw image url. The bookmarklet still grabs the correct image formatting though, so it is somewhat similar to a related issue before from Pixiv as pointed out by Unbreakable.

inkuJerr said:

Using the bookmarklet on the full sized image page from NicoNicoSeiga places the post link in the source field instead of the raw image url. The bookmarklet still grabs the correct image formatting though, so it is somewhat similar to a related issue before from Pixiv as pointed out by Unbreakable.

That's what it is supposed to do. Those full-size image links only last for about a minute before timing-out and 404'ing, which makes them worthless, which is why the post URL is put in the source field instead.

We haven't talked about the new recommended tags system for a while.
I saw that it's not working at all off of mistakes, like "girl" doesn't give "1girl" as a suggestion. That was something that i liked about the old system, as well as that you could write a word from later in the title (Ex: yeager) and you'd get popular results.
It also doesn't give suggestions if you end up using - instead of _.

keonas said:

We haven't talked about the new recommended tags system for a while.
I saw that it's not working at all off of mistakes, like "girl" doesn't give "1girl" as a suggestion. That was something that i liked about the old system, as well as that you could write a word from later in the title (Ex: yeager) and you'd get popular results.
It also doesn't give suggestions if you end up using - instead of _.

The first one is intentional as explained in issue #3898

One thing I've noticed with tag autocomplete is that if I swap the name order of a tag (for example, "iwana_kate" instead of kate_iwana or "suzuko_mimori" instead of mimori_suzuko), the current system doesn't suggest the correct tag as often as the old system did. In cases where it does, it seems to take a while to calculate before showing the suggestion.

Another minor irritation is that the new "abbreviations as shortcuts" feature doesn't extend to suggesting Love Live! School Idol Festival when I type "llsif." So to tag it, I have to type "love" and press the down arrow several times.