SamIf anyone is still interested in the old IRC channels, I created #xmpp on irc.libera.chat (the new network by most of the old Freenode maintainers).
pulkomandyhi, I'm thinking about adding something to my xmpp client to notify the user when their name is mentionned in a MUC. I found xep-0372 (I was directed there from 0452, which is related but different), but is that really used? or should I just grep the messages content for a match with the current nickname? Or is there something else in use?
flowpulkomandy, I guess doing both is sensible
flowsearching the message for the users nick is a technique used by many IRC clients, and highlighting those messages is a popular feature (at least that is my impression)
pulkomandyyes, that's how it's done in IRC. But some other chat systems have more specific requirements (like using @nickname or similar)
jonas’pulkomandy, 372 is barely used
jonas’some clients do it, but by far not all
pulkomandyI guess I can go with something IRC-style (it works for me since currently I use biboumi to talk to IRC people), but then I have many questions on how to detect a nickname (I guess it should be delimited by whitespace and maybe ':' and ',' suffix should be allowed, but I don't like guessing at these things)
pep.Making progress on something like 372 would be good (proper wire format!!1!). Matching nicknames atm is mostly in the realm of regexp in <body/> indeed (and failing at it some of the time)
MartinTrue, I get pinged everytime Georg cites some Martin Something on twitter.
Ge0rGunfollows Martin Something
Ge0rGI'm not aware of citing *that* Martin
KevI think we need to somehow make 372 support groups of people (e.g. @everyone) as well. It’s all a bit complicated.
Ge0rGMaybe it was @marcan42, aka Hector Martin?
pep.(Note that I wasn't explicitely saying I want 372, I'd just like some way of mentioning people that doesn't require searching in <body/> for hard-to-define strings)
Link Mauvehas left
Link Mauvehas joined
mathieuiKev, I kind of think stuff like @everyone & other meta-actions could fit a XEP but maybe are more of a fit for stuff like modernxmpp (e.g. do we want things like @admins, etc, and in the end it boils down to the URIs inside)
KevSurely if you want it to interop you need to have the mechanism standardised?
ZashThat's ... why we're here :)
mathieuiYes, but how much depends on the platform? e.g. could there be different meta-references for MIX and MUC, etc
KevAlthough a MUC service could detect “@everyone” in the body, and have the MUC fan-out include a reference for each person there when it sends to them, it wouldn’t allow clients to do the markup sensibly.
pulkomandysome IM systems also have a distinction of @everyone vs @all with the latter only notifying people who are not offline or away or some other kind of inactive
pulkomandywhich means the client must know what kind of notification it is
pulkomandy(or maybe it is @here vs @all, but anyway you get the idea)
mathieuito be fair having @everyone or @all on public channels is more often than not a bother and a low-effort way to generate noise
ZashYou'd probably not enable such things in public channels
ZashOr have it opt-in somehow
ZashCould do something with the MUC registration or some MIX settings node?
mathieuiextending MUC at this point always feels like walking on a lego barefoot
pulkomandymaybe this @all thing is a misfeature and it shouldn't be done at all?
Martin@mods would be cool to not have look them up and ping them manually if a spammer appears.
ZashMight have uses, but needs to be weighted against the abuse potential
Martin@mods would be cool to not have to look them up and ping them manually if a spammer appears.
pep.“Kev> Although a MUC service could detect “@everyone” in the body, and have the MUC fan-out include a reference for each person there when it sends to them, it wouldn’t allow clients to do the markup sensibly.” < I'd be careful here and include the original mention so that I can have my client ignore "@everyone" if I want it to
pep.as in, without having to parse body, still
ZashConverse.js extracts out @Nickname into additional wire protocol and sends it without '@' in the <body>
pep.pulkomandy, I agree I think
ZashThis is the way.
pep.That was some carefully planned lobbying effort (half joking)
KevIt’s horrid on public channels, and jolly useful on private ones.