We have a list of all the potential requirements for our chat infrastructure. The next step is to decide which of those requirements are essential.
These requirements will be used to select the shortlist of chat technologies that we will evaluate in detail. The only apply to the evaluation process itself and don't imply an automatic decision to drop our current official chat infrastructure (IRC).
We could extend this exercise to deciding on the priority of other features, but let's focus on what's absolutely essential for now.
I tested this today, and my message from myself (as an unregistered IRC user) reached me on Matrix just fine. So I think this actually somehow got fixed at some point?
@heftig it's absolutely true but... it's the best compromise I could come up with so far. If you know better alternatives I'm absolutely open to hear about it!
AFAIK all +e override all +b. Wouldn't that also make it impossible to ban authenticated people at all?
Is it perhaps possible to ban merely unauthenticated people and except only the bridge users?
Following a conversation with unrealircd maintainers, they told me that setting those modes to a channel would:
+b *@*
-> ban everyone+e ~a:*:*@*
-> except people who are authenticated against NickServ+e *@ip.subnet.of.the.bridge.*
-> and except people who come from the bridgeHi, what's the status of this?
Silently dropped messages is the worst issue IMO.
The issue has been solved in https://github.com/matrix-org/matrix-appservice-irc/issues/1219
The MSC has been merged, and Firefox nightly even supports matrix:
links
Element does have a centralized view for notifications (the bell on the top right corner). This feature is still wanted in Fractal Next, the rewrite of Fractal which is happening right now.
Excellent news, the maintainer of the IRC bridge landed a "no-kick from IRC" PR today! The option should be available in the next release, which we will test extensively.