Danbooru changelog discussion thread

Posted under Bugs & Features

sabisabi said:

girl why are the headers now right aligned on mobile........i am going to drop a bara nuke in the danbooru server room

The menus for me on mobile are left aligned. This too is yuri.

Knowledge_Seeker said:

One of my scripts, specifically one I used to avoid being notified of forum postings, broke today somehow. No clue how or what the problem is, but I figured it's probably related to here.

Notified how?

nonamethanks said:

Notified how?

I assume 9fd2b6d broke some people's CSS to disable the "Forum" element in the header from being italicized.

The following should work (Works On My Machine):

#nav-forum.font-italic {
    font-style: normal;
}

ANON_TOKYO said:

I assume 9fd2b6d broke some people's CSS to disable the "Forum" element in the header from being italicized.

The following should work (Works On My Machine):

#nav-forum.font-italic {
    font-style: normal;
}

Yep, that's exactly what I meant lol. Anyway, this script here fixed the issue. Thank you.

Blacklists work, but now they're more of a sticky-toggle(remembers if a tag was disabled for every new page/tab/window opened or navigated to until you personally turn it back on) than the auto-reenable it had been(where it would immediately re-hide anything on the list on the next page/tab/window). I would prefer that it auto-reenable itself like before... if it was intentional to be changed this way, I'd really like for it to be a preference in settings so we could choose how it behaves.

I thought it might have been. I get why they may want it that way, but I've been relying on that behavior for years. Unless it would take a major overhaul, if possible I'd really like to see it eventually be a Settings preference, something along the lines of "Remember Blacklist Toggle".

Bulleted lists inside an [expand] tag seem to have broken. A bullet character is not displayed, sub-items are not indented, and an extraneous blank line is inserted after an item's last sub-item.

This is in the latest version of Firefox, 139.0.4

Outside an expand block:

  • 1
  • 2
    • 2a
    • 2b
  • 3
Inside an expand block
  • 1
  • 2
    • 2a
    • 2b
  • 3

Um, so I have a question about DMCA. Artists no longer can request a ban on all their works on the site and have to send DMCA requests about each post individually or did I misunderstand something? It's just that many artists still have the "Banned" label on their wikis at the moment and blue users can not search their tags (example: ikemeru19. Wiki is working, searching isn't working)). I'm pretty sure that Ikemeru19 contacted Danbooru due to NovelAI incident and asked to take down all of their works, yet new artwork was just uploaded today.

Searching for ikemeru19 leads to "This page has been removed because of a takedown request.", yet new post is visible in wiki and if you add another tag ikemeru19 original

Updated by Gardares

nonamethanks said:

That's been the case for the past 3 years or so. All bans must go through the DMCA form, as required by US law.

Yeah, but... DMCA notice says "Please list each individual post, not a tag search or profile page.", yet it seems that artist tag searches are taken down too or at least partially since they are working with two tag searches like ikemeru19 original. I'm also asking because I got notified about this post by artist RSS tag the first time after takedown of all posts (aka after post #5729374) and I can see by modifying the link to the latest available post with "?q=ikemeru19" that there was other post uploaded 2 months ago (post #9192404) by the same artist that was taken down before RSS noticed it.

The legacy ban system is handled by two components: a ban flag on the artist tag called is_banned and the banned artist tag. Both are handled first class by the site.

Banning an artist sets is_banned to true on the artist tag and also has it imply banned artist. The banned artist tag automatically applies status:banned to a post, while the is_banned flag on the artist tag handles blotting out the page so that you can't find posts that should've been banned but weren't (aka. if the intent was for all posts to be banned, then might as well just not show the page to begin with). That's how you get accidents where someone applies banned artist, paid reward or another "special tag" to a post where it shouldn't be and that post gets autobanned.

Banned artist is deprecated so it can't be added to new posts and therefore no post is automatically banned anymore. However, is_banned was not removed from the code at the same time, so all it means is you can't view their posts directly. For now it's still just another grandfathered state.

Updated by WRS

1 44 45 46 47 48