| 2 Jun 2021 |
 hexa | (like this one) | 23:25:02 |
 emily | ok I thought "we can't give out :nixos.org accounts because of the $10/month user limits" meant "nobody gets :nixos.org accounts", not "the most special people get them", sorry :p | 23:25:13 |
| emily | so yeah, it would probably be a good long-term futureproofing idea to have backup admins in the rooms I guess | 23:25:29 |
| hexa | graham and eelco have one account on nixos.org each | 23:25:30 |
 kevincox | Well we need a couple of people with nixos.org accounts to manage the aliases and room directory for nixos.org | 23:25:37 |
| hexa | three are "free", but that doesn't mean they will be used | 23:25:43 |
| emily | yeah, admin is unavoidable | 23:25:46 |
| hexa | the homeserver on nixos.org is just for the control over the namespace | 23:25:57 |
| emily | can a foreign-homeserver user not be admin in a homeserver for managing aliases and stuff? that's a bit sad | 23:26:02 |
| hexa | you can only add public aliases for homeservers you control | 23:26:30 |
| hexa | i could add #nixos-matrix-suggestions:lossy.network | 23:26:39 |
| hexa | but I could only publish it if i was at least moderator | 23:26:47 |
| emily | yeah | 23:27:40 |
| emily | I just wasn't sure if you had to be native to that homeserver to publish them | 23:27:41 |
| kevincox | I think right now yes. | 23:28:22 |
| kevincox | In the future spaces will make homeserver directories obsolete. But right now the support is sparse. (AKA just Element IIUC) | 23:28:51 |
| kevincox | * In the future spaces will make homeserver directories obsolete. But right now the support is sparse. (AKA just the Element clients IIUC) | 23:28:59 |
 sumner | I don't think that homeserver directories will ever become entirely obsolete, but I think they will definitely become less necessary. | 23:33:02 |
| kevincox | IDK. There was some talk about if the homeserver directory APIs could be re-targeted at a space. Basically keep them there for compatibility but under the hood they are just reading from and writing to a space. Of course there is still work to do like making sure that peeking and everything works as it does today. | 23:34:51 |
| hexa | finding spaces is still a bit tedious :) | 23:35:07 |
| kevincox | What do you mean by "finding"? | 23:35:20 |
| hexa | can't exactly search for spaces | 23:35:36 |
| hexa | only rooms | 23:35:37 |
| sumner | discovery of spaces is total crap currently | 23:35:48 |
| kevincox | Well this would be solved because the room directory would be a well-known space per server. And you can nest other spaces inside of it. | 23:36:08 |
| sumner | In reply to @kevincox:matrix.org
IDK. There was some talk about if the homeserver directory APIs could be re-targeted at a space. Basically keep them there for compatibility but under the hood they are just reading from and writing to a space. Of course there is still work to do like making sure that peeking and everything works as it does today. There will always be a number of rooms which are not part of a space. | 23:36:11 |
| kevincox | Just like there are always a number of rooms that aren't in the server directory right now 🤷 | 23:36:33 |
| sumner | In reply to @kevincox:matrix.org
Well this would be solved because the room directory would be a well-known space per server. And you can nest other spaces inside of it. this sounds like a bad idea. How would permissions work? Who would be allowed to control it? | 23:36:42 |
| kevincox | At the core both features are just a list of rooms. Spaces are growing new features quickly though. | 23:37:04 |
| kevincox | In reply to @sumner:sumnerevans.com
this sounds like a bad idea. How would permissions work? Who would be allowed to control it? Can't you ask the same questions about the server directory today? | 23:39:42 |
