Ralph Meijer

@goffi-contrib: care to take a look at this?

@juhaz: looking into this, I seem to remember that was more or less intentional. In what circumstances would it be reasonable to have `XMPPClient` *not* use TLS?

I guess the use-case itself is not that uncommon. However, for a while now, best practice is to have interconnecting (micro)services use transport encryption. Usually for regulatory compliance and privacy...

This looks good. but the added `timeout` parameter is not tested. I think eventually this should work with the `Request` class instead of the `IQ` one, but not in this...

Thanks for this contribution! A few comments: - `notifyRetract` lacks a docstring in `wokkel.iwokkel.IPubSubService` (which would then be inherited in the docstring for `PubSubService` automatically when generating API docs. -...

@sayoun: Thanks for the patch! It would be great if you could add some unittests for the these changes, as well as a docstring for the new parameter to `XMPPClient`.

I am not aware of the earlier use, but the thing with `-7787d55d69-slj9p` at the end of topic names is not used anymore. At current count we have about 180...

What about the following? - Introduce a configuration option `ephemeral` in the `global` section. - It will have values `yes` and `no` (default). - Users will immediately have the ability...

Host labels that start with an underscore are reserved, so we can use them ourselves. They are called [automatic labels](https://learn.netdata.cloud/guides/using-host-labels#automatic-labels), and are already _special_. The others are user-defined and we...

By the way, by doing it this way, you can also use ephemerality in alerts, exports, etc.