for the Tigase client for ios is it possible to know if a connection is disconnected ?
bhaveshsguptahas left
kikuchiyohas left
nykb
is there a way to know MessageSendingClient client is disconnected ?
bhaveshsguptahas joined
Wojtek
@nykb in the settings account has a dot indicating whether it's connected or not (or connecting);
Wojtekhas left
sonnyhas joined
nykb
okay i found out the XMPPClient has a variable called state "SocketConnector.State"
nykb
with this im able to know the state of the client
pep.
Wojtek, why do you use @ btw? Is that a bug in your client?
nykb
i was looking for this because , sometimes i try to send messages , but it does not send , i suspected the client was disconnected
nykb
is it possible to keep the client connected as long at the application is active ?
nykb
i mean the XMPPClient for swift iOS
nykb
is it possible to keep it connected ?
pulkomandyhas left
pulkomandyhas joined
kikuchiyohas joined
sonnyhas left
bhaveshsguptahas left
bhaveshsguptahas joined
pulkomandyhas left
pulkomandyhas joined
nykbhas left
kikuchiyohas left
kikuchiyohas joined
bhaveshsguptahas left
Wojtekhas joined
bhaveshsguptahas joined
Wojtek
pep. I guess "force of habit" of mentioning someone from "other places"
pep.
ok
Wojtek
nykb - it should stay connected as long as it is active (in the foreground, limitation of the iOS). once you push it to the background the os will kill the connection after a short delay
Wojtek
pep. also - BeagleIM gives you a dropdown with nicknames after typing "@" so it's easier to mention someone
pep.
Why do you need to send @ on the wire?
pulkomandyhas left
pulkomandyhas joined
Zash
Converse.js does this too but doesn't include the @ in the actual message
pep. does it actually matter if it's there or not?
kikuchiyohas left
pep.
It does. You're putting arbitrary semantics into body
jonas’
Wojtek, most importantly, some clients will not match in that case✎
pep.
Of course it's not the same nick anymore :)
jonas’
Wojtek, most importantly, some clients will not match for a highlight in that case ✏
Zash
And it's kinda annoying
pep.
You'd expect other clients to recognize that arbitrary character and continue operating as if it wasn't there
pep.
-> arbitrary semantics
Wojtek
Zash - why it's annoying?
pep.
Why is "not being highlighted" annoying? (when it's actually aimed at you)
pep.
Is that a question
Wojtek
I'd argue that "@" shouldn't be treated as part of word (in the same sense that it's not part of localpart, domain or resource name)
Wojtek
I thought that "including 'a" per se was annoying, not the consequences
Wojtek
my bad
jonas’
Wojtek, but I can have an `@` in my nickname
Link Mauve
Wojtek, the rules for highlight matching are very ad-hoc, no two clients will do the same.
jonas’
what if I’m called @pep.?
Link Mauve
\b or \< in a regex might match the beginning of @pep.’s nick, or not, I’m not sure.
bhaveshsguptahas left
Link Mauve
If I wrote about “somethingpep.” you may or may not highlight pep. for instance.
Link Mauve
Highlighting is still very much not a solved problem.
bhaveshsguptahas joined
Wojtek
Link Mauve - I know, Beagle for example highlights "sequences of characters" which is convenient in a way (if someone tries to add some sort of flexion to the nickname for example)
Zash
What if the attention element had a target nickname for muc
Link Mauve
References do fix that on the sending end, so that for instance when you press Tab to complete “p” into “pep.” it adds said metadata for pep.’s client to understand that this specific chunk of codepoints is a hl to him.
Link Mauve
Converse.js does use it the way you’re used to, you type @p, enter, and it puts “@pep.” in the input field but on the wire sends “pep.” with a reference attached.
Link Mauve
Wojtek, right, some languages do declinate names (including nicknames) and using \bnick\b would be very bad in that case.
Wojtek
jonas’ that's quite tricky
Wojtek
but as stated - this is very much not solved problem