XMPP doesn't provide for much in the way of security unless you are using strictly private single servers.

Once your contacts are scattered across multiple jabber servers all bets are off as far as security.
Your server will almost surely end up forwarding your message to other servers insecurely.

XMPP also struggles with binary blobs (images) etc.

So authors can't possibly want to provide for their children or grandchildren?

Having known many older authors, I assure you that's not true.

If copyright expired at death, what incentive would P.G. Wodehouse or SF Grandmaster Jack Williamson (both of whom continued writing into their late eighties or early nineties) have had?

Which is why I support fixed-length copyright terms, rather than life or life-plus.

Authors and Inventors

Copyright (c) ,
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

        Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
        Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
        Neither the name of the nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

No. Its github, where hosting those repos like that requires you concede to freeing the code.

Obfuscation pretty much never has a place in security.

Unless "pretty much never has a place in security" actually means "has a critical place in security", please tell me your usernames, passwords, crypto keys, host addresses, VPN token parameters, etc. Also your bank account numbers as well as your bank routing number.

Secrets == obfuscation. Crypto == obfuscation.