mellium
/
legacy
7
0
Fork 0
Code Issues Pull Requests Releases Activity
Legacy XMPP functionality that has been pulled out of the main xmpp module or is still useful but generally should be avoided if at all possible. https://mellium.im/legacy/
43 Commits 1 Branch 0 Tags 72 KiB
Go 100%
Go to file
Sam Whited 2de8dec130
ci/woodpecker/push/dco Pipeline was successful Details
ci/woodpecker/push/test Pipeline was successful Details
ci/woodpecker/push/validate Pipeline failed Details
all: bump deps 
Signed-off-by: Sam Whited <sam@samwhited.com>
 		2023-01-12 09:15:26 -05:00
.woodpecker all: update Go language version to 1.18 2022-08-14 20:42:07 -04:00
bookmarks bookmarks: add canonical import comment 2022-07-11 08:04:31 -04:00
compress compress: update package for new module 2022-03-17 08:47:42 -04:00
privatexml privatexml: fix missing error handling 2022-03-20 09:03:10 -04:00
LICENSE legacy: add readme and license 2022-03-17 08:45:24 -04:00
README.md all: update readme with new Codeberg links 2022-07-11 08:24:53 -04:00
go.mod all: bump deps 2023-01-12 09:15:26 -05:00
go.sum all: bump deps 2023-01-12 09:15:26 -05:00

README.md

Legacy XMPP

Issue Tracker Docs Chat License

The legacy module contains XMPP related functionality that may still be useful for backwards compatibility, but has been deprecated or obsoleted by other functionality. This module should be used selectively and with caution as many of its packages may have security weaknesses, compatibility issues, or other major problems.

To use it in your project, import it (or any of its packages) like so:

import mellium.im/legacy

If you'd like to contribute to the project, see CONTRIBUTING.md. As a general rule, no new functionality will be added to this package, this is just a place to put existing functionality that previously existed in mellium.im/xmpp that wasn't quite ready to be completely retired.

Compatibility

This module does not follow any sort of backwards compatibility promise. We will attempt to follow semver and keep the API backwards compatible on a best-effort basis, but changes may be made at any time to fix bugs or make the API easier to use.

License

The package may be used under the terms of the BSD 2-Clause License a copy of which may be found in the file "LICENSE".

Unless you explicitly state otherwise, any contribution submitted for inclusion in the work by you shall be licensed as above, without any additional terms or conditions.