Logs for jdev@conference.jabber.org

Show join/part/nick changes:

[00:04:47] * joined the chat.
[00:21:59] * left the chat.
[00:29:45] * left the chat.
[01:14:56] * joined the chat.
[01:14:58] * left the chat.
[01:15:01] * left the chat.
[01:19:06] * left the chat.
[03:00:03] * joined the chat.
[03:00:03] * left the chat.
[03:00:03] * left the chat.
[03:00:03] * left the chat.
[03:00:03] * left the chat.
[03:00:03] * left the chat.
[03:00:06] * joined the chat.
[03:07:20] * joined the chat.
[04:21:57] * left the chat.
[04:33:16] * joined the chat.
[05:28:18] * joined the chat.
[05:38:45] * joined the chat.
[06:04:07] * left the chat.
[06:17:47] * joined the chat.
[06:43:22] * left the chat.
[06:51:15] * joined the chat.
[06:57:05] * left the chat.
[07:53:10] * joined the chat.
[07:53:52] * joined the chat.
[08:35:59] * joined the chat.
[08:38:56] * joined the chat.
[08:46:35] * left the chat.
[08:46:35] * left the chat.
[08:46:35] * left the chat.
[08:46:35] * left the chat.
[08:46:35] * left the chat.
[08:46:35] * left the chat.
[08:46:35] * left the chat.
[08:46:35] * joined the chat.
[09:11:01] * joined the chat.
[09:20:56] * left the chat.
[09:36:12] * joined the chat.
[09:42:22] * joined the chat.
[10:50:36] * joined the chat.
[10:50:44] * left the chat.
[10:51:31] * joined the chat.
[10:51:38] * left the chat.
[10:58:31] * joined the chat.
[10:58:58] * left the chat.
[11:27:49] * joined the chat.
[11:37:51] * left the chat.
[11:38:16] * joined the chat.
[11:48:30] * joined the chat.
[13:08:00] * joined the chat.
[13:36:50] * joined the chat.
[14:00:44] * left the chat.
[14:17:12] * left the chat.
[14:23:48] * joined the chat.
[14:48:33] * joined the chat.
[14:55:19] * joined the chat.
[14:56:15] * joined the chat.
[14:58:59] * joined the chat.
[15:00:54] * joined the chat.
[15:01:43] * joined the chat.
[15:15:45] * joined the chat.
[15:38:19] * left the chat.
[15:44:10] * left the chat.
[15:52:30] * left the chat.
[16:00:45] * joined the chat.
[17:36:25] * joined the chat.
[17:44:54] * joined the chat.
[18:04:07] * joined the chat.
[18:05:36] * left the chat.
[18:07:33] * left the chat.
[18:10:15] * joined the chat.
[18:58:59] * joined the chat.
[19:12:11] * left the chat.
[19:17:14] * joined the chat.
[19:25:51] * joined the chat.
[19:34:08] * joined the chat.
[19:34:59] <> hey all
[19:34:59] * left the chat.
[19:34:59] * left the chat.
[19:35:20] <> i'm having trouble making my conference service available to users who are not on my XMPP server... i must be missing something simple. please help? :)
[19:47:51] <> You've probably not put the SRV records in for your MUC domain.
[19:48:17] <> i definitely have not put in any SRV records except for my base domain
[19:48:48] <> would you be willing to point me to some documentation on this issue?
[19:49:06] <> RFC 6120.
[19:49:16] <> But if you just put _xmpp-server._tcp.your.muc.domain, that's what you need.
[19:49:17] <> it looks like all of my services are failing to be queried properly
[19:49:27] <> They will be unless you've got DNS set up for them.
[19:49:38] <> okay, makes sense
[19:49:46] <> Every domain that you want exposed over S2S must be exposed :)
[19:50:20] <> i thought it would be something like that, but i was having lots of trouble finding any examples or discussion on the issue :-P
[19:50:55] <> all of the discussions of SRV records i found online seemed to conclude with base domain C2S and S2S
[19:53:39] <> Kev: if i do that, though, does my server's TLS certificate need to be a wildcard certificate?
[19:54:30] <> It doesn't need to be wildcard, but you do need either: A) One certificate for all S2S that covers each of the domains in an appropriate manner or B) Offer a different cert for each domain, covering that domain.
[19:55:11] <> i was afraid of that
[19:56:09] <> if it offers an invalid certificate the S2S connection will still succeed via plain text right?
[19:56:23] <> Depends who you're federating with.
[19:56:35] <> Mostly, it'll happen over unauthenticated TLS, as things stand at the moment.
[19:56:41] <> But people are tightening up their servers these days.
[19:58:59] <> i really appreciate your help
[19:59:05] <> YW.
[20:00:08] <> would there be any conceivable reason why i would need an _xmpp-client record for any of these services?
[20:00:24] <> or just the _xmpp-server ones?
[20:00:38] <> xmpp-client tells clients where to connect. So you will only need that for IM domains.
[20:00:42] <> ok
[20:00:45] <> And on the average server, there's only one of those.
[20:01:10] <> There's nothing to stop you virtual hosting lots of IM domains, in which case you need xmpp-client for ecah.
[20:01:12] <> *each
[20:01:15] <> /me nods
[20:01:56] <> i'm sure you hear this a lot, but i'm moving to self-hosting XMPP services for my domain following Google's recent policy changes
[20:02:09] * joined the chat.
[20:14:50] * left the chat.
[20:26:41] * left the chat.
[20:34:37] * left the chat.
[21:13:40] * joined the chat.
[22:06:51] * left the chat.
[22:06:57] * joined the chat.
[22:13:24] * left the chat.
[22:36:11] * joined the chat.
[22:37:43] * left the chat.
[22:45:31] * left the chat.
[23:25:00] * left the chat.
[23:31:24] * joined the chat.
[23:36:21] * left the chat.
[23:36:23] * joined the chat.
[23:42:46] * left the chat.
[23:47:33] * left the chat.
[23:48:48] * left the chat.