reboot.reboot-codes.com / clover
Smart fursuit parts made for daily wear to help out your species dysphoria. https://clover.reboot-codes.com
Star
Fork 0
Watch
46%
Rust 39%
Dart 7%
C++ 3%
CMake 3%
TypeScript 1%
Nix <1%
CSS <1%
Swift <1%
C <1%
HTML <1%
Astro <1%
RPC <1%
JavaScript <1%
Dockerfile <1%
Kotlin <1%
Objective-C <1%
Shell <1%
183 1 0
.cargo
.github
.vscode
.zed
clover-hub
clover-hub-macros
core
docs
nix
toolbox
website
.editorconfig
.envrc
.gitattributes
.gitignore
.yarnrc.yml
Cargo.lock
Cargo.toml
deno.json
deno.lock
flake.lock
flake.nix
LICENSE.md
listeners.md
manifest.clover.json
package.json
process-compose.yaml
README.md
rust-toolchain.toml
rustfmt.toml
todo.md
tsconfig.json
README.md

C.L.O.V.E.R. #

Cybernetic Living Organism Variable Extension Regulator; Smart fursuit parts made for daily wear to help out your species dysphoria. #

Please note: Clover is Currently NOT suitible for any sort of regular use and is being developed in sparse sprints as we can find time to do so.

Features #

  • Ease of Setup: C.L.O.V.E.R.'s management software includes step by step guides on building, setup, and maintenence.
  • Focus on Security: Every event and module is verified and authenticated with an explicit trust and permission framework by the user.
  • Open Extensibility: C.L.O.V.E.R. ships with FLOSS APIs and an application management system which promotes open source projects.
  • Use Case Adaptability: While originally designed for use in Smart Fursuits, C.L.O.V.E.R. can also be used for Cosplay and Body Modifications (e.g. Cyborgs).

Usage #

The currently planned workflow is to:

  1. install a management application on an external device (like a PC, Laptop, Smartphone, or Tablet)
  2. use it to plan out required materials,
  3. connect them,
  4. and flash them to create a working instance of C.L.O.V.E.R.

Due to OS limitations, a linux/darwin desktop or a powerful android device is required for building C.L.O.V.E.R. firmwares. Otherwise, anything that supports the communication protocols configured in your instance and that has an application which speaks the management API can be used for external management/control once authenticated.

We also plan to make pre-built binaries available through a Nix cache to cut down on build times for CloverHub, C.O.R.E. components, and some supported configurations; but offline builds will always be an option.

C.L.O.V.E.R.'s primary orchestration process(es, a.k.a. CloverHub), reference API implementations (Tesseract, CarbonSteel, CarbonFiber), management software (Spanner), hardware (C.O.R.E.), and documentation are licensed under the GNU Affero General Public License version 3. CloverHub ships with or will download a copy of the repository it was built from to run C.O.R.E. and ensure AGPL compliance.

Software developed with any reference API implementations (Tesseract, CarbonSteel) may be covered under the AGPL as well. This is not legal advice, but a notice to developers who may be considering building for C.L.O.V.E.R., that you may be required to publish your source code in accordance with the AGPL if you choose to make your software publicly accessable at all.

Of course, any contributor to this repository and associated materials does not provide any guarantee of any kind, nor will take liability for actions caused by or relating to C.L.O.V.E.R.