More thoughts on the STUN server fallback question:
· This is something other #XMPP Clients just do quietly without having a big debate about it¹
· I don't think users should configure this. Anyone who knows what a STUN server is will likely switch to a server offering one.
· Treat it like channel search. On first use (call, file transfer), ask once: Use our fallback STUN server? Yes/No.
¹: github.com/dino/dino/blob/v0.4…
dino/plugins/ice/src/plugin.vala at v0.4.4 · dino/dino
Modern XMPP ("Jabber") Chat Client using GTK+/Vala - dino/dinoGitHub
Râu Cao ⚡
in reply to Daniel Gultsch • • •Gary "grim" Kramlich
in reply to Daniel Gultsch • • •with @pidgin we never officially had one nor did we default to anyone in particular. We looked at doing it for awhile but never went forward with it.
This is something we will be looking at again in the nearish future though, but we'd just be offering ip lookups and maybe udp hope punching, but we also don't want our servers to be used in illicit activity either which is where all of this becomes problematic.
Zash
in reply to Daniel Gultsch • • •rfc-editor.org/rfc/rfc1925#sec…
RFC 1925: The Twelve Networking Truths
www.rfc-editor.orgZash
in reply to Daniel Gultsch • • •Gary "grim" Kramlich
Unknown parent • • •@pidgin gotcha. Originally I was just looking at stun as well, but since that would typically be used for p2p file transfers and stuff, the idea of turn came up.
Also I was looking at using coturn as the actual service. I'll probably set that up soonish even though we're very far away from needing it in pidgin 3 but I could also point pidgin2 at it and get some basic usage monitoring on it.
Gary "grim" Kramlich
Unknown parent • • •monal-im.org
Unknown parent • • •at monal we are offering a stun and turn server as fallback (you can disable this in the settings).
So far (over the last ~12 month) we didn't have any traffic excess.
Our stun and turn server seems to be used way less than originally anticipated.