moparisthebestI hope not, that's a crappy slack-ism
Martinmoparisthebest: The beagle dev suggested me to tell my clients devs to also notify on @user. Because his client adds an @ in front which results in not being notified of that mention.
MartinIs there any XEP where mentions are defined? MUC XEP?
pulkomandyhas left
MartinWojtek: Are you the one from Beagle? Do you know any client supporting those @mentions? Afair none of all the XMPP clients I tested notifies you on them.
MartinGe0rG: Is this used in the wild? I thought clients are just parsing the messages. Also this won't work in public MUCs as you don't know the JID of the mentioned person.
Ge0rGMartin: of course not
MartinHa, there's an XEP for that (that nobody uses). :D
moparisthebestI'm sure some clients look for any old substring of your name, instead of ones surrounded by whitespace or :,
Ge0rGsome users with short nicknames dislike that
lovetoxin gajim you can define a list of words which you get notified on
lovetoxso its in theory supported, though not by default
moparisthebestwe had an unfortunate user in our IRC channel once who chose the nickname 'z' and his client would highlight him constantly if we said zapped or yowza or anything like that
moparisthebestso we abused him a lot :)
Link MauveMartin, yes, Converse.js does support it, sending and receiving.
pep.Martin, I suggest you suggest the Beagle devs not to do it this way :x
Link MauveHow it works is that when you press @ it presents you with a list of users in the room, you pick one cycling with tab, and on sending it replaces @Martin with Martin in the body, and adds a reference.
Link MauveRace condition happens when the user left in-between these two operations.
pep.What converse does makes a bit more sense already
Link MauveSure.
serge90has joined
MartinNot sure if I can convince them.
Link MauveYou can point them to Converse, the only other XMPP client (to my knowledge) to use @nicks.
Link MauveAnd which thankfully doesn’t put the @ on the wire.
Link MauveSo that it integrates properly with the ecosystem.
serge90has left
serge90has joined
serge90has left
serge90has joined
serge90has left
pulkomandyhas left
pulkomandyhas joined
serge90has joined
waqashas left
waqashas joined
pulkomandyhas left
pulkomandyhas joined
jonas’Link Mauve, how does that cause a race condition?
jonas’is it stupid and only processes the @-mention when the message is sent instead of when it’s composed? :(
waqashas left
waqashas joined
Link MauveYes.
Link MauveWas this not clear in my description, “on sending it replaces @Martin with Martin in the body, and adds a reference.”?
pulkomandyhas left
pulkomandyhas joined
pep.Also there's no buffer and if you start replying to somebody who lives the room you can't autocomplete anymore either
pep.Also there's no buffer and if you start replying to somebody who leaves the room you can't autocomplete anymore either
MartinSame with profanity.
pep.well with profanity (or other clients that don't do @things), you can just write the nickname
pep.With converse it would also add the reference, that it doesn't do in this case
moparisthebestI've unfortunately been forced to use MS teams lately, it interprets formatting as you type, but with a bit of delay, and replaces it in-line
MartinAh they use what Georg linked earlier.
MattJConverse can work with the list of room members though, which is handy and counters all the issues of people leaving
moparisthebestwhich means if you type :) and hit enter, it'll actually send text :) then put a real smiley in your text box after the message was sent
moparisthebestsame with code blocks and everything else, it's TERRIBLE to work with
moparisthebestlike if I want to send code `bla` I have to put a space after the last ` and wait a few seconds for it to be replaced, if I hit enter too fast, it doesn't do any formatting
moparisthebestseriously who would implement something this bad
MartinSounds terrible indeed.
Link MauveMattJ, I should finish my module which automatically promotes regulars to members, and demote them once they aren’t present for a long time.
Link MauveBut I’ve been trying to generalise that for statistics too, so it isn’t finished yet.
goffihas joined
pulkomandyhas left
MattJYes please
pulkomandyhas joined
etahas left
etahas joined
etahas left
etahas joined
pulkomandyhas left
etahas left
pulkomandyhas joined
etahas joined
lovetoxhas left
lovetoxhas joined
WojtekHi Martin, yes - I'm from Tigase/Beagle. As I explained in the linked issue - we decided to go with `@` as it's states the intention of mentioning someone more explicitly (and it helps with avoiding abuse as moparisthebest mentiond with guy nicknamed `z`); there is yet another argument for that, and this is somewhat related to push notifications -- in Tigase you can currently "register" your nickname and then you would get notifications for intentional mentions in MUC (instead of including even random correlations)
Current argument for not sendongi `@` over wire boils down to basically: other clients don't do it and we don't like it (mostly because of habbit and because other client don't do it)
There is xep-0372 but as Ge0rG said - nobody uses it; and as yo mendioned - it may be tricky to use in MUC (though, I think that maybe using FullJID with room+nick would work)
Link MauveWojtek, no, the main argument against @ is that encoding intent in the body is a terrible idea, see the current LC on XEP-0393.
Wojtekyet everyone assumes that a string should be assume as 'mention' - which is IMHO equally as bad
MartinI am only a user so I don't know what is the best solution but having two ways of mentions is a bad UX because I wasn't notified of Beagle users mentioning me.
lovetoxhas left
WojtekMartin out of curiosity - which client do you use?
pep.Wojtek, what Link Mauve says
Link MauveWojtek, do you expect BeagleIM to make the entire ecosystem to change, or do you plan on keeping it to controlled environments where it only has to interact with itself?
Link MauveOtherwise, as you can see from me hling you, most people using other clients will use the traditional way, not the Slack way.
MartinWojtek: Regularly I use profanity and Conversations. Sometimes also Dino and Gajim.
Wojtek@Link Mauve it's not 'slack way' - afair there were prior usage (twitter comes to mind I guess, mastodon uses it the same way); A lot of IM's actually uses `@` as a way to mention…
There is no XEP that mandates that mentions should come in a plaintext form - it's just an assumption, which is quite bad (because as shown it breaks when suddenly someone doesn't follow something that's not written)
Link MauveMaybe Someone™ should write a XEP about the current usage.
Link MauveI said Slack because AFAIK it’s the one which popularised @ mentions for IM, but yes that probably comes from Twitter.
Link MauveOr from perl, dunno. :D
sonnyhas left
sonnyhas joined
WojtekLink Mauve do we really want to standardise current usage though? when there is 0372? :-)
Link MauveI don’t believe so, but as historical why not.
sonnyhas left
sonnyhas joined
pep.Wojtek, the point is wire format vs input format
pep.The rest, the specific sigil etc., doesn't actually matter :)
kikuchiyohas left
goffihas left
pulkomandyI can see the French hate the way the @ key is unconvenient for their azerty keyboards :o)
MartinWhere is the @ on French keyboard layout?
debaclehas left
debaclehas joined
alexishas joined
xeckshas left
xeckshas joined
MattJWojtek: use 372. Converse supports it, and I'm happily using it for sending notifications from MUCs
MattJ(Prosody)
MattJBased on registered nicks, as it sounds like you are too
MattJHaving another compatible client would be great :)
Link MauveMartin, AltGr+0.
MattJ(I have been asked why other clients don't generate the notifications, and I had to defend the sorry state of the XMPP ecosystem... let's fix that!)
Link MauveMattJ, +1!
etahas left
etahas joined
pulkomandyhas left
pulkomandyhas joined
pulkomandyhas left
pulkomandyhas joined
etahas left
etahas joined
debaclehas left
sonnyhas left
sonnyhas joined
waqashas left
waqashas joined
sonnyhas left
sonnyhas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
paulhas left
sonnyhas left
sonnyhas joined
wurstsalathas left
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
xeckshas left
xeckshas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
Alexhas left
Alexhas joined
waqashas left
waqashas joined
waqashas left
sonnyhas left
waqashas joined
sonnyhas joined
sonnyhas left
sonnyhas joined
waqashas left
waqashas joined
Wojtekwe are leaning towards 0372, but funnily enough, @Link Mauve - we do hope that "the entire ecosystem to change" by adopting it as well ;-)
Link MauveMe too. :)
Link MauveBut this is an actual improvement, while using @ like you’re doing is just preventing my client from hl’ing me, and doesn’t have any benefit other than familiarity for Slack users.