misty.cafe/mistykey
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

replace "Mark instance as NSFW" toggle with an instance-level mandatory CW

Browse source
This commit is contained in:
Hazelnoot 2025-06-29 18:56:42 -04:00
parent 604f5a5c68
commit d62be884b3
24 changed files with 44 additions and 127 deletions
Download patch file Download diff file Expand all files Collapse all files

16
UPGRADE_NOTES.md
View file

@ -1,6 +1,18 @@
# Upgrade Notes
## 2025.X.X
## 2025.5.2
### Mark instance as NSFW
The "Mark instance as NSFW" has been removed in favor of the new "mandatory CW" / "force CW" system.
Moderators can now apply any Content Warning of their choice to all notes from an instance by populating the "Force content warning" field on that instance's info page.
The new Content Warning applies immediately, is retroactive, and does not federate or "infect" replies in a thread.
The upgrade will automatically a content warning of "NSFW" for instances that were formerly marked as NSFW, which displays as `[instance name] is flagged: "NSFW"` to users.
The `notes` table is also cleaned up to remove any leftover "Instance is marked as NSFW" content warnings from posts.
Staff can then remove or modify the new CW as usual.
## 2025.2.2
### Authorized Fetch
@ -13,6 +25,8 @@ Do not remove it before migration, or else the setting will reset to default (di
### Hellspawns
**Note: this workaround is no longer needed on Sharkey version 2025.5.2 and later, as "Mark instance as NSFW" has been completely rewritten.**
Sharkey versions before 2024.10 suffered from a bug in the "Mark instance as NSFW" feature.
When a user from such an instance boosted a note, the boost would be converted to a hellspawn (pure renote with Content Warning).
Hellspawns are buggy and do not properly federate, so it may be desirable to correct any that already exist in the database.