Now that I've figured out what was going on I'm going to suggest switching the fetched header to Translated, TRANSLATED, or translated tags, it gets very very confusing if translated is the last tag on the post and there aren't any any tag translations.
However, basic members can't do wildcard searches at all because there were performance concerns. You'd need to be builder+ to do that. If you try to do a wildcard search as a basic member it will be interpreted as a regular search and not work like you want it to.
Doesn't seem this is included in help:users. Does this apply to tag searches as well? (As in on the Tags header section, not searching for posts)
Doesn't seem this is included in help:users. Does this apply to tag searches as well? (As in on the Tags header section, not searching for posts)
No it works for Tags. The "wildcards are limited to builder+" thing is only for artists, comments, dmails, forum posts, forum topics, notes, and wiki pages. Other things work the same for everybody.
Now that I've figured out what was going on I'm going to suggest switching the fetched header to Translated, TRANSLATED, or translated tags, it gets very very confusing if translated is the last tag on the post and there aren't any any tag translations.
I'm not entirely sure how the pixiv api handles deletions but if a post returns "該当作品は削除されたか、存在しない作品IDです。" could the translated tags spit out only bad_id? (post #1717485 triggered this if you need a test post.)
Are artist aliases not moving URLs again? e.g. bellend was aliased to gonzozeppeli but the entry for the latter is empty.
jxh must have forgotten to check the "Move aliased artists and wiki pages" checkbox when doing all the artist aliases. I moved that artist entry manually.
I'm having a problem with forum threads randomly being marked unread, sort of the opposite of the old problem where many got marked read before I'd seen them. This new issue actually makes it much harder to determine which threads I need to check than them being manually marked read.
Happening to anyone else or are my cookies borked again like when I couldn't view threads?
Edit: Tho in the meantime, "Mark All Read" seems to have gotten it to calm down. I'll try to remember to use that each time I catch up (...if I can stay caught up).
I'm having a problem with forum threads randomly being marked unread, sort of the opposite of the old problem where many got marked read before I'd seen them. This new issue actually makes it much harder to determine which threads I need to check than them being manually marked read.
Happening to anyone else or are my cookies borked again like when I couldn't view threads?
Edit: Tho in the meantime, "Mark All Read" seems to have gotten it to calm down. I'll try to remember to use that each time I catch up (...if I can stay caught up).
It's not just you, this has been happening intermittently since the change to topic unread states.
I don't know for sure but I suspect that it's just an unavoidable problem with storing this in cookies, which is why I've suggested not storing it in cookies: issue #2197
Aren't those stored in session variables rather then cookies? I thought session variables allow arbitrary amounts of data to be stored, since they are actually just plaintext files.