!NasysSDfxKxZBzJJoE:matrix.org

#matrix-spec

735 Members
Discussion regarding the Matrix spec. Please ensure comments end up on MSCs! | https://spec.matrix.org/proposals/ | Offtopic/expansion: #matrix-spec-offtopic:matrix.org | Office: #sct-office:matrix.org | Doc/spec writing: #matrix-docs:matrix.org | SCT Workflow: https://github.com/orgs/matrix-org/projects/31 | Old design drafts: https://drive.google.com/drive/folders/0B4wHq8qP86r2ck15MHEwMmlNVUk 315 Servers

Load older messages


SenderMessageTime
26 May 2024
@clokep:matrix.orgclokepSounds like another good MSC! I think there’s a spec issue open on that issue too.10:55:41
@clokep:matrix.orgclokepMight need server sent events or whatever Travis’ MSC is called.10:55:54
@emma:rory.gayEmma [it/its] i personally dont think that should be a server task, given it kinda takes some of the user control away 10:56:11
@matthias:ahouansou.czMatthias
In reply to@emma:rory.gay
i personally dont think that should be a server task, given it kinda takes some of the user control away
I mean, they could always just use /send if they choose to.
10:57:16
@emma:rory.gayEmma [it/its] eg. what if i want to write my own vias, explicitly pointing towards servers i know wont leave the room (eg. how the element.io server isnt likely to leave rooms from the element org)
i'd expect servers not to overwrite those
10:57:45
@matthias:ahouansou.czMatthias I guess servers can just store whether the event was sent via /send. 10:58:34
@matthias:ahouansou.czMatthiasAnd if so, don't touch it.10:58:39
@matthias:ahouansou.czMatthias
In reply to@clokep:matrix.org
Might need server sent events or whatever Travis’ MSC is called.
MSC4049?
10:59:15
@mscbot:matrix.orgmscbot

MSC4049: Sending events as a server or room by @turt2live

10:59:16
@clokep:matrix.orgclokepYeah that’s the one.10:59:38
@matthias:ahouansou.czMatthias Seems to be so, it even list updating m.space.child as an example. 10:59:53
@matthias:ahouansou.czMatthias Seems to be so, it even lists updating the via field of m.space.child as an example. 11:00:07
@clokep:matrix.orgclokepBtw me (or other spec folks) saying “this would be a good MSC” is not me saying “this should absolutely be in the spec”. It means it is with exploring enough that a more formal document than chat that can list pros, cons, security concerns, etc is worth doing. Then an educated decision on whether to accept it reject can be made.11:01:10
@morguldir:sulian.eumorguldiri wonder what's gonna happen to https://github.com/matrix-org/matrix-spec-proposals/pull/394613:13:18
@morguldir:sulian.eumorguldirneeds-implementation label can be removed i think at least13:13:43
@matthias:ahouansou.czMatthias On m.space.* again, the spec says "the creation of loops is explicitly disallowed". Does this mean servers should reject C-S /send requests that would cause loops? 13:18:55
@matthias:ahouansou.czMatthiashttps://spec.matrix.org/v1.10/client-server-api/#managing-roomsspaces-included-in-a-space13:19:19
@cat:feline.supportCat
In reply to @morguldir:sulian.eu
i wonder what's gonna happen to https://github.com/matrix-org/matrix-spec-proposals/pull/3946
Well i mean the usecase for it was for Gitter.
13:53:51
@cat:feline.supportCatBut as far as i understand that problem is considered dealt with.13:54:05
@cat:feline.supportCatlike theres a series of MSCs related to cleaning up the gitter mess.13:54:25
@cat:feline.supportCatWhat i mean is that if things where done differently none of these issues would ever have existed that prompted MSCs to exist to resolve the problem.13:55:03
@cat:feline.supportCatWhat i mean is that theres a series of MSCs that essentially break immutability properties that are related to it. For example the lets be able to increase max PL in a room post creation MSC and this one. 13:57:14
@morguldir:sulian.eumorguldirRedacted or Malformed Event14:05:28
@tulir:maunium.nettulir morguldir: depending on how badly, that might be a security@element.io thing 14:08:10
@cat:feline.supportCatFuck that reminds me i have still to file my issue about Redacting profile info being borky in atleast one Element version publicly as security cleared it for public filing.14:11:16
@eroc1990:matrix.orgeroc1990 set a profile picture.14:14:12
@morguldir:sulian.eumorguldir
In reply to @tulir:maunium.net
morguldir: depending on how badly, that might be a security@element.io thing
oh you're right
14:25:58
@morguldir:sulian.eumorguldirthanks for pointing it out, sent 🙏14:38:26
27 May 2024
@fheese:element.ioFlorian Heese changed their display name from Florian Heese // away to Florian Heese.07:11:36
@davideg:element.ioDavide changed their display name from Davide[away] to Davide.07:54:19

There are no newer messages yet.


Back to Room ListRoom Version: 5