| 3 Oct 2022 |
 Nico | A delete endpoint is useful, but how is it more flexible, if it doesn't even fullfill the original requirements? | 12:01:42 |
 HarHarLinks | i can either
- call patch with a diff
- file gets cloned
- maybe old file gets deleted implicitly
- return new mxc that i can edit in my event
or
- upload new/patched file completely
- return new mxc that i can edit in my event
- delete old file explicitly
| 12:03:36 |
| Nico | If you upload the new file completely, you don't need a delete endpoint and the original question was explicitly about not uploading a new file | 12:04:33 |
| HarHarLinks | i think patching makes little sense with e2ee | 12:04:55 |
|  Broccolo Romanesco joined the room. | 17:33:59 |
 mscbot | [MSC3902] "MSC3902: Faster remote room joins over federation (overview)" has been created: https://github.com/matrix-org/matrix-spec-proposals/pull/3902 | 18:31:53 |
| 4 Oct 2022 |
|  Michael Weimann changed their display name from Michael Weimann (back on 4/10) to Michael Weimann. | 06:44:37 |
 Andrew Morgan (anoa) | Half-Shot: wondering if you can think of any use cases for including remote users in an AS' user namespace? re: https://github.com/matrix-org/synapse/pull/14000#issuecomment-1266552433
I was thinking remote user presence, but then that would likely be covered by listening to the presence updates that a local user receives
| 08:20:13 |
 Half-Shot | I can't really think of any. Local users lines up quite nicely with federation behaviour (i.e. in order to get events, you have to have your host in the room. In order to get events over the AS, you have to have a local user in the room).
I can easily see people getting confused as to why they don't get a remote user's information down the AS api, and it turns out because they don't have any local users who share rooms with them etc. | 08:23:03 |
| Half-Shot | It's ultimately more likely to be a footgun imo. | 08:23:14 |
| Half-Shot | The only nice thing I can see is you are being explicit about what users on the remote side you are interested in, but for me that's not a huge win. | 08:24:11 |
| Andrew Morgan (anoa) | Yeah, especially as you'll still be receiving events from other remote users, which may be confusing. | 08:24:49 |
| Andrew Morgan (anoa) | cc tulir as well | 08:25:48 |
| Andrew Morgan (anoa) | https://github.com/turt2live/matrix-monitor-bot/issues/45 argues for specifying remote users in the user namespace. But I believe having a regex for all local users would cover this use case.. | 08:48:41 |
| Half-Shot | My feeling is that the AS API does need a filter API / config of some kind to filter out stuff you don't care about, which is logically seperate from namespaces imo. | 09:39:54 |
| Half-Shot | Which would help the use case of "I only care about these events, or these remote users". | 09:40:55 |
| Half-Shot | Namespaces are typically things you control / own in some fashion, and ASes can never control remote users obviously :) | 09:41:23 |
| Half-Shot | In reply to @Half-Shot:half-shot.uk
My feeling is that the AS API does need a filter API / config of some kind to filter out stuff you don't care about, which is logically seperate from namespaces imo. I should say: Largely the reason this doesn't exist is that it's far easier to simply /dev/null all the stuff you don't care about on the AS side. The only reason for it to exist is performance / privacy reasons. | 09:42:58 |
| Andrew Morgan (anoa) | Sounds like we're in agreement about limiting what the namespace covers then - thanks! | 09:49:34 |
| Andrew Morgan (anoa) | (And yes, I came across your MSC https://github.com/matrix-org/matrix-spec-proposals/issues/3806 🙂) | 09:49:47 |
| Half-Shot | I was much younger and optimistic back then! | 09:55:19 |
| Andrew Morgan (anoa) | weren't we all 🧓 | 09:55:47 |
 TravisR | In reply to @andrewm:element.io
Half-Shot: wondering if you can think of any use cases for including remote users in an AS' user namespace? re: https://github.com/matrix-org/synapse/pull/14000#issuecomment-1266552433
I was thinking remote user presence, but then that would likely be covered by listening to the presence updates that a local user receives
There are T&S aspects which are useful, however these are also covered by an implicit .* rooms namespace | 13:48:46 |
|  condencionadoVEVO changed their profile picture. | 17:08:52 |
| mscbot | [MSC3903] "MSC3903: X25519 Elliptic-curve Diffie-Hellman ephemeral for establishing secure channel between two Matrix clients" has been created: https://github.com/matrix-org/matrix-spec-proposals/pull/3903 | 17:33:29 |
| 5 Oct 2022 |
|  Naveen Chandra joined the room. | 04:18:19 |
|  Florian Jacob joined the room. | 20:05:09 |
|  @florian:dsn.tm.kit.edu left the room. | 20:05:13 |
| 6 Oct 2022 |
|  Kerry Archibald [out] changed their display name from Kerry Archibald to Kerry Archibald [out]. | 11:31:12 |
|  benp (away) changed their display name from benp to benp (away). | 23:04:41 |
