Please excuse for my lack of knowledge if this topic has been discuss before. I have a couple of questions that relates to spreading the use of XMPP:
0. Does the user of XMPP has to know about XMPP in order to use it for instant messaging?
1. If Electronic Mail have a URI shorten down to `mailto:`, why does XMPP which is supposed to be the standard for Instant Messaging is shorten down to `xmpp:`?
2. Can we change it? If we can't change it since it has already been implemented in many software, can we add an alias ?
3. If it is possible to add such an alias, can we go for something with less syllables that can be easily and quickly pronouced in every human language?
My suggestion is adding an alias for XMPP as `chatto:` or even just `chat:`.
But I don't know enough about XMPP and standards and where else it is used so…
mhhas left
mhhas joined
goffihas left
goffihas joined
Matthewhas left
uhoreghas left
homebeachhas left
Half-Shothas left
Half-Shothas joined
Matthewhas joined
homebeachhas joined
uhoreghas joined
Trunghas left
MSavoritias (fae,ve)has left
MSavoritias (fae,ve)has joined
Trunghas joined
Vidakhas joined
Tim Rhas joined
mhhas left
pep.
0. A user certainly doesn't have to know about the protocol. There's many examples of that in the wild already. Mostly closed silos. 1. I don't know. I guess because there was no other name for it at the time (or rather, they didn't want to reuse 'jabber' which had just been trademark'd?) 2. Can we change it? Maybe? We can certainly have software understand multiple schemes for the same protocol. 3. That'll depend on individual projects to implement it, but there can be a push from the community for it.
https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml
mjk
Trung: ditching `xmpp:` definitely wouldn't fly, but adding things is always possible. that'd probably be IETF's business rather than XSF, though (disclaimer: I'm affiliated with neither).
strictly speaking, the `mailto:` URI scheme sticks out like a sore thumb, because it describes an intent, which URI schemes, in general, arent. `chat:` is another matter tho
Steve Killehas joined
pep.
I personally don't think the scheme matters at all. People use https:// just fine
pep.
Or don't use it, rather
MSavoritias (fae,ve)
Yeah. I dont think many people are seeing mailto: links anyways
mhhas joined
MSavoritias (fae,ve)
Just a button most of the time
antranigvhas left
mjk
they're just sufficiently trained :) http(s) is _everywhere_, to the point of people thinking "link == https"
pep.
Browsers are making lots of effort not to show these also
pep.
And one can type in a url without the scheme and it'll land. Worst case, google will find it for you..
Andrzejhas joined
antranigvhas joined
antranigvhas left
antranigvhas joined
mathijshas left
mathijshas joined
Zash
meanwhile, http: and https:
karoshihas joined
Trung
Sure. http: and http: and even ws: and wss: has no problem because browsers are all following this standard. Meanwhile, mailto:user@domain.org and xmpp:user@domain.org looks very similar but use completely different software and protocol and user experience.
Trung
Crawler can't get to this link I think: https://chat.trung.fun/dang-ky?t=62MUmG9zF21_lIvSPSWr0sgH
Mario Sabatinohas left
Mario Sabatinohas joined
Steve Killehas left
mdosch
My wife and my parents don't know what xmpp is and are using it, so users don't need to know what protocol they are using. But I agree that a snappy name for the eco system is missing nowadays. Previously Jabber was used…
Trung
if in the invite link above, I change `xmpp:user@domain.org` to `im:user@domain.org` or someth along that line, will there be some sort of police force that comes knocking on my door?
Menel
You can do what you want there
Menel
But clients won't understand it
mjk
im: is a different uri scheme tho (the syntax is different, afaik)
mjk
and yea, most importantly, it's not associated with xmpp clients :)
Trung
yeh that's why i'm throwing the topic here Menel. 😁
pep.
If you want to do this by the rules, follow the iana link I sent above
pep.
Otherwise nothing prevents clients from experimenting
Menel
If you write a clients, or change them to react on that, then if will work for your contacts that use your specific client.
Menel
I wouldn't mind if conversations would try to react on that..
mjk
wait a minute... https://www.iana.org/assignments/uri-schemes/perm/jabber
Menel
Would be even nicer if some think like thunderbird or Firefox would react on xmpp:
mjk
Menel: as long as the scheme is registered in the system, browsers in general try to handle it (at least Firefox)✎
mjk
Menel: as long as the scheme is registered in the system, browsers in general try to pass it on (at least Firefox) ✏
Trung
ok I understand. Thank you everybody. I'll leave <a href="xmpp:user@domain.org">` as it is and will change the content to `im:`.
Menel
Uh, so I've some file somewehe where I can enter that? Good to know
*IM*has joined
Trung
sorry the link is in Vietnamese, I don't know enough Lua to mess about with the module yet.
jonas’
Trung, fwiw, that may be confusing though, if people based on your (visual) example try to use im: and it doesn't work
jonas’
so rather stay with the standard I guess
mjk
Menel: on freedesktop systems, you just register and app as a handler of, say, x-scheme-handler/xmpp MIME type. on windows, you add `xmpp` somewhere into registry✎
mhhas left
mjk
Menel: on freedesktop systems, you just register an app as a handler of, say, x-scheme-handler/xmpp MIME type. on windows, you add `xmpp` somewhere into registry ✏
mhhas joined
pep.
The thing with schemes other than https? is that they don't matter anyway as long as web is the norm. It's almost impossible to leave a browser with another scheme. Chrome filters xmpp, and many others
pep.
(Or rather it allows quite a small set)
Trung
yeah I know it will cause confusion that's why we might want to discuss it and add it to the book before start implementation. But honestly, xmpp: means gibberish in human language doesn't matter which country you are coming from. People won't spread gibberish if they can't even pronouce the thing properly.
Zash
Changing the scheme now would just cause problems.
MSavoritias (fae,ve)
Also jabber is worse imo
gooyahas joined
Zash
I also don't see what the problem is.
MSavoritias (fae,ve)
I wouldnt mention either
pep.
I say the scheme doesn't matter. As I said above, "http" is used every day and nobody complains. It's invisible to most and people call that "web" anyway
mjk
pep.: for me, chromium asks if I wanna open the link with the external app (and says its name), no filtering 🤷️
krauqhas left
Zash
`<a href="xmpp:alice@example.com">💬️ chat with Alice</a>`
the problem is user@domain.org means emails to most people.
pep.
Looks like Chrome does.. but not on android? And other things also don't support it
pep.
Woah, matrix: even is supported.. :/
Trung
and most people now relate user@domain.org to user@gmail.com or user@outlook.com
Trung
s/relate/have/
mjk
pep.: Navigator.registerProtocolHandler is a different thing from what I was talking about, it allows registering http urls to handle schemes in-browser
Menel
Hide it as a browser button seems a good choice
pep.
Yeah it's handy for movim, libervia, etc.
pep.
But you're right
Menel
mjk: thanks. Will add it there
Link Mauve
mjk, please not xdg-open, that shell script doesn’t implement XDG specs, you should instead use a proper tool like `gio open`.
mjk
Menel: it should probably be there already. :) when you install, e.g., Gajim, Firefox will start asking if you wanna open the xmpp link in Gajim
mjk
Link Mauve: tell that to Google, I guess
Link Mauve
I don’t speak much with Google.
mjk
idfk why does it ask me to open xmpp with xdg-open
mjk
Link Mauve: me neither, so, local patching it is!.. oh wait, I don't have a computer that can build it, nvm
Kevhas joined
Kevhas left
Kevhas joined
goffihas left
goffihas joined
SteveFhas joined
goffihas left
goffihas joined
MSavoritias (fae,ve)
> pep.:
> Woah, matrix: even is supported.. :/
Makes sense matrix paid them to move to madric and they wanted to support it
*IM*has left
inkyhas left
mjk
madric :D
MSavoritias (fae,ve)
XD oups
mjk
I thought it was intentional
MSavoritias (fae,ve)
No :D
Danielhas left
xnamedhas left
massiveboxhas left
massiveboxhas joined
inkyhas joined
pasdesushihas joined
karoshihas left
Trung
I found `im:` here: https://en.wikipedia.org/wiki/List_of_URI_schemes
mhhas left
Trung
it also has `xmpp:` in the note section which myself am now confused lol
massiveboxhas left
massiveboxhas joined
mhhas joined
eevvoorhas left
mjk
that note _is_ confusing
kurisuhas left
wurstsalat
> At the time this document was written, numerous instant messaging protocols were in use, and little interoperability between services based on these protocols has been achieved. (2004)
And history is currently repeating itself, as the IETF is trying to spin up a new IM interoperability initiative
Danielhas joined
Zash
all this has happened before, and all will happen again, and again, and again
p42ityhas joined
Kevhas left
florettahas left
florettahas joined
Kevhas joined
p42ityhas left
Kevhas left
Kevhas joined
karoshihas joined
belovehas left
catchyhas left
catchyhas joined
Trung
ok… for now I'll leave my inivte page as it is then. =]]]]
mjk
hopefully, this time is a bit different, given the current regulational background
belovehas joined
Danielhas left
sonnyhas left
sonnyhas joined
mjk
> presentity
RFCian is a weird language
belovehas left
LNJhas left
mjkhas left
Matthewhas left
uhoreghas left
homebeachhas left
Half-Shothas left
mjkhas joined
Half-Shothas joined
Matthewhas joined
homebeachhas joined
uhoreghas joined
MattJ
mjk: hopefully, indeed. I'm not holding my breath 🙂
MattJ
There is no indication of the regulations mandating any specific tech or standard, so currently as long as the giants publish some form of accessible (but proprietary) API, they can comply
qyhas left
MattJ
And there is no indication that any of them are interested in whatever the IETF comes up with
Alexhas left
mjk
yeah. the MIMI authors seem to merely express the hope themselves :D
MattJ
So it could easily go the way of CPIM, regulation or not
Alexhas joined
belovehas joined
Danielhas joined
mhhas left
florettahas left
belovehas left
mhhas joined
kurisuhas joined
inkyhas left
belovehas joined
karoshihas left
karoshihas joined
Kevhas left
Kevhas joined
Kevhas left
belovehas left
eevvoorhas joined
inkyhas joined
Zashhas left
LNJhas joined
Zashhas joined
wladmishas left
wladmishas joined
wladmishas left
xnamedhas joined
wladmishas joined
wladmishas left
wladmishas joined
Kevhas joined
Kevhas left
Kevhas joined
Kevhas left
Kevhas joined
belovehas joined
qyhas joined
Matthewhas left
uhoreghas left
homebeachhas left
Half-Shothas left
Half-Shothas joined
Matthewhas joined
homebeachhas joined
uhoreghas joined
sbachhas left
sbachhas joined
sbachhas left
sbachhas joined
inkyhas left
sbachhas left
sbachhas joined
SteveFhas left
karoshihas left
LNJhas left
Kevhas left
belovehas left
Andrzejhas left
antranigvhas left
Trung
https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml ← is the official page and does not have `chat:` right?
antranigvhas joined
Alexhas left
Alexhas joined
belovehas joined
mjk
Trung: correct
antranigvhas left
konstantinoshas left
konstantinoshas joined
LNJhas joined
florettahas joined
belovehas left
wladmishas left
wladmishas joined
wladmishas left
wladmishas joined
SteveFhas joined
SteveFhas left
wladmishas left
wladmishas joined
wladmishas left
wladmishas joined
Trung
> There is no indication of the regulations mandating any specific tech or standard, so currently as long as the giants publish some form of accessible (but proprietary) API, they can comply
Speed of implementation is more important that what the ‘official’ is publishing, correct?
belovehas joined
Zash
Important for capturing the market, or important in a correctness sense?
mathijshas left
mathijshas joined
karoshihas joined
belovehas left
Trung
hmmm………………
Menelhas left
Menelhas joined
neoxhas left
Menelhas left
Menelhas joined
papatutuwawahas joined
belovehas joined
Trung
https://chat.trung.fun/dang-ky?t=62MUmG9zF21_lIvSPSWr0sgH ← This is the same link as before. The `<a href=""` is still `xmpp:`, but I am now going to display `chat:`. I am now an ‘outlaw’ and I welcome all developers of clients and servers to join force.✎
Trung
https://chat.trung.fun/dang-ky?t=62MUmG9zF21_lIvSPSWr0sgH ← This is the same link as before. The `<a href=""` is still `xmpp:`, but I am now going to display `chat:`. I am now an ‘outlaw’ and I welcome all service providers and developers of clients and servers to join force. ✏
inkyhas joined
inkyhas left
Trung
(Zash, quick and dirty win the race.)
inkyhas joined
Andrzejhas joined
neoxhas joined
konstantinoshas left
konstantinoshas joined
konstantinoshas left
konstantinoshas joined
Vaulorhas left
Menelhas left
Menelhas joined
belovehas left
Menelhas left
Menelhas joined
Menelhas left
Menelhas joined
Menelhas left
Menelhas joined
belovehas joined
belovehas left
qyhas left
qyhas joined
Matthewhas left
uhoreghas left
homebeachhas left
Half-Shothas left
Half-Shothas joined
Matthewhas joined
homebeachhas joined
uhoreghas joined
belovehas joined
belovehas left
massiveboxhas left
massiveboxhas joined
Vaulorhas joined
atomicwatchhas left
inkyhas left
mdoschhas left
belovehas joined
mdoschhas joined
inkyhas joined
massiveboxhas left
massiveboxhas joined
belovehas left
petrescatraianhas left
petrescatraianhas joined
Projjalhas left
Projjalhas joined
belovehas joined
inkyhas left
inkyhas joined
roothas left
roothas joined
SteveFhas joined
resolihas joined
massiveboxhas left
massiveboxhas joined
massiveboxhas left
massiveboxhas joined
qyhas left
p42ityhas joined
p42ityhas left
qyhas joined
Matthewhas left
uhoreghas left
homebeachhas left
Half-Shothas left
Half-Shothas joined
Matthewhas joined
homebeachhas joined
uhoreghas joined
archas left
archas joined
resolihas left
atomicwatchhas joined
pablohas joined
neoxhas left
karoshihas left
karoshihas joined
pablohas left
stphas joined
resolihas joined
wladmishas left
wladmishas joined
Ingolfhas left
stphas left
mathijshas left
mathijshas joined
wladmishas left
wladmishas joined
stphas joined
Sevehas left
Ray22has joined
Andrzejhas left
belovehas left
djorzhas joined
belovehas joined
belovehas left
belovehas joined
belovehas left
Andrzejhas joined
belovehas joined
belovehas left
wladmishas left
wladmishas joined
Sevehas joined
belovehas joined
singpolyma
Trung: a protocol scheme should specify the protocol, which `chat:` does not helpfully do
neshtaxmpphas left
mhhas left
neshtaxmpphas joined
Zashhas left
jcbrandhas left
belovehas left
Zashhas joined
jcbrandhas joined
resolihas left
Trunghas left
Trunghas joined
millesimushas left
mhhas joined
MSavoritias (fae,ve)has left
MSavoritias (fae,ve)has joined
Tim Rhas left
belovehas joined
Tim Rhas joined
Zash
Email is not a single protocol, plus it predates everything, so we can let it get away with mailto:
Matthewhas left
uhoreghas left
Half-Shothas left
homebeachhas left
Half-Shothas joined
Matthewhas joined
homebeachhas joined
uhoreghas joined
kryptoshas joined
kryptoshas left
Trunghas left
mhhas left
kryptoshas joined
kryptoshas left
mhhas joined
stphas left
Trunghas joined
Trunghas left
Trunghas joined
colemanhas left
colemanhas joined
singpolyma
Yeah. I think everyone regards mailto: as a mistake, but too established to change
Trung
what is `im:` then. there is also `facetime:` by the great big fuit
kryptoshas joined
kryptoshas left
Trung
I am quite happy if we can go back to `jabber:` too if that's possible. As long as you can read the damn thing to another person, i could not care less what u name it.
goffi
Hi. I'm checking XEP-0391 (Jingle Encrypted Transport), and it's not clear to me how Transport Secret (TS) is made and exchanged. XEP-0391 can't be used alone right? Thus currently, we need to use XEP-0396 with it. However it's tight to legacy version of OMEMO, is there any plan to update to TWOMEMO? Thanks. cc vanitasvitae
singpolymahas left
kryptoshas joined
kryptoshas left
SteveFhas left
vanitasvitae
Right. 391 only defines the JET security element and tells you that you need a way to protect the TS using some encryption method. 396 implements this protection using legacy OMEMO
vanitasvitae
It should be pretty straight forward to simply replace the legacy key transport element with a TWOMEMO element.
vanitasvitae
I'll add updating 396 to my todo list 😀
kryptoshas joined
kryptoshas left
vanitasvitae
(perhaps JET could be replaced altogether with SCE encrypted jingle messages though?)
vanitasvitae
Not sure what implementors of Jingle would prefer
millesimushas joined
singpolymahas joined
goffi
vanitasvitae: is any known implementation at the moment? In my case SCE is already implemented, so I'm happy if it's used.
goffi
is there any known implementation*
vanitasvitae
I'm not aware of any.
inkyhas left
vanitasvitae
I think conversations opted for something completely different? cc Daniel
sebastianhas left
sebastianhas joined
goffi
I'll go with current version for now, and make necessary changes when the updated version will be available, thanks vanitasvitae.
kryptoshas joined
kryptoshas left
mhhas left
MSavoritias (fae,ve)has left
MSavoritias (fae,ve)has joined
kryptoshas joined
kryptoshas left
Daniel
I thought we used JET. I can't check the code right now but I vaguely remembering sitting in a cafe with larma and implementing it
mhhas joined
millesimushas left
vanitasvitae
For file transfer or for AV?
vanitasvitae
I though AV used some DTLS stuff?
Daniel
File transfer
inkyhas joined
vanitasvitae
Right, I can see some JET related stuff in the JFT implementation of Conversations
kryptoshas joined
kryptoshas left
larma
I think SCE for Jingle would be great, but I don't think SCE is properly specd for IQs yet
singpolyma
SCE doesn't completely solve jingle unless you use IBB right?
millesimushas joined
vanitasvitae
larma, I agree
vanitasvitae
Since I haven't created an implementation for IQs along with the spec, I sort of "blind drafted" 😛
vanitasvitae
singpolyma, you could encrypt the whole jingle init stanza with SCE and include a plain security element in there
goffi
singpolyma: it's just used to exchange keys, transfert is done out of band as usual (only it's encrypted).
singpolyma
goffi: oh yeah, that makes sense
singpolyma
For bits of binary it could encrypt the whole thing too, though at the expense of shrinking the max file size that works
kryptoshas joined
kryptoshas left
goffi
for very small files, yes IBB could work out of the band with SCE
goffi
out of the box*
Zash
or BOB!
vanitasvitae
for the sake of genericism (is that even a word?) you probably don't want to SCE all the IBBs but instead negotiate a transport key and use that to protect the IBB session
singpolyma
You can do big files with IBB, just have to wait awhile ;)
vanitasvitae
So you can swap out IBB for another transport more easily
Zash
Server rate limits has entered the chat.
inkyhas left
goffi
vanitasvitae: right, but you then end up with 2 layers of e2ee with IBB (SCE + JET).
vanitasvitae
why?
kryptoshas joined
kryptoshas left
Zash
(+TLS!!!1)
vanitasvitae
You only SCE(Jingle Init + plain TS) and then JET(IBB)
goffi
vanitasvitae: except if I missed something, you would have to make an exception inside SCE for IBB, sure it's possible but I can imagine how this can go wrong easily.
Kevhas joined
goffi
anyway, IBB should hopefully be barely needed nowadays.
vanitasvitae
Ah now I see what you mean
singpolyma
IBB is pretty important, since it's the only thing that always works
vanitasvitae
I guess you are right. For IBB it probably makes sense to only use SCE then and use JET for out of band transports
singpolyma
It like to implement ice-tcp eventually, maybe some other stuff✎
singpolyma
I'd like to implement ice-tcp eventually, maybe some other stuff ✏
goffi
singpolyma: sure it's important to have it just in case, but the less it's used, the better.
singpolyma
goffi: I sort of agree, except that if it is used *too* little it doesn't get tested enough and starts to break in clients and then people who do need it their file transfers don't work
Ray22has left
djorzhas left
jcbrandhas left
jcbrandhas joined
kryptoshas joined
kryptoshas left
millesimushas left
millesimushas joined
antranigvhas joined
inkyhas joined
Andrzejhas left
kryptoshas joined
kryptoshas left
Menelhas left
Menelhas joined
kryptoshas joined
kryptoshas left
Menelhas left
Menelhas joined
Menelhas left
Menelhas joined
Steve Killehas joined
inkyhas left
singpolymahas left
singpolymahas joined
kryptoshas joined
kryptoshas left
Fishbowlerhas left
Fishbowlerhas joined
Steve Killehas left
kryptoshas joined
kryptoshas left
kryptoshas joined
kryptoshas left
Andrzejhas joined
inkyhas joined
kryptoshas joined
kryptoshas left
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
kryptoshas joined
kryptoshas left
florettahas left
stphas joined
Vaulorhas left
kryptoshas joined
kryptoshas left
florettahas joined
thilo.molitorhas left
singpolymahas left
thilo.molitorhas joined
kryptoshas joined
kryptoshas left
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
antranigvhas left
neshtaxmpphas left
neshtaxmpphas joined
Tobiashas left
Tobiashas joined
singpolymahas joined
Ingolfhas joined
Steve Killehas joined
Tobiashas left
Tobiashas joined
eevvoorhas left
mathijshas left
mathijshas joined
Paganinihas left
kinetikhas joined
xnamedhas left
xnamedhas joined
sbachhas left
sbachhas joined
Tim Rhas left
pablohas joined
belovehas left
belovehas joined
Steve Killehas left
kryptoshas joined
kryptoshas left
pablohas left
mathijshas left
mathijshas joined
bhavyhas left
p42ityhas joined
neshtaxmpphas left
neshtaxmpphas joined
bhavyhas joined
MSavoritias (fae,ve)has left
MSavoritias (fae,ve)has joined
Menelhas left
Menelhas joined
jgarthas joined
stphas left
marc0shas left
marc0shas joined
kryptoshas joined
kryptoshas left
neoxhas joined
sbachhas left
sbachhas joined
Menelhas left
Menelhas joined
Menelhas left
Menelhas joined
Vaulorhas joined
Tobiashas left
Tobiashas joined
Fishbowlerhas left
Fishbowlerhas joined
Syndace
(test message please ignore)
Zash
NEVER
catchyhas left
catchyhas joined
Syndace
flow, you are one of the authors of OX, right?
atomicwatchhas left
stphas joined
Syndace
If so, I'd appreciate if you took a look at this email thread: https://mail.jabber.org/pipermail/standards/2022-August/038949.html
Syndace
(and everybody else who has experience with OX too)
wladmishas left
wladmishas joined
wladmishas left
wladmishas joined
kryptoshas joined
kryptoshas left
atomicwatchhas joined
moparisthebest
Trung: may I suggest "snikket:" for a new url scheme
adiaholichas left
adiaholichas joined
colemanhas left
colemanhas joined
kryptoshas joined
kryptoshas left
Trunghas left
Trunghas joined
Trunghas left
Trunghas joined
kryptoshas joined
kryptoshas left
kryptoshas joined
kryptoshas left
kryptoshas joined
kryptoshas left
kryptoshas joined
kryptoshas left
kryptoshas joined
kryptoshas left
djorzhas joined
djorzhas left
djorzhas joined
kryptoshas joined
kryptoshas left
Andrzejhas left
Andrzejhas joined
kryptoshas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
archas left
archas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
Tobiashas left
Tobiashas joined
MSavoritias (fae,ve)has left
MSavoritias (fae,ve)has joined
Trung
hahaha why the hell not hahahahaha let's start a monolopoly
Menel
Hehe.
Only a brand
Trung
how about `xep:`?
Trung
it's not on the ‘official’ web page either.
Menel
xep: is obviously to link to a xep..
Trung
i think people can pronouce `xep:` much better than `xmpp:`
mjk
aaaa: would probably most accessible to pronounciation
Trung
yeah… i don't know man. the whole reason i register trung.fun was because i don't know which name to take and .fun was cheap so
Steve Killehas joined
papatutuwawahas left
papatutuwawahas joined
eevvoorhas joined
Tobiashas left
Tobiashas joined
jcbrandhas left
Zash
`slash-colon-at-dot:`
Trung
and then later I realized that ‘fun’ if read in Vietnamese would be ‘phân’ which means ‘shit’ in English
Steve Killehas left
Trung
too freakin late to change now =]]]]]]]]]
mjk
yes, naming is hard
moparisthebest
How often do you say url schemes out loud
moparisthebest
why yes visit my webpage at h t t p s colon forward slash forward slash w w w dot ...
singpolyma
Aech tee tee pee semicolon backslash backslash double yew double yew double yew dot
wladmishas left
wladmishas joined
Trung
not that you say it out loud, but we are providing a chat service and it is called ‘xmpp’ which is very difficult to say to another person. There are other chat services that are very easy to pass around which im sure u know already.✎
moparisthebest
Sorry do you say XMPP to other people?
Trung
not that you say it out loud all the time, but we are providing a chat service and it is called ‘xmpp’ which is very difficult to say to another person. There are other chat services that are very easy to pass around which im sure u know already. ✏
wladmishas left
wladmishas joined
moparisthebest
Do WhatsApp users say "funxmpp but now with json" to each other? Strange
xnamedhas left
moparisthebest
When people ask me for my website I don't start with "first you need a TCP stack then..."
moparisthebest
My point is you are at the wrong protocol layer here, you don't tell people "contact me on XMPP" you say "install Snikket and send me a message" or whatever, same as every other chat system
singpolyma
Trung: it's all about context. If I'm talking about the network in a general way I'll say Jabber of course. More often I'm talking about a particular app. But URIs are technical details, it's about a protocol, and the protocol is named XMPP
singpolyma
Usually users don't need to see the URI at all, they can just click a link, etc
singpolyma
Unless you're printing on a business card or something maybe?
Trung
that's exactly my point. it's confusing with mail system
Trung
that's why people will have to see the uri
singpolyma
Why? Why would you show them the URI? What is the context?
Trung
bussiness card
Trung
u just said it
singpolyma
Ah, ok. So specifically if they still do business cards where you are then yeah. Though even then I'd probably write "Jabber ID: me@example.com" not a raw URI. Put the URI in a qr code
Trung
ok so we go for `Jabber ID:`
singpolyma
For labelling a jabber id that seems like the right label :)
mhhas left
Trung
i thought we don't want to use `jabber:`
mhhas joined
singpolyma
Trung: not as a URI scheme
Trung
but mailto is not smtp
Trung
and pop and imap
moparisthebest
I don't say jabber either, that's that old Cisco tool that doesn't work well
Trung
which level are we on lol
singpolyma
Trung: mailto is a mistake that's all
singpolyma
It's a bad URI scheme
singpolyma
But we can't fix it now
Trung
puffff what is `im:`
moparisthebest
Has anyone ever seen mailto: on a business card? Not me
Trung
i have seen plenty
singpolyma
I haven't seen a business card this decade 🤷♂️
moparisthebest
Just put you@your.domain on there and people will email you or send you an XMPP message, no problem
xnamedhas joined
Trung
we can do `snikket:` if that's what u really up to mate. but mixing up mail and xmpp will cause confusion and it will be hard to spread. that's all i'm saying.
Menel
Trung: just recommend one client and tell them. About that.
And advanced and later, you can tell them that you can actually use different apps because it's an open standard.. 🤯.
One of the biggest problem is people trying all clients at once at the beginning and then saying the feature are buggy and bad..
Because they don't compare the best client with $alternative but always the worst.
catchyhas left
Trung
Snikket currently is not getting notification mate 😁 it is already confusing enough✎
Trung
Siskin currently is not getting notification mate 😁 it is already confusing enough ✏
Trung
↑ sorry ↑
Menel
For just an address stay with xmpp:...
Because you don't change https:, do you?
Menel
It's some meaningless technical link.. It's more important what it does once someone presses it
*IM*has joined
belovehas left
Trung
ok i'll just remove the uri all together and let people be confused
Menel
I honestly don't get you. But do what you want, it's your service.
singpolyma
Trung: if you want to label it for humans to read, use a human label, that's all. A URI is for computers not mostly for humans
beanhas joined
singpolyma
No label is also valid as some have said here, depending on context
Menel
Like https://search.jabber.network/rooms/1
There is no xmpp: visible..
But every link will just do that...
singpolyma
Yeah. This is why cheogram android also doesn't show just saw xmpp URIs in chats✎
singpolyma
Yeah. This is why cheogram android also doesn't show just raw xmpp URIs in chats ✏
belovehas joined
Trung
sorry i cannot be any clearer. it is confusing for people who already have emails to see that because they are used to seeing mailto: or email: attach to user@domain.org. I just want to minimize that. But that's what u guys suggesting then sure i'll remove the uri.
Kevhas left
Menel
Trung: did you Visit
> https://search.jabber.network/rooms/1
For inspiration? Maybe that would be an approach for you?
singpolyma
Trung: email: would be a label for humans, not a URI. Feel free to usefully label with the name of the thing, like Jabber ID
singpolyma
Menel: this is for printing on paper
belovehas left
Menel
Ah
Trung
the second point is it is difficult to spread the actual xmpp which at the current moment, a it-just-work user will be very confused when they are told they should try another app with the same account. because they might be confused with email apps too and it will cause more trouble.
Trung
i'm just pointing out the fact that people who doesn't understand all this uri stuff will be very freakin confused.
moparisthebest
When you read a domain name do you often think "huh is that a website or a Java package name?" I don't think that's actually a problem in practice
BASSGODhas left
p42ityhas left
moparisthebest
People don't and shouldn't understand URI things, those are for clicking, only the computer needs to understand them
Menel
One can also print a website that has a button to the chat.. https://conversations.im/j/xsf@muc.xmpp.org
Trung
there is only one type of app for website. it's call browser
flow
Syndace, could you priortize your points somehow. I have seen the email but my main problem is that I don't have the time to provide a detailed answer for each point. and I somehow don't want to answer arbitrary question✎
Trung
u get any browser u like the domain will return the website
flow
Syndace, could you priortize your points somehow? I have seen the email but my main problem is that I don't have the time to provide a detailed answer for each point. and I somehow don't want to answer arbitrary question ✏
Trung
but if u try to send mail to an xmpp account. things don't go very well…✎
Trung
but if u try to send mail to an xmpp account, things don't go very well… ✏
singpolyma
Trung: there are definitely multiple browsers with different names. Though less than there used to be I understand
Menel
There is nothing you can do about that
> but if u try to send mail to an xmpp account, things don't go very well…
moparisthebest
BRB printing business cards with:
> Firefox address: www.moparisthebest.com
wladmishas left
moparisthebest
> but if u try to send mail to an xmpp account, things don't go very well…
Why not? My email and XMPP address are the same
singpolyma
Make your jabber id and email address be the same, that's what I do
Trung
well nothing we can do really?
wladmishas joined
flow
Syndace, could you priortize your points somehow? I have seen the email but my main problem is that I don't have the time to provide a detailed answer for each point. and I somehow don't want to answer arbitrary questions ✏
Menel
No
singpolyma
Mine also works for SIP and someday AP
Trung
what if u just have an xmpp and no email
belovehas joined
singpolyma
I'm working on that
singpolyma
Soon you'll be able to set an MX and get emails over xmpp if you don't have email otherwise
Menel
Jids won't be changed to some scheme not beeing local@server
Trung
me too i would like to get rid of emails all together
Trung
but we are not there yet
colemanhas left
colemanhas joined
Menel
You'll need a text about :
"open that link in this chat app:
xmpp:....."
flow
Syndace, but if I find time I may try to answer one point at a time. so please don't be surprised that you may not get a full answer immediately. I could also offer that we have a video chat sometimes, as I believe some questions require a more interactive answer
flow
would that be an option for you?
Trung
Menel, I have that. But opening the app would mean they need to have an app first. So most will register through website then go to the clients page then figure out how they hell they can install it, then it doesn't work then download an app for email, then use whatsapp
Syndace
flow: thanks, I'll respond tomorrow
atomicwatchhas left
Syndace
Most things aren't super important - I'll just aim for compat with Gajim for noe
atomicwatchhas joined
Trung
sorry people i'll stop spamming here coz i think i made it clear enough. thanks everybody.
neshtaxmpphas left
neshtaxmpphas joined
Menel
Did you look at the snikket invite page?
It seems to do exactly that. Steer the user to the app and automate the sign up
Trung
Menel, I'm doing exactly that too. The confusion problem comes when stuff don't work.
belovehas left
Trung
if it just works, they never ever have to download a new app to their device and that is it.