Stop plugins from clogging up my screen with information

[Pumpkin]

Specs

Hello, lately I’ve been exploring Obsidian’s rich functionality, especially the extensive plugin experience.

I’m using the following plugins in unison:

• Consistent attachments and links
• Unique attachments

Please note I’m using the most up-to-date version at the time of writing (“1.4.16”: ‎Obsidian - Connected Notes on the App Store), and running iPadOS 17.1.2 .

Steps to reproduce

(I’ve sent a zip file of my vault so that hopefully it will be easy for everyone to look at my findings themselves)

1. Notice “Test file” is located at the root of the vault, and embeds an image attachment stored in a folder called “_attachments”, which is in the same directory as ”Test file”: this structure (an “_attachments” folder in the same directory as the note which embeds the attachments) is meant to be maintained even if the note containing all the embedding links is movedI.
2. In fact, upon moving “Test file” into “Test folder”, a series of plugin-related messages appear on the top-right of the screen.

This is certainly useful information to have at hand, especially for verifying the plugins correct functionality, but starts to become annoying after a while: after all moving files is a very common operation in file management.

Question

Any way I can prevent these messages from popping up on the screen?

(Clicking on them seems to remove them from view after about a second, but I’m looking for something which doesn’t require my interaction and makes them totally disappear)

Zip file of vault I used for testing

Test vault.zip (3.3 MB)

[ush]

A quick fix would be the following CSS snippet.

.notice {
    display: none;
}

But it completely shuts out all notifications, including emergent ones, so it can be dangerous. So I recommend filing an issue to the plugin’s GitHub repository.

[Pumpkin]

I see, thanks for the insight! I’ll definitely consider this if I ever have the chance to experiment with CSS in Obsidian. I’ll mark your answer as a solution since now I understand that this is something more relevant to GitHub issues in the plugin’s repository.