spam pointing me to a jid on antispam.im... oh the irony (-:
Tobias
totally makes sense for spamproviders and antispam providers being in the same boat...the same works for cloundflare, who provide DDoS protection for DDoS booter sites ;)
Tobias
*booster
Tobiashas left
koyuhas joined
efrithas joined
danielhas left
danielhas joined
jerehas joined
jerehas joined
nycohas joined
nycohas joined
nicolas.veritehas left
nicolas.veritehas joined
suzyohas joined
vurpohas left
vurpohas joined
winfriedhas left
mimi89999has left
winfriedhas joined
danielhas left
danielhas joined
tim@boese-ban.dehas joined
tim@boese-ban.dehas joined
Guushas left
Guushas joined
kalkinhas left
Yagizahas joined
kalkinhas joined
Yagizahas left
Zashhas left
Zashhas left
Guushas left
Zashhas joined
Guushas joined
mimi89999has joined
koyuhas left
koyuhas joined
vurpohas left
vurpohas joined
intosihas joined
uchas left
uchas joined
uchas left
tim@boese-ban.dehas joined
tim@boese-ban.dehas joined
uchas joined
goffihas left
uchas left
sezuanhas left
uchas joined
uchas left
uchas joined
uchas left
uchas joined
Tobiashas joined
Tobiashas joined
Tobiashas joined
uchas left
uchas joined
Tobiashas joined
uchas left
uchas joined
Guushas left
Guushas joined
intosihas left
jerehas joined
Guushas left
archas left
Guushas joined
kaboomhas left
kaboomhas joined
uchas left
uchas joined
Guushas left
intosihas joined
Guushas joined
danielhas left
danielhas joined
Zashhas joined
devnullhas left
devnullhas joined
intosihas left
intosihas joined
intosihas left
vurpohas left
vurpohas joined
danielhas left
jerehas joined
vurpohas left
kaboomhas left
vurpohas joined
Guushas left
Guushas joined
danielhas left
nycohas left
nycohas joined
nicolas.veritehas left
nycohas left
nycohas joined
suzyohas left
danielhas left
suzyohas joined
suzyohas left
suzyohas joined
danielhas left
nicolas.veritehas joined
danielhas left
Guushas left
Guushas joined
blipphas left
danielhas left
danielhas left
nicolas.veritehas left
Yagizahas joined
nycohas joined
danielhas left
goffihas joined
danielhas left
nycohas joined
danielhas left
kaboomhas joined
vurpohas left
vurpohas joined
daniel
Is there a reason muc doesn't force all resources into using the same nick?
danielhas left
nicolas.veritehas joined
SamWhited
I've honestly never considered that… I kind of want to go try it just to see how things behave.
jonasw
"boom"
danielhas left
suzyohas left
daniel
the reason i'm asking is because ejabberd now supports merging and parting multi sessions nicks. and Conversations behaves pretty badly when you actually try it
daniel
and gajim is even worse
daniel
which kinda lets me believe that this is a problem that can not really be fixed
jonasw
you could fix it in conversations, couldn’t you?
SamWhited
Where "this" == "MUC"
jonasw
also, where can I test how bad pidgin breaks?
SamWhited
I'd be curious to see how other clients behave though; theoretically clients have to accept whatever NIC the server gives them, so I'd *think* this would "just work", but never underestimate client devs ability to ignore the spec :)
SamWhited
Nick, even.
daniel
jonasw, yes and i'm about to. i'm mostly done
xnyhpshas left
daniel
however that's like soo many edge cases to consider
daniel
i'm confident that *I* will get that to work somehow. but i'm not sure for like 99% of the other clients out there
daniel
in that regard forcing a clients into the same nick might actually be the smoother edge case
Zashhas joined
SamWhited
On a similar note, why don't servers let you change to an existing nick if it's also owned by another resource? Every time I try to change my nick in Conversations ot a new room I'm in from the default one it sets I get the dreaded "nick already in use", and then have to part/join to use my own nick.
SamWhited
It seems like this could work; but most of my intuitions about MUC end up being wrong, so…
jonasw
if I understand you correctly, that’s one of the thigs ejabberd now allows and it’s simply because of "we don’t implement that" when it doesn’t work
daniel
SamWhited: yes I think that's a recent thing that ejabberd allow that now.
daniel
Prosody still prevents this
blipphas left
SamWhited
Excellent; all MUCs need to switch to ejabberd. That's quite possibly my biggest annoyance when using Conversations, I'd never considered that you could fix it on the server with either of these changes.
jonasw
I think Zash mentioned that it’ll be a thing with prosody in 0.10 too
jonasw
but I might be wrong
daniel
SamWhited: the nick already in use is a server error
daniel
Meaning you have to fix it on the server side
daniel
That's not a Conversations check
SamWhited
Yah, I'd always wanted to fix the symptom, not the problem (by having a "default nick" setting in Conversations)
SamWhited
I'd still like that, because I'd still like a default nick on servers that don't force all resources to the same nick, but it would definitely be better if the error were fixed on the server too.
SamWhited
Although, even if you force all clients to the same nick, nick changes would still be break things I guess because I don't *think* there's a way to force clients to change their nick if they don't request it.
SamWhitedthinks out loud even though you've probably been through all this reasoning before because MUC is hard…
jonasw
SamWhited: xep 45, around example 51:
If the service modifies the user's nickname in accordance with local service policies, it MUST include a MUC status code of 210 in the presence stanza sent to the user. An example follows (here the service changes the nickname to all lowercase).
daniel
and now that i fixed most of the bugs in conversations i think there is a bug in ejabberd
jonasw
not clear whether that can happen out of the blue
daniel
Holger, when i'm joined with two clients A and B both using the nick x and client A changes the nick to y client B will see y join (which is correct) but client A wont see x join
daniel
which i think would be the correct behaviour...
daniel
but the fact that i'm not even sure about that doesn't speak for MUC
waqashas left
suzyohas joined
jonasw
ugh
koyuhas left
devnullhas left
devnullhas joined
Guushas left
Guushas joined
daniel
another thing you wouldn't have to worry about when forcing all clients in the same nick; if you you receive a message from another client with a different nick; does this count as a sent or as a received message?
Guushas left
Guushas joined
jonasw
ugh
jonasw
can we have MIX please.
daniel
in Conversations it actually counts as a received message; which totally confused me when testing multi session nicks; but in general this is probably expected behaviour?
kaboom
daniel: it's a received message, and: does forcing nick mean that I can no longer join a MUC with different nicks per resource?
daniel
kaboom, that whati mean by forcing the nick
kaboom
but, why?
kaboom
I use that as a feature...
daniel
kaboom, because it would get rid of *a lot* of problems
daniel
kaboom, https://xkcd.com/1172/
SamWhited
Is there any other big multi-user chat system that allows different clients using the same account to show up as different nicks? I don't know of any.
kaboom
you can already have multiple resources share a nick optionally, why force it?
SamWhited
> kaboom, because it would get rid of *a lot* of problems
kaboom
what problems?
daniel
those i just described
kaboomhas left
mimi89999has joined
kaboomhas joined
vurpohas left
vurpohas joined
waqashas joined
Manchohas left
danielhas left
danielhas left
Guushas left
moparisthebesthas joined
Zashhas joined
suzyohas left
suzyohas joined
danielhas left
danielhas left
Yagizahas left
Tobiashas joined
waqashas left
uchas left
uchas joined
Zashhas joined
kalkinhas left
moparisthebesthas joined
suzyohas left
Guushas joined
danielhas left
Guushas left
Guushas joined
SouLhas left
SouLhas joined
Valerianhas joined
mimi89999has joined
MattJ
There are a lot of corner cases on the server wide with nick sharing
MattJ
Prosody just doesn't let you change nick if you are sharing it with another resource, decided the complexity to implement it correctly wasn't worth it for the one person that might one day need this feature :)
blipphas left
daniel
MattJ: I'm sure. However I'm starting to assume that (forced) nick sharing has fewer corner cases than allowing client to merge and split their nicks
pep.has left
MattJ
I'd potentially be ok with that (forcing you to use a nick you are already using), but I don't really see a need for it
MattJ
It's probably what users want in (almost?) all cases
MattJ
The main problem is that from what I've seen, clients haven't traditionally been very good at handling server-forced nick changes
daniel
MattJ: well I'm kinda starting to assume that this will be easier for clients and maybe even for servers. Gajim for example has completely broken behavior when joining and splitting nicks
MattJ
I'm not sure why clients should have any issue with it, if the server does it correctly
Ge0rG
prosody's current behavior makes it really hard to change your nickname if you are using two clients, already.
Guushas left
MattJ
s/hard/impossible/? (unless you rejoin)
Ge0rG
MattJ: yes, unless you rejoin with all clients at the same time. it's a PITA
Guushas joined
MattJ
Oh, you want to change nick on all clients
MattJ
Yeah, we could implement it, but again, is it really useful? and then... will clients handle it?
Ge0rG
It might be a good thing to enforce the nick change over all clients as well
Ge0rG
I'm sure clients will love to receive a new nickname
MattJ
Exactly
Ge0rG
I still don't see how any part of MSN can negatively affect the client-side protocol implementation
MattJ
No, I think it can always be transparent to clients if done correctly
daniel: it's a received message if it comes from another nickname, and it's a sent message if it comes from another nickname. just ignore the non-anon-MUC JID ;)
MattJ
The server has remote code execution on the client for the following operations: nick joined, nick changed, nick left
Ge0rG
daniel: and what you described above sounds like a bug in ejabberd
MattJ
i.e. it has full control over the nick list
MattJ
in every client
Ge0rG
the thing with "sent" messages in a MUC is: how do you know if it's the one you sent right now or a message from an MSN client?
MattJ
To implement every operation for nick sharing, you have to stop thinking about room state management and code for client state management instead
Ge0rG
MattJ: you need to think about both, actually.
Ge0rG
Still, I'd love to have prosody either implement nick-split and nick-join, or to enforce a nick-change over all MSN resources
Ge0rG
the current situation is really cumbersome, especially with clients that disallow editing a MUC you are not joined to *cough*conversations*cough*
MattJ
I think enforcing nick change is likely the easiest, but I don't think many clients handle it
MattJ
Maybe we should just try that and see
Ge0rG
MattJ: +1 to that.
Ge0rG
MattJ: I'm sure it affects the same clients that fail to recognize that your nickchange was rejected by the server.
daniel
MattJ, if a client doesn't handle nick changes; how can you expect them to handle the merging and seperation of nicks properly
Ge0rG
daniel: because merge and separation are join and leave events for a different participant
Valerianhas left
Ge0rG
daniel: when you initiate a nick change, you see that change followed by a join of your other client, everybody else (including the other client) will see your new nickname joining
jonaswhas left
nicolas.veritehas joined
nicolas.veritehas left
nycohas joined
nycohas joined
danielhas left
ralphmhas left
vurpohas left
vurpohas joined
sezuanhas left
Zash
daniel: I haven't seen any client handle forced nicknames
Valerianhas joined
daniel
Zash, conversations certainly does. I haven't check others
daniel
sure that's not common?
nycohas left
Zash
daniel: all I tested broke in varying ways
nicolas.veritehas joined
nicolas.veritehas left
nycohas joined
jerehas left
jerehas joined
vurpohas left
vurpohas joined
mimi89999has joined
SamWhitedhas joined
moparisthebesthas joined
SamWhitedhas left
Valerianhas left
Valerianhas joined
Lancehas joined
Valerianhas left
Valerianhas joined
Valerianhas left
danielhas left
Valerianhas joined
Lancehas left
SamWhitedhas left
Ge0rGhas joined
Ge0rG
Zash: now I'm surprised. They break on forced nick change, but not when the server denies a change?
Zash
Nick override on join at least
Ge0rG
My client doesn't even always recognize MUC events.
Ge0rG
Something is leaking presence listeners...
goffihas left
sezuanhas left
archas joined
Lancehas joined
kaboom
Just for the record: because most clients an servers fail to properly implement nick split/join, you want to remove the feature of being present with multiple nicks completely. Ever thought of removing just the split/join and forbid nick changes when being online with multiple resources? Solves the problem without losing a totally unrelated feature...
Valerianhas left
goffihas joined
Martinhas joined
Ge0rG
kaboom: prosody forbids nick changes for MSN, and it's a usability nightmare