| 7 Jun 2021 |
David Arnold | An alternative could be argument here: "please remove there" | 13:28:32 |
| Linux Hackerman joined the room. | 13:29:58 |
David Arnold | Linux Hackerman did my reply actually resolve your suggestion? (In that case we can delete there) | 13:30:43 |
David Arnold | Redacted or Malformed Event | 13:30:52 |
David Arnold | @lukegb doesn't seem to be here 🤐 | 13:31:27 |
Las | Discourse could be built on top of Matrix TBH | 13:34:59 |
Las | Eventually, Discourse could be replaced by Hummingbard or Cerulean | 13:43:29 |
David Arnold | For the te being though, I imagine some sort of clarification what kind of content should go where. And maybe a mapping of discourse topics to matrix spaces.
That way, we can "discuss" here and "record" there. | 13:55:55 |
David Arnold | In effect discourse could potentially become a collection of "discussion outputs / aggregates". | 13:56:30 |
David Arnold | I'd find that useful, but no ide if it would turn out to be practical. | 13:56:52 |
David Arnold | * I'd find that useful, but no ide if it would turn out to be practical to do. | 13:57:00 |
sumner | I wonder if something like the TWIM bot would be useful here. Basically, there's a TWIM room that anyone can post to, but messages with @TWIM or reacted to with ⭕️ get forwarded to a separate updates room that someone pulls from to create the TWIM post for that week. Only a few users can post to the updates room, so all discussion is in the main TWIM room. This may be overkill for "Nix Matrix Suggestions/Discussions", however, I think it may be interesting to set up such a bot anyway. It may come in handy in other scenarios. | 14:05:33 |
sumner |  Download image.png | 14:10:27 |
sumner | ^ https://matrix.to/#/!LPqOcoJQuGkweiTedq:riot.ovh/$RPyyxAJnec9tP1w2qVbQnZ3JNHcv9ipQgEm-Bxf5IpI?via=matrix.org&via=tchncs.de&via=dendrite.matrix.org | 14:10:41 |
David Arnold | * For the time being though, I imagine some sort of clarification what kind of content should go where. And maybe a mapping of discourse topics to matrix spaces.
That way, we can "discuss" here and "record" there. | 14:19:12 |
David Arnold | * I'd find that useful, but no idea if it would turn out to be practical to do. | 14:19:37 |
David Arnold | Such bot could even operate all over the nixos space. For people who need a digest for what's going on on matrix. | 14:20:55 |
David Arnold | * Such bot could even operate all over the nixos space. For people who need a digest for what's going on on matrix. (Via the ⭕ reaction) | 14:22:07 |
David Arnold | (presuming responsible usage) | 14:22:32 |
sumner | In reply to @blaggacao:matrix.org (presuming responsible usage) This is a strong assumption 😂 | 14:27:28 |
sumner | I think we'd need mjolnir set up before that happens | 14:27:51 |
hexa | In reply to @blaggacao:matrix.org
For the time being though, I imagine some sort of clarification what kind of content should go where. And maybe a mapping of discourse topics to matrix spaces.
That way, we can "discuss" here and "record" there. suggestions room gets: suggestions and a shortcut to the reasoning, if necessary | 14:38:06 |
David Arnold | (oh, the context was matrix & discourse coexistence) | 14:42:44 |
| Gytis Ivaskevicius joined the room. | 16:19:17 |
Gytis Ivaskevicius | Currently there are issues with rooms showing up under "All rooms" | 16:20:15 |
Gytis Ivaskevicius |  Download image.png | 16:20:17 |
Gytis Ivaskevicius | Also these subspaces do not seem to be working all that well: | 16:20:40 |
Gytis Ivaskevicius |  Download image.png | 16:20:41 |
sumner | Gytis Ivaskevicius: you may be interested in this GitHub issue: https://github.com/vector-im/element-web/issues/17203 | 16:20:52 |
sumner | Also, the "Topics" not being under "NixOS" is normally fixed with a restart or cache clear I think | 16:21:36 |