- Uploading new [[Flash]] files is no longer allowed.
- Added support for viewing old [[Flash]] posts using the Ruffle Flash emulator. This is experimental. Many Flash files aren't fully supported by Ruffle.
- You can now edit the flag reason after you flag a post.
- Discord: fixed the /count command not working sometimes because of search timeouts.
- Discord: fixed the /tagme command not working.
- Fixed a bug where if tag A implied tag B, and you tried to alias A to B, then it wouldn't remove the implication first.
- Fixed the Download link in the sidebar not respecting the "Disable tagged filenames" option.
These changes are only relevant to people running a personal Danbooru instance:
-
Made it easier to run a personal Danbooru instance. Just clone the Git repo and run
bin/danbooru
and it will automatically start a new Danbooru instance for you. See the Quickstart section in the README for more details. Note: this has known limitations and is still a work in progress. -
Changed the default database connection settings. You may have to update your config if you get database connection errors. See commit 189adc683 for details.
-
Removed support for the
~/.danbooru/secret_token
file and theSECRET_TOKEN
environment variable. You will have to update your config if you used the~/.danbooru/secret_token
file. See commit 1a8c70f5f for details. -
Disabled Redis by default. You will have to edit your config to re-enable Redis. See commit d59b0234a for details.
-
Custom CSS: Custom CSS no longer automatically adds
!important
to the end of your CSS rules. This means your custom CSS may no longer work because it doesn't override the site's CSS in some cases. If your custom CSS no longer works, you will need to manually add!important
to the end of your rules, or otherwise change your selectors to increase your CSS's specificity. See https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity. -
Notes: translators can control the stacking order of overlapping notes with e.g.
<div class="note-box-attributes level-5"></div>
. Valid levels are level-1 through level-5. -
Discord: Fixed Fumimi's /posts and /count commands being limited to 2 tags.
- Fixed
user_xxx
names being automatically added to the Other Names field of new Pixiv artists.
-
Changed how uploaded files are stored by default. If you're running your own Danbooru instance, and images are broken, you may have to move some files in the
public/data
folder or create some symlinks. This only affects users running their own Danbooru instance. See these commits for details:https://github.com/danbooru/danbooru/commit/a620a71b59e95ed5f6e6501bec97e4a4da31d546 https://github.com/danbooru/danbooru/commit/0f90ae0feda1aca6b1b8d3f65165d2e1f645812e https://github.com/danbooru/danbooru/commit/29d2e7fed2357fd57552472c13defee9f348a741
- Added max length limits for comments, forum posts, and dmails. The limits are max 15,000 characters for comments, max 200,000 characters for forum posts, and max 50,000 characters for dmails. These limits shouldn't affect most users.
- Fixed having to double tap related tags on iOS.
- Fixed Pawoo uploads saving the wrong source.
- Fixed a bug with Baraag.net that caused the batch bookmarklet to always pick the first picture in multi-image posts.
- Fixed the API key IP address whitelist not showing IP subnets.
- Hopefully fixed issue with Nijie uploads sometimes failing because of Danbooru getting logged out of Nijie.
- Fixed favgroup navbar not showing above post when browsing another user's favgroup.
- On the
/bans.json
endpoint, changed theexpires_at
field to `duration. - On the
/wiki_pages.json
endpoint, removed thecategory_name
field. You can use/wiki_pages.json?only=title,tag
instead if you need this.
Reworked rate limit system:
- Rate limits are now per-endpoint instead of global. This means that each endpoint has different rate limit counters; if you're rate limited on one endpoint, it won't affect other endpoints.
- Rate limits are now tied to both your account and your IP address. If multiple accounts share the same IP address, then they share the same rate limit counters.
- If you make a call while rate limited, you're penalized 1 second, up to a max of 30 seconds. This means that if you don't stop making calls while rate limited, you will stay rate limited forever until you stop and wait for your rate limit to recover.
- All write endpoints now have rate limits. Previously some actions, such as voting, commenting, or forum posting, didn't have rate limits.
- Added stricter rate limits for some actions, most notably creating new accounts, logging in, sending dmails, commenting, forum posting, and voting. These limits are meant to be high enough that they shouldn't affect most normal non-spammy usage.
- Raised the default write rate limit for Gold users from 2 per second to 4 per second for all other write actions. Now Gold+ users all have the same rate limits.
- Added a
/rate_limits
page where you can view your rate limits. This only updates after each API call, so it only shows the state after the last call, not the current state. - Renamed the
X-Api-Limit
HTTP header toX-Rate-Limit
.X-Rate-Limit
is now a JSON object that includes more information, including the cost of the call, the endpoint's recharge rate, and the burst limit. - Removed the
remaining_api_limit
,api_regen_multiplier
, andapi_burst_limit
fields from/profile.json
.
- Uploads: added links to the artist's profile pages to the 'Fetch source data' box.
- Tweaked light mode color scheme.
- Fixed source field being too small on uploads page.
- Fixed
rating:S
not matchingrating:safe
in autocomplete.
-
Using the Enter key to submit uploads or tag edits now shows a warning that you should use Ctrl+Enter instead.
-
Adjusted input boxes to be a bit bigger in some places, to fit better on smaller screens, and to more consistently sized throughout the site.
-
Changed colors in light mode to have better contrast and be more consistent throughout the site.
-
Changed username colors (in light mode, if you have colored usernames turned on): ** Gold users are now orange. ** Moderators are now green. ** Builders are now purplier. ** Admins are now darker red. ** Username colors now use the same colors as tag colors.
-
Parent/child borders are now darker green and darker orange.
-
Changed the current post in the parent/child box to have a darker background, to make it easier to see.
-
Changed how the New/Approved/Pending/Rejected labels look in the forum.
-
Changed how the post mode menu indicates the active mode (for tag script mode, etc). Instead of giving the page a different background color, the post is highlighted when you hover over it.
- Moved the artist tag to the translated tags section.
- Removed the artist URLs from beneath the artist tag.
- Selected tags are now shown in bold with a checkbox, instead of highlighted in blue. This is so you can see the tag type of selected tags.
- Removed support for a few disused CSS properties.
- Made the monospace font slightly thicker.
- Added Baraag upload support.
- Fixed Pixiv commentaries generating bad /jump.php URLs.
- Fixed the tag counter counting duplicate tags.
- Fixed it so that when users send a dmail to themselves, it won't get potentially marked as spam.
- Fixed spellcheck being disabled in the note edit box.
- Fixed "()" in page title when the post didn't have a copyright tag.
- Fixed
*_(cosplay)
tags with a single post having their tag count marked in red.
- You can now have multiple API keys.
- You can now see when your API keys were last used, how many times they've been used, and which IP address last used them.
- API keys can be restricted to only work with certain IPs or certain API endpoints.
- If you're an app or script developer, and you have an app that requests API keys from users, you're highly encouraged to request that users generate keys with only the minimum permissions necessary for your app to work.
- If you have a privileged account, and you run scripts under your account, you're highly encouraged to restrict your API keys to limit damage in case they get leaked or stolen.
- The login action (POST /sessions) no longer returns the
api_token
field.
- Removed the rule that new users couldn't upload in their first 7 days.
- Raised the max video length from 2:00 minutes to 2:20 minutes for video uploads.
- Changed the post vote buttons to work the same way as the comment vote buttons.
- When aliasing or renaming an artist, the artist's {{*_(style)}} tag is now moved too, if the artist has one.
- Fixed an error when searching for {{-status:any}}.
- Fixed @-ing yourself in a comment or forum post sending you a notification dmail.
- Fixed buggy keyboard movement of notes.
- Fixed the tag 'History' link not showing up on post search pages when the search contained a metatag.
- Changed 'Shortlink' to 'Copy ID' in comment menu.
- Fixed favorite icon not being filled in on favorited posts.
- Fixed series pool titles not being purple.
- Fixed bug when a logged out user tried to logout again.
-
Comment system overhaul:
- Comment scores are now visible.
- The upvote and downvote buttons are now arrows.
[quote]
tags have a new appearance.- The Comments page now shows 20 posts per page (before it was 5 posts per page).
- The comment report/edit/delete options are now hidden behind a menu.
- The comment menu has a "Shortlink" option that copies a comment #1234 link to the clipboard.
- Removed the rule that regular Members couldn't post more than 2 bumping comments per hour. Now there's no limit on the number of bumping comments you can post per hour.
- Removed the rule that you couldn't upvote your own comments.
- The way hidden comments work has changed. Now when comments are hidden, instead of being hidden completely, they're replaced with a [hidden] link that you can click to unhide the comment.
- The way deleted comments work has changed. Now when comments are deleted, they're replaced with a [deleted] placeholder, so you can see when a post has deleted comments.
- The default comment threshold has been lowered to -8. This means that comments are now hidden when their score is -8 and greyed out when their score is -4. You can edit your settings to change your threshold back. Note that a threshold of -1 in the new system is the same as a threshold of 0 in the old system. So don't set it back to 0, set it to -1. Also, the max threshold is now 5 and the minimum threshold is now -100.
- Mods can now click the comment score to see the list of voters.
-
Account settings:
- Removed the option to disable the next/previous post navbar under posts.
- Removed the option to disable keyboard shortcuts.
- Removed the option to disable tag autocomplete.
-
The next/previous post navbar is now available to logged out users. This is the navbar beneath posts that lets you move to the next or previous post in a tag search. Previously this was only available to logged in users.
-
You can now see the list of comments and forum posts you've reported to the moderators at Moderation Reports.
- Deleted comments now have some of their fields hidden in the API. The creator_id, updater_id, and body fields are hidden if you're not a moderator.
- The
POST /comment_votes
andDELETE /comment_votes
endpoints now return a comment vote instead of a comment. - The
score
param in thePOST /comment_votes
endpoint now takes the values "1" or "-1", not "up" or "down".
Full changelog: https://github.com/danbooru/danbooru/compare/production-2021.01.13-021402-utc...production-2021.01.23-063752-utc
-
Using the Enter key to submit an upload or save a tag edit will be removed in the future. Ctrl+Enter should be used instead (issue #4661).
-
Added a new Restricted user level. New users start out as Restricted if they signup from a proxy or are detected as a sockpuppet. Being restricted is like a soft ban: you can't upload, edit tags, create comments or forum posts, or otherwise make any changes to the site, but you can still keep favorites, saved searches, and other personal things. Restricted users must verify their email address to become unrestricted.
-
The Restricted system actually existed before, the only change is that now it's a public user level instead of a hidden flag on someone's account.
-
Your IP address, location, and browser version are now recorded when you login to your account. They're also recorded when you create an account, or do any sensitive account actions, such as changing your password or email address, requesting a password reset, or deleting your account. Failed login attempts to your account are also recorded. Mods will be able to view this information. This information is recorded for account security purposes and for site moderation purposes (detecting sockpuppet accounts and ban evasion).
- Fixed a bug with not being able to upload certain Hentai Foundry posts (issue #4657).
- Fixed a bug with tag scripts sometimes adding the [[null]] tag (issue #4663).
- Fixed various issues with wiki other names, artist other names, and saved search labels allowing invalid characters.
- Fixed slow autocomplete when searching for Japanese or other non-English text.
-
As described above, there's a new Restricted user level. Anything dealing with users will need to deal with a new user level.
-
Added support for the following types of searches:
-
<field>_not
searches on enum fields: -
<field>_<eq|not_eq|lt|gt|lteq|gteq>
searches on foreign key fields (user IDs, post IDs, etc): -
any_<field>_matches_regex
, where is an array field: -
Using multiple search filters on the same field. Before things like this didn't work:
-