Danbooru

Danbooru 2 Issues Topic

Posted under General

This topic has been locked.

BrokenEagle98 said:

The only recent change to the newpool metatag was a change of order of when it gets applied due to its case-sensitivity (issue #3341), but which shouldn't be causing the issue you've described as it only changed the order and nothing else. I'm somewhat suspicious though that it might be related to the use of Unicode characters, as when I tested the newpool metatag as part of of the above fix I used all Roman uppercase characters which worked just fine. I must admit though that I only tested it on an existing post and not an upload, so it could potentially also be that as well...?

Thanks to help from evazion on Discord, the problem was located and I submitted a fix with issue #3347. It's already been merged but not yet deployed to the site. I'll post again in this thread once it is to let everyone know that it's safe to use the newpool metatag again.

Just had it happen to me. The newest message listed is 12 days old, and while I don't recall reading it before, it lacked any indication it was unread. Also, the From and Subject info show as "[filtered]" on all messages.

Moonspeaker said:

Just had it happen to me. The newest message listed is 12 days old, and while I don't recall reading it before, it lacked any indication it was unread. Also, the From and Subject info show as "[filtered]" on all messages.

@Moonspeaker

Check out your Dmail filter, under Advanced settings. When I tested that feature out, particularly by adding a username to the list of filtered items, all hits would get [filtered] added to the messages like you indicated in both the From and Subject fields.

BrokenEagle98 said:

@Moonspeaker

Check out your Dmail filter, under Advanced settings. When I tested that feature out, particularly by adding a username to the list of filtered items, all hits would get [filtered] added to the messages like you indicated in both the From and Subject fields.

I didn't think I had any filters turned on, but weirdly, the text of the next-to-most-recent reply I thought I'd sent was in the filter box, in its entirety. I know I was using a cell phone to respond at the time, having no choice, but I have no idea what keys I hit to put the entire text of the reply into my Dmail filters.

Deleting that text appears to resolve the "[filtered]" problem, at least, so thanks for pointing me in the right direction.

(FYI, I received no notice of this @ mention of my user name, but that appears to be another symptom of having that response text in my filters.)

@fossilnix

The fix for issue #3341 has been deployed, so the newpool metatag should be safe to use.

Moonspeaker said:

I didn't think I had any filters turned on, but weirdly, the text of the next-to-most-recent reply I thought I'd sent was in the filter box, in its entirety. I know I was using a cell phone to respond at the time, having no choice, but I have no idea what keys I hit to put the entire text of the reply into my Dmail filters.

There is a "Filter messages like these" link at the bottom of all Dmails, however it's a two step process as it brings you to a page that allows you to input all that you want to block, so IDK how it could have happened...?

No. Just occasionally when I try to view a post or go to the next page of search results it gives me Error 504 gateway time-out error saying it cant reach danbooru.donmai.us No one else experiencing this then?

Chiera said:

What's this error?
http://danbooru.donmai.us/uploads/1622429

An error occurred: error: SocketError - Failed to open TCP connection to www.pixiv.net:443 (getaddrinfo: Name or service not known)

The server couldn’t resolve www.pixiv.net. As the domain is correct, has worked before and works now, I guess it was a temporary name resolution error. Those happen from time to time on the Internet. Just try again later.

kittey said:

The server couldn’t resolve www.pixiv.net. As the domain is correct, has worked before and works now, I guess it was a temporary name resolution error. Those happen from time to time on the Internet. Just try again later.

It would've been a duplicate, anyway :e.
Was only wondering since it happened a lot some hours ago.

Thanks for the explanation.

Kikimaru said:

Is there any way to disable "swipe left to go back" on mobile?

Everything else is fine, but this feature breaks the mobile site for me (Android/Firefox)

@Kikimaru

This was recently fixed and deployed. The option to disable them is found under "Advanced" in user settings.