Create Portal on new message without deleted-portals

[whowantsmybigdata]

Hi,
thanks for this great project! Am forced to using discord for work and also I like using it from time to time for support-channels for projects if theres no other option.

Has been working flawlessly for me but I have one concern which is really annoying for me (and maybe for some others as well):

When choosing bridge-modes for my use-cases I can only use create-on-message. Otherwise I miss when a new channel is started, somebody formally unknown creates a conversation with me etc.
Thats nice and well but it also means, the portals which I manually and deliberately deleted (because I don't need them) are recreated as well if sbd. posts sth.

Feature Request: a new bridge-mode which does sth like create-on-message-exept-deleted-portals

Real world example for use-case: A discord guild for discussing a podcast. Every new episode gets a new channel, so I want a new portal to be created. The same when sbd pm's me of course. if-portal-exists doesn't work because of that.
create-on-message annoys me because of some channels which are used frequently but I don't want them to be bridged. Like a channel for discussing (unrelated) game-suggestions, a channel for memes etc. I manually do !discord delete-portal for them but they are recreated every time a new message arrives (which is the desired action in that mode I know). I can just mute them but I still get a growing number of unread chats in my matrix client which triggers my need for a clean interface...

Sorry, I have almost no idea of coding so I don't know if thats asked to much. If so, feel free to ignore.

Thanks for reading!

[ScharadaValcta]

One major advantage of this feature request is that it gives users better control over the bridge by allowing them to exclude specific channels without completely switching to manual management. It also helps reduce clutter and distractions, as frequently active but unimportant channels—such as meme or off-topic discussions—will no longer be recreated after being deliberately removed. This leads to a much cleaner and more organized Matrix client experience, especially for users who prefer a tidy interface without unnecessary, ever-growing channel lists.

Another important benefit of this feature request is the reduction of storage usage on the Matrix server. Every automatically created portal room consumes server resources, specially media storage. When unwanted portals are continuously recreated after being manually deleted, this leads to unnecessary storage bloat over time. By preventing the recreation of deliberately removed portals, the proposed feature helps keep the Matrix server leaner and more efficient.

This is especially relevant for self-hosted Matrix instances or those with limited resources, where excessive room creation can contribute to higher disk usage and slower performance. Reducing the number of unnecessary rooms also means less metadata and event history to store, ultimately leading to a more lightweight and performant Matrix environment.

i very much hope that the feature will be implemented or is already in the making

[ScharadaValcta]

i notice part of is a duplicate of #56