search

misskey-dev / misskey

🌎 An interplanetary microblogging platform 🚀
https://misskey-hub.net/
GNU Affero General Public License v3.0
9.81k stars 1.32k forks source link

Sensitive Media Warning Not Removed in Profile 'Files' Section #13854

Open namecantbebl0nk opened 3 months ago

namecantbebl0nk commented 3 months ago

💡 Summary

There is an inconsistency with the 'display of sensitive media' label in the profile 'Files' section. When 'Display media marked as sensitive' is selected in the settings, the warning is removed, and sensitive media is shown as expected (see screenshot below).

timeline

However, when visiting account's profile, the 'Files' section still shows the sensitive media warning, even if the account is from the same instance or a different instance (see screenshot below). files

This bug has been tested on three different Misskey instances: https://misskey.id, https://misskey.art, and https://misskey.social, confirming that it is not an instance-specific issue.

🥰 Expected Behavior

There should be no sensitive media warning label.

🤬 Actual Behavior

The sensitive media warning label still appears.

📝 Steps to Reproduce

  1. Go to https://misskey.id and create an account.
  2. Go to Settings > General > Display of sensitive media, and select 'Display media marked as sensitive'.
  3. Visit https://misskey.id/@namecantbebl0nk or https://misskey.id/@nemonerin@misskey.io or any account that has uploaded sensitive media.
  4. Scroll down to the 'Files' section of the profile.
  5. Observe that the images are still hidden behind the sensitive media label.

💻 Frontend Environment

* Model and OS of the device(s): Windows 10 22H2 (OS Build 19045.4291)
* Browser: Microsoft Edge Version 125.0.2535.51 (Official build) (64-bit)
* Server URL: https://misskey.id/
* Misskey: 2024.3.1

🛰 Backend Environment (for server admin)

* Installation Method or Hosting Service:
* Misskey:
* Node:
* PostgreSQL:
* Redis:
* OS and Architecture:

Do you want to address this bug yourself?

kakkokari-gtyih commented 3 months ago

Changing a media's sensitive flag is equivalent to editing the note, so that's not propagate to the remote and will not fixed at the present time. The reason why some components are not updated when changed locally may be due to the page cache (Misskey's internal cache done at the router layer).

t1nyb0x commented 3 months ago

@namecantbebl0nk Have you made any progress or learned anything about what @kakkokari-gtyih was talking about?