Secure Scuttlebutt client for Haiku
Go to file
Jeremy List 27874ed72c Fix bugs in MUXRPC connection cleanup 2024-01-08 11:35:51 +13:00
.github GitHub: add my Ko-Fi button 2022-06-28 17:39:03 +12:00
locales Migrate version control to git 2022-06-17 09:10:08 +12:00
src Fix bugs in MUXRPC connection cleanup 2024-01-08 11:35:51 +13:00
tests Fix issue where some SSB messages use keys that we remove 2023-11-03 14:31:15 +13:00
.clang-format Migrate version control to git 2022-06-17 09:10:08 +12:00
.gitignore Migrate version control to git 2022-06-17 09:10:08 +12:00
.haiku-format Can use `hey` to create the first message. 2022-11-15 14:12:24 +13:00
CODE_OF_CONDUCT.md Add contributor code of conduct 2022-07-27 11:21:17 +12:00
Habitat-icon Migrate version control to git 2022-06-17 09:10:08 +12:00
Habitat-icon.svg Add icon to readme (assuming it works) 2022-06-23 12:16:51 +12:00
LICENSE Migrate version control to git 2022-06-17 09:10:08 +12:00
Makefile Consolidate query usage: messages 2023-11-17 12:01:19 +13:00
README.md Adjust README to reflect catch2 package being split into parts 2023-10-27 12:55:17 +13:00

README.md

Habitat

A Secure Scuttlebutt client for Haiku.

Habitat icon

Installing Dependencies

  • Libsodium: pkgman install devel:libsodium
  • ICU: pkgman install icu66_devel
  • Catch2 (only needed for unit tests) pkgman install catch2_devel

Building

cd habitat
make

Once I have a fully functioning application I will add a build target to generate an hpkg file; and will also submit releases to [HaikuPorts](https://github.com/haikuports/haikuports/wiki/_

Unit tests

You can run unit tests with make test.

Contributing

This project's primary home is on GitLab at quickdudley/habitat and I will likely notice pull requests and issue reports sooner than on the GitHub mirror. Furthermore, before starting a pull request I advise checking GitLab for any related branches as GitHub only has main. With those said: feel free to submit pull requests and issue reports to either.

Please run haiku-format -i {src,tests}/*.{h,cpp} and commit any changes it makes before submitting pull requests, and otherwise try to stay consistent with the existing coding style. Where possible, use BString rather than std::string, and use Haiku's messaging system for communication between components. If you would like to contribute to the user interface, please discuss it with me first as I may already have detailed plans for that feature.

You are also welcome to contribute financially via https://ko-fi.com/jeremylist

To anyone who contributes in any way: thank you so much!