release clarification

[profanity-im]

release clarification

[jubalh]

Yes that is the goal. We plan to port the good stuff from libmesode to libstrophe. And then deprecate libmesode.
People have limited time though.

[pasis]

The only difference with libstrophe is that libmesode provides callback to review certificate and manually trust it or not. Libstrophe doesn't ask user anything and validates (or rejects) certificates automatically depending on provided flags.

After implementing something similar in libstrophe we can deprecate libmesode completely. The thing is that I would like to see a similar feature in libstrophe which would be implemented properly: supported (or at least works correctly with a stub) in all TLS modules, new API is in the same style as the rest API, etc.

libstrophe is a general-purpose library, we need to provide features that would work for all applications, not break existing users and be backward-compatible.

[Neustradamus]

@jubalh: Always diff at this time?
What is missing yet?

[pasis]

@Neustradamus, there is no development in libmesode. All releases are just merges with libstrophe. There are a lot of conflicts, so merging process consumes much time. With code refactoring commit it will be near to impossible to support libmesode. Personally I would vote not to support it and backport only recent bugfixes without new features.

[Neustradamus]

It is not possible to import features in libstrophe?
Comparaison of the old libstrophe code and libmesode at a moment...

[DebXWoody]

Go for it? What is the good stuff?

[jubalh]

@DebXWoody what do you mean?

What needs to be done is to backport the features that are in libmesode but not in libstrophe back into libstrophe.
You can talk to @pasis if you want to help.

[jubalh]

libmesode got deprecated, see 8e5c8b3