Releases 0.9.379 - 0.9.382: Change Log

In October and November we prepared for and then deployed the updated Terms of Service. We also included a variety of smaller improvements from as many contributors as we could.

Special thanks and welcome to our first-time contributors Amy Lee, anechol, Dev21Maker, lydia-theda, MarleaM, minionluvr, Mugdha Gupta, mystyrust, nil-cipher (Wanda), Paola Solari, phthallo [Annabel Quach], and slavalamp!

Credits

• Coders: Amy Lee, anechol, Bilka, Brian Austin, Cesium-Ice, Dev21Maker, lydia-theda, MarleaM, Mugdha Gupta, minionluvr, mystyrust, nil-cipher (Wanda), Paola Solari, phthallo [Annabel Quach], Sarken, slavalamp
• Code reviewers: Bilka, Brian Austin, james_, lydia-theda, Sarken
• Testers: Bilka, Brian Austin, calamario, Deniz, Flerken, lydia-theda, Sarken, Taki, Teyris, therealmorticia, wichard

Details

0.9.379

On October 5, we deployed a bug fix in preparation for the upcoming changes to the Terms of Service as well as two other small fixes.

• [AO3-5538] - Tag set pages containing a nomination for an existing canonical tag used to give a 500 error if the wrangling team edited the canonical tag's suffix (e.g., " - Freeform") or diacritics. Now the nomination gets updated correctly and the error will no longer happen.
• [AO3-6815] - We made some tweaks to our README and CONTRIBUTING documentation on GitHub.
• [AO3-6816] - We bumped our version of reviewdog/action-rubocop from 2.19.0 to 2.19.1.

0.9.380

On November 4, we did a small deploy relating to the planned updates to the Terms of Service.

• [AO3-6825] - When tag wranglers changed a tag's suffix (e.g., " - Freeform") or diacritics, the changes were not being reflected on any bookmarks where the tag was used as a bookmarker's tag. We've added some cache expiration to make sure they'll get updated going forward.
• [AO3-6824] - Some of the automated tests we run using GitHub Actions require a dependency called ImageMagick, which used to be installed on Actions by default. An update to Actions stopped including it, so we updated our tests to install it.
• [AO3-6828] - We wrote some code that allowed us to email all AO3 users to inform them about the TOS update and Underage warning rename.

0.9.381

On November 19, we deployed the updates to the Terms of Service that were announced earlier in the month.

• [AO3-6838] - We updated the text and format of the TOS and TOS FAQ pages. This also required us to update various references to those documents across the Archive, including the prompt that requires you to agree to the TOS before accessing the site.
• [AO3-6831] - As part of the Terms of Service update, we've renamed the "Underage" warning tag to "Underage Sex" to make its meaning and purpose easier to understand. Please refer to the "Clarification to the Archive Warning for underage sexual content" section of the AO3 Terms of Service: 2024 Update Guide for more information.
• [AO3-6837] - We switched our Docker setup for automated testing to Chromium instead of Chrome to support Apple Silicon.

0.9.382

On November 24, we updated the DMCA Policy and implemented a number of small improvements all over the Archive.

• [AO3-4283] - The HTML classes on the marked for later section of the homepage were inconsistent with the classes we use on the marked for later page itself, so we've standardized things a bit.
• [AO3-5421] - On works, news posts, and various other places, the vertical spacing between lines of text could vary a bit depending on whether the text was in a paragraph or, for example, a list. We made some adjustments to keep it consistent.
• [AO3-5951] - If you tried to use an unordered list in your work summary or bookmark notes, the list displayed horizontally on the blurb. We've made it display vertically, as you'd expect from a list.
• [AO3-6244] - We removed an extra underline from hovered links in the Notes section of works.
• [AO3-6268] - Emails generated by gift exchanges would be sent as only one email to all owners at once. Now they will be sent to each owner individually, so each email can be translated separately in the future.
• [AO3-6376] - The browser page titles for changing username, password, and email had an extra "User" at the end. We've removed it.
• [AO3-6819] - We fixed some invalid and inaccessible HTML on the Blocked Users and Muted Users pages.
• [AO3-6834] - We made the "Parent Thread" link accessible when reviewing comments left on works or news posts with comment moderation.
• [AO3-6821], [AO3-6826], [AO3-6827], [AO3-6839] - Our automated dependency updater updated several of our dependencies: webrick from 1.8.1 to 1.8.2, Rails from 7.0.8.4 to 7.0.8.5, rexml from 3.3.6 to 3.3.9, and codecov-action from 3 to 4.
• [AO3-6768] - Did you ever look at the browser page title on your drafts page? It used to say "Drafts Work," which was just weird. Now it says "username - Drafts," much like your works page says "username - Works."
• [AO3-6829] - We updated the DMCA Policy page with new text from our Legal and Policy & Abuse teams that better explains the difference between Abuse reports, DMCA takedown notices, and DMCA counternotices – what each of them are, how to submit one, and how we handle them.
• [AO3-6840] - We added a link to the TOS FAQ to our site map.
• [AO3-6841] - In response to feedback from the 2024 TOS Update news post, Policy & Abuse has updated the definition of the "Underage Sex" warning to read "sexual activity involving characters under the age of 18" in order to more clearly indicate that the "Underage Sex" warning is required whether or not the sex is consensual. (All works featuring non-consensual underage sex must carry both the "Rape/Non-Con" and "Underage Sex" Archive warnings, or else use the "Creator Chose Not To Use Archive Warnings" label.)
• [AO3-6842] - As part of AO3-6838, we updated the work posting and editing forms to include links to the Content Policy and the TOS FAQ. Now that reminder also appears on the forms for posting or editing a chapter, previewing a draft, importing a work, and editing a work's tags.
• [AO3-6843] - To make it easier to log in if you've already agreed to the TOS, or to follow explanatory links from the TOS if you're still deciding whether to agree to them, we've stopped the TOS popup from appearing on the homepage, FAQs, and login page. We've also fixed an issue where the popup appeared on error pages for the Support and Policy & Abuse forms.