 | #matrix-spec | 175 Members |
| Discussion of specific Matrix Spec Change proposals | https://matrix.org/docs/spec/proposals | Design draft folder at: https://drive.google.com/drive/folders/0B4wHq8qP86r2ck15MHEwMmlNVUk | 64 Servers |
| #matrix-spec | 175 Members |
| Discussion of specific Matrix Spec Change proposals | https://matrix.org/docs/spec/proposals | Design draft folder at: https://drive.google.com/drive/folders/0B4wHq8qP86r2ck15MHEwMmlNVUk | 64 Servers |
| Timestamp | Message | |
|---|---|---|
| 19 Jan 2020 | ||
| 22:58:47 |  TravisR | It's the ancient version of the docs folder in the topic of this room |
| 22:59:58 | TravisR | Or at least it was. It looks to be useless now |
| 23:00:16 |  Aaron | Yeah it seems like something that should just be deleted |
| 23:02:10 |  Matthew | i'd prefer we didn't delete the ancient history (drafts, attic) etc, otherwise archaeology becomes needlessly hard |
| 23:02:43 | Matthew | !github create "the SSO section of CS API could really do with some sequence diagrams" |
| 23:02:44 |  Github | Created issue: https://github.com/matrix-org/matrix-doc/issues/2417 |
| 23:03:43 | TravisR | We can at least merge the directories |
| 23:03:46 |  nephele | version controll to the rescue :) |
| 23:04:21 |  Nico | Well, even with version control it is sometimes hard to discover deleted files |
| 23:04:21 | TravisR | Not advocating we delete drafts, just contain the archeological dig site |
| 23:04:46 | nephele | Nico: yeah, but it makes reasoning about the past easier |
| 23:05:26 | Nico | I don't see how that makes it easier, since both still clearly have dates, if you delete the file or not |
| 23:06:10 | Nico | Keeping old stuff around is an issue when programming, but with docs and specs, when they are clearly labeled as historical, I see keeping them around as a benefit |
| 23:06:49 | TravisR | In reply to@matthew:matrix.orgIt's 4 steps? |
| 23:07:34 | TravisR | *5 |
| 23:07:59 | Matthew | yup, but a picture tells a thousand words |
| 23:08:43 | nephele | must be a highly compressed picture |
| 23:09:11 | TravisR | It'd be a very boring sequence diagram. The numbered list feels clearer than a diagram. |
| 23:10:51 | TravisR | The synapse docs could certainly use a sequence diagram for how it works |
| 23:11:22 | TravisR | The spec doesn't really concern itself with how the auth system and homeserver "interact" |
| 21 Jan 2020 | ||
| 15:25:06 |  vermillion:core | Redacted or Malformed Event |
| 15:11:33 |  grin | why do I get presence and account_data events in |
| 15:11:45 | grin | * why do I get presence and account_data events in |
| 15:12:04 | grin | * why do I get presence and account_data events in |
| 15:14:29 | grin | Or how shall I join a room then get only the last few message events, and nothing else really (maybe room create and its state changes)? Or, phrasing a different way. how can I join a new room the fastest way possible to get the last few messages and able to reply them, without any more info (like members or old messages)? |
| 16:43:34 | TravisR | Probably some variation of https://github.com/matrix-org/synapse/issues/4299 rather than a spec problem. #matrix-dev:matrix.org is preferred for development questions. |
| 23:00:05 | grin | TravisR: Well I am in phase1, which is to ask whether what I am doing is proper spec-wise. ;-) |
| 23:00:51 | TravisR | when in doubt, over-specify the filter |
| 23:01:15 | Nico | That is still matrix-dev, I'd say. matrix-spec is for phase 3: the spec has issues, which should be fixed, imo |
| 23:01:54 | grin | 'kay. |