-
pep.
When doing MSN in MUC, a new resource joins, I don't advertize any of the other occupants expect other resources of the same account? possibly with @jid set to be more explicit, or not at all?✎ -
MattJ
pep., correct (possibly)
-
MattJ
If you do the multiple <item> thing, you may want to update their presence to anyone who is permitted to see that
-
pep.
When doing MSN in MUC, a new resource joins, I don't advertize to any of the other occupants expect other resources of the same account? possibly with @jid set to be more explicit, or not at all? ✏
-
pep.
Should I ensure one of the items is placed first or sth, for clients not handling this? (It's not like MSN was declared anywhere really..). Won't a client interpret weirdly its own presence coming back to it for no reason?
-
MattJ
We haven't seen any problems from that
-
pep.
Ok
-
nicoco_
may I ask what is MSN in this context, for my own education?
-
MattJ
Multi-session nicks, or the ability to have multiple clients of your own connected to the same MUC with the same nick
-
pep.
nicoco_, https://xmpp.org/extensions/xep-0045.html#terms-general it's somewhere in there
-
MattJ
Originally this wasn't defined by XEP-0045, but as people connecting from multiple devices concurrently became more popular, it was added on
-
pep.
"Multi-session nicks are not currently defined in this document."
-
pep.
Somebody(tm) should write an informational spec someday
-
MattJ
Before this (and still sometimes today in IRC) you would see MattJ-laptop and so on
-
Ge0rG
There is also https://wiki.xmpp.org/web/Multi-Session_Nicks
-
pep.
oh
-
Ge0rG
It's also the worst-named abbreviation in XMPP land.
-
nicoco_
thanks, I figured it couldn't be 'the microsoft network' but did not manage to find the acronym's meaning
-
MattJ
Ge0rG, so you've forgiven CSI so easily?
-
nicoco_
>Somebody(tm) should write an informational spec someday please ping me when you do, I'm interested 🙂
-
pep.
Come on I'm sure we could run a contest of badly named specs
-
Ge0rG
MattJ: CSI is the second-worst name, and I'm not forgiving it because there at least we had a chance to prevent it from happening
-
MattJ
pep., we are. It's called the Standards Track ;)
-
pep.
:DD
-
pep.
We should have a "Badly named XEPs of the year" thing
-
Ge0rG
pep.: with the number of XEPs published per year, we might end up with an automatic winner
-
pep.
What's x/item@nick for exactly? I know it's used as the target for some operations (kicks, bans, etc.), but is it useful when included in a presence update for example?
-
pep.
I know some servers (prosody?) use it to reserve it, but I doubt that's the originally intended use-case
-
pep.
It could be used as a replacement of /nick maybe :P
-
MattJ
It's used for role change operations, because moderators aren't allowed to see real JIDs of occupants
-
pep.
Ah right
-
MattJ
Prosody's behaviour is because some clients were also using it it for affiliation changes
-
MattJ
and the side-effect of including both is that it gets treated as an affiliation change, but with the specified nick as the nick to be reserved for that affiliated JID
-
MattJ
(that's (too vaguely) defined here: https://xmpp.org/extensions/xep-0045.html#grantmember )
-
pep.
“if a nick is provided, that nick becomes the user's default nick in the room if that functionality is supported by the implementation” heh
-
pep.
Is MUC-PM support required btw
-
pep.
One could return service-unavailable error message right?
-
pep.
Even though I'd want some other way to designate people that isn't realjids.. I might have another look at unique-id and try to do everything with that
-
MattJ
The XEP at least allows it to be disabled, so sure. Just implement it in a way that it cannot be enabled :)
-
pep.
Ah wait, there's a config option already right