search

turt2live / matrix-voyager-bot

A Matrix bot that attempts to travel the whole network, finding rooms along the way
GNU General Public License v3.0
45 stars 5 forks source link

Support bridged rooms in a more friendly way #120

Open turt2live opened 7 years ago

turt2live commented 7 years ago

Right now voyager just auto-joins the room, and some bridges may encounter issues with this.

Indirectly, this has been mentioned in https://github.com/SijmenSchoon/telematrix/issues/18

If voyager joins the room it'll possibly cause permissions issues. This isn't unique to telematrix. The IRC bridge will create rooms if someone happens to link an alias, which is already happening (#freenode_#example:matrix.org is valid).

Unsure of how to handle this at the moment. Some way to query the bridge would probably work. https://github.com/turt2live/matrix-voyager-bot/issues/63 may help with this as bridged rooms should appear in the directory of the target server. Other options would be bridge-specific support for this kind of thing (ie: GET /api/room/#alias:domain.com results in {"exists":true}).

14mRh4X0r commented 6 years ago

Leaving a room when there are no or only appservice users might work as well, although I suppose you would need some kind of list of known appservices.

Mikaela commented 2 years ago

Are you aware of https://github.com/matrix-org/matrix-appservice-irc/issues/1474#issuecomment-913025682 and able to either prove or disprove it? I think Voyager is on too many Libera.Chat bridged rooms and thus at times temporarily blocks new ones receiving messages from IRC when using the default room configuration.