| 4 Apr 2024 |
 raitobezarius | and if a new room spawn close to my area of interests | 21:49:54 |
| raitobezarius | i can quickly notice it | 21:49:57 |
| raitobezarius | with the current matrix tooling, i constantly miss out on rooms until someone mention its existence to me | 21:50:08 |
 @joepie91:pixie.town | okay, but in what way is this structurally different from spaces and subspaces? | 21:50:54 |
| raitobezarius | i'd say the main difference is that i can urlwatch a webpage and we control the layout, split things as we want and have multiple views | 21:51:25 |
| raitobezarius | and that i'm utterly unable to use the space / subspaces feature of matrix | 21:51:44 |
| raitobezarius | and i surmise that many clients / users just ignore them | 21:51:52 |
| raitobezarius | also | 21:52:18 |
| raitobezarius | our split for subspaces is Topics / Teams / ... | 21:52:23 |
| raitobezarius | Not "System Administration" / "Politics" / ... | 21:52:31 |
| raitobezarius | For example | 21:52:32 |
| @joepie91:pixie.town | sure. but nothing is preventing multiple views, from a technical perspective | 21:52:58 |
| raitobezarius | If we believe this to be feasible and accessible for end users, I'm all for it | 21:53:28 |
| raitobezarius | I simply cannot conceive how to make it with the Matrix tooling and how to make it work for everyone using Matrix | 21:53:43 |
| @joepie91:pixie.town | I think there are real UI problems with actually viewing spaces, but that's why I was suggesting an automated exporter that exports the structure to a webpage | 21:53:51 |
| raitobezarius | Yeah | 21:54:08 |
| @joepie91:pixie.town | mainly to avoid having to maintain two separate hierarchies of rooms and them inevitably going out of sync over time | 21:54:19 |
| raitobezarius | So my proposal is to make the automation manual and say that from now on, everytime you create a new room, you must have an entry in the room directory for it | 21:54:31 |
| raitobezarius | Because I believe the metadata quality will be higher | 21:54:40 |
| raitobezarius | In reply to @joepie91:pixie.town
mainly to avoid having to maintain two separate hierarchies of rooms and them inevitably going out of sync over time I think sync issues won't happen though | 21:54:47 |
 @patka_123:matrix.org | I personally would've rather had a list myself. I've found new rooms on multiple occasions because people randomly mentioned them. The Matrix UI is cluncky and I somehow didn't find them myself, although I went throuw the spaces | 21:54:52 |
| raitobezarius | Integrating a new room inside of the space requires going via a human (hexa right now) | 21:55:00 |
| @patka_123:matrix.org | * I personally would've rather had a wiki list myself. I've found new rooms on multiple occasions because people randomly mentioned them. The Matrix UI is cluncky and I somehow didn't find them myself, although I went throuw the spaces | 21:55:12 |
| raitobezarius | But I think we have a disagreement over a small procedural point | 21:55:23 |
| raitobezarius | Exporter can automatically create an empty entry and wait for someone to fill it | 21:55:38 |
| raitobezarius | Or synchronize the topic or something | 21:55:45 |
| @joepie91:pixie.town | right, I'm not really sure where the disagreement is because functionally these look like the same thing to me | 21:56:09 |
| @joepie91:pixie.town | I was proposing an auto export mainly because it is a) easy to implement b) easy to maintain | 21:56:24 |
| raitobezarius | So an automated exporter can never do the work of an editor | 21:56:28 |
| raitobezarius | But an editor can do the work of an automated exporter | 21:56:34 |
