pep.jonas’: also who would set that critical flag?
Yagizahas joined
adityaborikarhas left
adityaborikarhas joined
jubalhhas joined
xnamedhas left
LNJhas joined
Nekithas joined
jubalhhas left
debaclehas joined
krauqhas left
pdurbinhas left
jubalhhas joined
adityaborikarhas left
sezuanhas joined
krauqhas joined
adityaborikarhas joined
jubalhhas left
lovetoxhas joined
wurstsalathas joined
sezuanhas left
jcbrandhas joined
karoshihas joined
Severalphm: yes, as far as I remember dwd was the most on the loop regarding MLS
adityaborikarhas left
adityaborikarhas joined
alameyohas left
alameyohas joined
alameyohas left
Douglas Terabytehas joined
jubalhhas joined
sezuanhas joined
Douglas Terabytehas left
Steve Killehas left
alameyohas joined
Steve Killehas joined
Douglas Terabytehas joined
jubalhhas left
pdurbinhas joined
jonas’pep., sender, and the spec would mandate it
flowjonas’, I wonder what the motivation and envisioned use case behind that is?
Ge0rGflow: if you encounter an element that's marked as critical, and that you don't know, you engage the airbags and make the computer explode
Steve Killehas left
jonas’flow, it came up the other day, and I’m still playing with the thought. It *could* be useful for entities to (a) learn that the peer who received the message cannot deal with an extension and (b) for the recipient of such a message (generalized, could be an IQ or a presence or whatever) to show an indiciator, e.g. if it’s received in the context of a 1:1 conversation
Steve Killehas joined
jubalhhas joined
Dele (Mobile)has joined
Dele (Mobile)has left
pdurbinhas left
moparisthebesthas left
delehas joined
delehas left
delehas joined
delehas left
Dele (Mobile)has joined
Dele (Mobile)has left
Douglas Terabytehas left
Douglas Terabytehas joined
debaclehas left
ralphmWhat about multi-device, offline, etc. It feels a bit like the urgent flag in e-mail.
Douglas Terabytehas left
Douglas Terabytehas joined
Zashhas joined
jonas’ralphm, especially in multi-device it’s useful in replacement of feature discovery. It is kind of a "ask for forgiveness instead of permission" thing
andyhas joined
ralphmWon't every extension be marked critical?
ralphmEspecially if at some point large corps world be forced to federate using XMPP.
larmahas joined
waqashas left
jubalhhas left
ZashKind of a large shift to move away from ignoring what you don't understand
ralphmThis
ralphmIMNSHO client and feature/protocol developers should include fallback behaviour in their design.
lovetoxwhats the fallback for chatstates? :D
lovetoxi think its a failed approach to say everything needs a fallback
KevThe fallback for chatstates is not rendering chatstates.
KevThe fallback for most things is ignoring them.
lovetoxthere are things where it makes sense, and there are things where the client just ignores it
KevIn fact the majority of fallbacks are probably ignoring them.
lovetoxyeah if you consider ignoring a fallback, then im fine with it
KevIgnoring as a fallback has worked well for most things over the last 20 years.
lovetoxi agree, although im not on board for 20 years :D
KevNor me, only 18.
lovetoxregarding having a body fallback for reactions, i can see both sides, but i find it unlikely that somebody uses a legacy client for very important conversations and depends on that new clients send a body fallback
DanielSeeing how very much annoying message correction is in clients that don't support it (looking at you Dino) I can only imagine that reactions with fallbackswill be much much more annoying once a popular client has support for it and people start using it
Kevreacts to
Daniel > Seeing how very much annoying message correction is in clients that don't support it (looking at you Dino) I can only imagine that reactions with fallbackswill be much much more annoying once a popular client has support for it and people start using it
with a 👍
Kevreacts to
Daniel > Seeing how very much annoying message correction is in clients that don't support it (looking at you Dino) I can only imagine that reactions with fallbackswill be much much more annoying once a popular client has support for it and people start using it
with a ❤
KevIt's taking the piss, but it's genuinely going to be like that.
KevAnd assuming we take this as the new model, it'll continue long beyond when 'all' clients support reactions.
KevAnd, of course, you'll never be able to stop supporting old versions, or it'll start getting worse again.
Kevreacts to
Kev > It's taking the piss, but it's genuinely going to be like that.
with a 🎇
Kevreacts to
Kev > It's taking the piss, but it's genuinely going to be like that.
with a 🎆
Mikaelahas joined
mimi89999has left
mimi89999has joined
debaclehas joined
Zashreacts to /me reacts to /me reacts to /me reacts to /me with :chutulu:
Andrew Nenakhovhas joined
intosihas joined
Andrew Nenakhovhas left
Mikaelahas left
Mikaelahas joined
marc_has left
intosihas left
marc_has joined
marc_has left
marc_has joined
marc_has left
intosihas joined
marc_has joined
marc_has left
marc_has joined
marc_has left
marc_has joined
marc_has left
marc_has joined
marc_has left
marc_has joined
marc_has left
marc_has joined
marc_has left
marc_has joined
ralphmDoesn't look too bad.
marc_has left
marc_has joined
adityaborikarhas left
adityaborikarhas joined
marc_has left
marc_has joined
ralphmBut another choice for reactions could be not having a fallback body. Yes, non-supporting clients wouldn't see anything. Not sure if that's bad.
marc_has left
marc_has joined
marc_has left
marc_has joined
marc_has left
marc_has joined
marc_has left
marc_has joined
MattJHow much do we care about non-supporting clients?
marc_has left
MattJEven if a client wanted to not show the fallback, but otherwise not show reactions, that would be trivial to implement
flowI think it is. But I also believe the whole discussion is mostly pointless as we do not have any implementation experience, is heavily dependent on the personal taste and you can't forbid clients developers to add a fallback body (even if the XEP states so)
marc_has joined
flowalso I think it is trivial for clients to not show fallback bodies if the XEP is designed right
flowi.e. messages with fallback bodies will also have that special extension element
pdurbinhas joined
andrey.ghas left
adityaborikarhas left
adityaborikarhas joined
rionhas left
rionhas joined
rionhas left
ralphmIndeed
lovetoxflow, fallback is for clients that dont get updated
lovetoxa client who gets updated, just ignores evey message that has the reactions namespace
lovetoxno need for fallback
lskdjfhas joined
rionhas joined
larmaa client that gets updated can also produce the fallback body on their side for incoming messages. So if you'd want to annoy pidgin users, you could have libpurple render the reactions fallback body even if there was none transmitted on the wire 😉
pdurbinhas left
lskdjfhas left
lskdjfhas joined
lskdjfhas left
lskdjfhas joined
lskdjfhas left
lskdjfhas joined
lskdjfhas left
lskdjfhas joined
jubalhhas joined
lskdjfhas left
Neustradamushas left
Neustradamushas joined
remkohas joined
winfriedhas left
winfriedhas joined
andrey.ghas joined
jubalhhas left
Ge0rG> also I think it is trivial for clients to not show fallback bodies if the XEP is designed right
This is the minimum I will insist on. But given that, I think that annoying legacy users is less bad than silently leave them out of the conversation.
KevI think the 'legacy users' thing is fallacious.
KevIf I implement this this afternoon, everyone in here other than me is a 'legacy user', and will start getting annoyed.
jubalhhas joined
Ge0rGKev: yaxim is implementing the suggested quoting format for a year or so now, and emoji on their own line will be displayed in 6x size. Nobody complained about that so far.
KevAnd then I start developing a new extension that does similar things, so do the same, and not only is everyone else a legacy user, but there's no spec yet for them to implement. So if we believe that it would be 'annoying' to 'legacy users', that means it's annoying to current users too.
KevIf we believe it's not annoying, that's a different thing (I don't currently see how it could not be annoying, but it would be a different thing).
balu_der_baerhas joined
lskdjfhas joined
lskdjfhas left
lskdjfhas joined
lskdjfhas left
lskdjfhas joined
lskdjfhas left
lskdjfhas joined
lskdjfhas left
lskdjfhas joined
Ge0rGEven if we believe that it's annoying, we need to weigh between the right of legacy users to participate and the importance of reactions. That said, annoying them is probably a very good way to increase the pressure on the respective client authors.
jubalhhas left
ZashIt can easily backfire into "xmpp sucks" tho
KevAssuming that users have control over which clients they use is fine in the personal-user-on-the-Internal case (mostly), but not in many other environments, but you still might get interactions with other clients. I don't believe we can reasonably have a policy of "Inconvenience people who don't support feature X so that they upgrade".
ZashKev "This message is encrypted but your client sucks, switch or GTFO"
KevIdd.
Ge0rGKev: my humble opinion is that it's much more annoying to learn, by accident, after the fact, that you missed out on a part of the conversation.
Nekithas left
KevMaybe <fallback>...</fallback> is the least bad option. It's a bootstrap problem for now, but in the future we could rely on it.
ZashHow is that different from body?
Nekithas joined
KevIt doesn't get shown in the conversation flow automatically.
Ge0rGwhat would <fallback> be good for, then?
Ge0rGFor the clients that implement the XEP but decide to not show the actual reaction?
Ge0rGSo they can show the ugly <fallback> text element?
KevAssuming <fallback/> to be be a generic fallback mechanism, It'd allow a client to alert the user that there are parts of the content that they're missing.
KevWhile not flooding the log with potentially more meaningless reactions than there is message content.
ZashLike EME but generic?
KevEME?
ZashEncrypted Message Eeeeeh, what was it?
Ge0rGElement?
ZashXEP-0380: Explicit Message Encryption
KevKinda, ish.
ZashSo a generic variant of this would be "this message won't make sense unless you understand feature x"
KevOr, rather, "If you don't understand this element, the meaning is X", I think.
Ge0rGWould that be just a tag, or an actual text element?
KevBut I could imagine a client saying "This chat contains content that Swift can't render: 5000 messages containing [An emoji reaction to a previous message]" or something, where the [] has come from the <fallback/>.
Ge0rGalso it can't be inside of the non-supported element, because it's not supported, so it needs to be outside, and have the ns of the non-supported element as an attribute, because a message can contain multiple fallbacks.
Ge0rGIt's all a PITA
ZashHow is saying that better than just having some fallback "foo reacted with bar" in body?
KevZash: Because that's one message rendered in an info box somewhere outside the log, rather than 5000 messages inside the message box preventing you seeing the 1000 messages of content.
Ge0rGSpeaking of which. This MUC mostly contains irrelevant presence changes.
ZashAnd can't you do this any time you see a message with unknownnamespaces?
KevGe0rG: Yes. Imagine if your client was showing each of those to you because it didn't understand they were presence updates, it'd be insufferable.
alameyohas left
alameyohas joined
KevZash: You can warn that there's content you don't understand, but not know whether it's interesting content, or what the content represents.
Ge0rGKev: my client does understand that, but fails to aggregate / hide them in a meaningful way.
KevTalk to your client author :)
Ge0rGBecause apparently, you can't force client authors to do useful things.
KevSwift hides updates other than joins/parts, and even those it condenses in a (hopefully) smart way.
KevAnd even that I'm considering dropping.
Ge0rGIt's something that's actually useful for admins, and for when you are writing a message to somebody who just disappeared.
KevThe join/part, yes. Which is why I'm only considering dropping, rather than having actually done so :)
ZashSomeone who was recently active (sent messages) leaving is more interesting than some idling and then dropping out, right?
KevDepends entirely on the situation, I think.
Kev(But may well be)
Nekithas left
Nekithas joined
curenhas joined
pdurbinhas joined
winfriedhas left
winfriedhas joined
alameyohas left
pdurbinhas left
adityaborikarhas left
adityaborikarhas joined
winfriedhas left
winfriedhas joined
jubalhhas joined
afrogeekhas left
Ge0rGOnly show the leave if a message by that person is visible on screen. The next logical step is to add a presence indicator to that message.
Ge0rGWhich is actually something I plan to add to yaxim
Ge0rGYou could also add a notification bubble if you mention an occupant that's offline.
adityaborikarhas left
Chobbeshas joined
alameyohas joined
alameyohas left
adityaborikarhas joined
adityaborikarhas left
adityaborikarhas joined
jubalhhas left
Chobbeshas left
Chobbeshas joined
kokonoehas left
kokonoehas joined
Chobbeshas left
Chobbeshas joined
ralphmAlso want to note that MIX would handle these cases better in sense that you can choose to not subscribe or display certain streams.
adityaborikarhas left
adityaborikarhas joined
Ge0rGLike the Emoji Reactions stream?
ralphmI can see a use for an explicit fallback element. That said, I'm also curious about stanzas with more than one namespaced element.
ralphmGe0rG: I suppose that would be a very decent idea. However, then you'd have different handling for one-on-one chats.
ralphmI meant presence and join/leave above.
Alexhas left
Ge0rGYeah, got that.
Chobbeshas left
ralphmI don't think doing reactions over pubsub for one-on-one chats is a good idea. But then, having both options for MIX would suck.
rionIsn't xmpp going to fully migrate to pubsub?
ralphmSo I'm tempted to say: don't put reactions in a separate stream. Unless we have multiple streams that are delivered with regular message stanzas, and I don't like that either.
ralphmrion: going strong since 2004
ralphmEh 2002 I mean
xnamedhas joined
ralphmrion: seriously though, something like reactions is likely considered part of a conversation. Taking it "out" by using pubsub events breaks that.
Steve Killehas left
ralphmUnlike, say, a stream of code commits, the tunes you are playing, or news flashes.
ralphmIf I'd work on Slack, for example, I'd build something that takes such streams out of the channel, and move them to the side bar.
ralphmHowever, you could still start a thread from such notifications, e.g. causing the commit with comments to become embedded in the chat stream.
eevvoorhas joined
ralphmOr allow the user the choice at least.
alameyohas joined
LNJhas left
LNJhas joined
pdurbinhas joined
moparisthebesthas joined
curenhas left
alameyohas left
alameyohas joined
pep.Guus, it wasn't intended. I don't think we'll migrate the logs, meh
pep.I'll move to the new url
alameyohas left
krauqhas left
adityaborikarhas left
adityaborikarhas joined
pdurbinhas left
Steve Killehas joined
LNJhas left
LNJhas joined
krauqhas joined
alameyohas joined
Alexhas joined
sezuanhas left
Alexhas left
Alexhas joined
alameyohas left
alameyohas joined
alameyohas left
Guushas left
alameyohas joined
Guushas joined
moparisthebesthas left
moparisthebesthas joined
adityaborikarhas left
adityaborikarhas joined
winfriedhas left
winfriedhas joined
adityaborikarhas left
adityaborikarhas joined
pdurbinhas joined
Nekithas left
Nekithas joined
archas left
archas joined
kokonoehas left
kokonoehas joined
pdurbinhas left
neshtaxmpphas joined
wojtekhas joined
xnamedhas left
xnamedhas joined
wojtekhas left
Steve Killehas left
Steve Killehas joined
archas left
archas joined
patrickhas joined
krauqhas left
curenhas joined
krauqhas joined
eevvoorhas left
eevvoorhas joined
pep.All URIs in 0372 references pubsub are incorrect right? They use "?node=" and not "?;node="✎
pep.All URIs in 0372 referencing pubsub are incorrect right? They use "?node=" and not "?;node=" ✏
ralphmHmm, yes, that's wrong
pep.https://github.com/xsf/xeps/pull/810 here
Lancehas joined
pdurbinhas joined
Lancehas left
ralphmQuery parameters should be separated by semicolons, too, not ampersands.
curenhas left
pep.As in, "xmpp:fdp.shakespeare.lit?;node=fdp/submitted/stan.isode.net/accidentreport&item=ndina872be" should be "xmpp:fdp.shakespeare.lit?;node=fdp/submitted/stan.isode.net/accidentreport;item=ndina872be" ?
remkohas left
pep.will do
pdurbinhas left
pep.done
eevvoorhas left
lovetoxthat semicolon after the ? looks weird
lovetoxsure this is right?
Ge0rG0372 is weird.
Ge0rGmy gut feeling would be that the question mark is not needed, but what do I know of URIs.
Yagizahas left
debaclehas left
kokonoehas left
pdurbinhas joined
kokonoehas joined
archas left
archas joined
pdurbinhas left
lumihas joined
xnamedhas left
xnamedhas joined
waqashas joined
murabitohas left
murabitohas joined
ralphmYeah, your gut feeling is wrong. Without question mark, there's no query component.
ralphmlovetox: the position before the first semicolon is for an action. Without action, eg. when pointing to a node (or item within), that position is empty.
lovetoxah, thanks
wurstsalathas left
Douglas Terabytehas left
wurstsalathas joined
Douglas Terabytehas joined
Douglas Terabytehas left
Douglas Terabytehas joined
Douglas Terabytehas left
Nekithas left
Douglas Terabytehas joined
patrickhas left
jubalhhas joined
wurstsalathas left
wurstsalathas joined
pdurbinhas joined
neshtaxmpphas left
jubalhhas left
lovetoxhas left
pdurbinhas left
sex www.realamater.comhas joined
sex www.realamater.comwww.realamater.com
sex realamaterhas joined
sex realamaterhttps://www.realamater.com
sex realamaterralphm Alex Alex Alex Alex Alex Alex Alex
sex realamaterAlex
sex www.realamater.comhas left
sex realamaterhas left
Ge0rGhttps://twitter.com/matrixdotorg/status/1159787827636441088 why don't we have a merch shop?
j.rhas joined
j.rHello, I'm currently developing a little XMPP admin helper app for Android and now I want to make a icon... I have an Idea involving the XMPP Logo but a) I'm not sure if I can modify it so that it fits in the Icon context and b) how I have to meantion that it's based on the XMPP Logo wich is as Wikipedia tells me under MIT... (My app is btwe under GPLv3)
moparisthebesthas left
moparisthebesthas joined
andyhas left
moparisthebesthas left
moparisthebesthas joined
pep.Ge0rG, we should indeed
moparisthebesthas left
moparisthebesthas joined
wurstsalathas left
pep.j.r, re licensing, you'd just need to mention somewhere in your COPYING file or README that you're using the XMPP logo with license XYZ and put the license there.
If it's really MIT, I don't know, you'll have to copy that specific version of the license, because the copyright line is also part of the license and that makes MIT things somewhat unique
pep.Also if it's MIT then you can of course reuse/modify/etc. etc.
j.rpep., ok so I just have to find the license put it into my readme and I'm good to go?
pep.IANAL, but that's generally how it works :)
pep.Maybe it's even in the file itself. Is it an svg you got?
pep.hmm no it's not in the one from xmpp.org. Too bad
pep.hmm, CI for xmpp.org is borked. There's a PR to fix it: https://github.com/xsf/xmpp.org/pull/595, is anything blocking for it?
pep.If it's blocking on editor(s) not having time (which I'm not blaming him for), I'll rush my application for that. Where do I send my resume again?