Conversation
turt2live
added
requires-room-version
|
|
||
| ## Alternatives | ||
|
|
||
| Pseudo IDs of some variety, or senders-as-keys, might be an easier/different way to solve this MSC's |
There was a problem hiding this comment.
I'm pretty concerned that this stack of MSCs collides almost directly with MSC #4014 and #4080. while aiming solve slightly different problems, the changes hit in almost precisely the same place. Once we finally get back to senders-as-keys I think we should reconcile the two together rather than having competing stacks of MSCs.
There was a problem hiding this comment.
This MSC is not meant to be conflicting, but indeed all the MSCs involved will have to consider each other's use cases before moving forward.
| A common feature request is a room structure where most/all members are not aware of each other. Matrix | ||
| currently requires all senders to be aware of each other for routing purposes, making it difficult to hide | ||
| a user's subscription to the room. |
There was a problem hiding this comment.
The direction of thought is interesting here.
Will I make stretch by extending it to "have rooms as topics anyone can chat about"?
Akin to adding tags to messages.
Interestingly, this unlocks one to define what he wants to see about a topic.
E.g., events about "politics" (tag) from my friends.
A kind of personalized feed.
That includes events shared to you by others cordially (since they know you need them). The grassroots style. Wondered about it here.
3 participants
Rendered
Dependencies: