You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should really be an command (to appservice), curl/POST API, or some method of unprovisioning an irc-channel from matrix side. Not having this is most obvious in an room that was once provisioned aka joined directly with #ircnet_#channel:matrix.org way and later on room gets upgraded or totally new room is made and then same irc-channel is plumbed to new room.. Everything is otherwise okay, but everything that is seen on irc-side is still carried onto the old room, and also if some matrix user joins the "provisioned room" address it goes to old channel, not the new plumbed one.
The text was updated successfully, but these errors were encountered:
Basically somewhat discussed in the past here: #387 but for today as things has moved on this has become diffirent kind of issue, like I described above...
Basically all I ask is that on provisioned room an room admin (that has proper PL in bridge-appservice mind too) could issue "unprovision" command that would do whatever it needs to make room state like "virgin"... Either that, or honor/follow plumbing command so that remote address follows to plumbed room... Again could even ask provisioned OP yes/no so no malicious attemt can be done on a whim...
There should really be an command (to appservice), curl/POST API, or some method of unprovisioning an irc-channel from matrix side. Not having this is most obvious in an room that was once provisioned aka joined directly with #ircnet_#channel:matrix.org way and later on room gets upgraded or totally new room is made and then same irc-channel is plumbed to new room.. Everything is otherwise okay, but everything that is seen on irc-side is still carried onto the old room, and also if some matrix user joins the "provisioned room" address it goes to old channel, not the new plumbed one.
The text was updated successfully, but these errors were encountered: