Go to file
strawberry 9a3866afff return `M_INVALID_PARAM` instead of `M_BAD_JSON` for bad room aliases
Signed-off-by: strawberry <strawberry@puppygock.gay>
2024-01-17 14:26:26 -05:00
.gitea Change license to Apache-2.0 2020-10-18 13:47:52 +02:00
.github chore(deps): update actions/cache action to v4 2024-01-17 12:04:47 -05:00
.gitlab/merge_request_templates remove old gitlab stuff and issue templates 2023-12-20 21:46:54 -05:00
.vscode remove deprecated recommended vscode extension 2023-12-20 23:03:18 -05:00
complement the great persy, sled, and heed purge (and bump MSRV to 1.74.1) 2024-01-14 20:55:56 -05:00
debian the great persy, sled, and heed purge (and bump MSRV to 1.74.1) 2024-01-14 20:55:56 -05:00
docker the great persy, sled, and heed purge (and bump MSRV to 1.74.1) 2024-01-14 20:55:56 -05:00
nix only listen on IPv6 since that's what conduit does 2023-07-21 12:12:37 -07:00
src return `M_INVALID_PARAM` instead of `M_BAD_JSON` for bad room aliases 2024-01-17 14:26:26 -05:00
tests Complement improvements 2022-10-17 18:41:45 +02:00
.dockerignore fix(ci): Only build in (remote host) docker and switch to glibc 2022-11-02 12:12:48 +01:00
.envrc add shebang to .envrc 2023-12-24 01:56:56 -05:00
.gitignore bump various deps (except for the HTTP libs currently), use my 2023-11-25 11:36:55 -05:00
.gitlab-ci.yml oops forgot to bump 1.70.0 in flake and gitlab dockerfile 2024-01-14 20:55:56 -05:00
APPSERVICES.md Pre-0.3 doc adjustments 2022-02-04 18:05:24 +01:00
CODE_OF_CONDUCT.md remove nightly only feature, small housekeeping stuff 2023-11-29 21:59:18 -05:00
Cargo.lock actually we can remove loole (for now) and crossbeam 2024-01-17 14:26:26 -05:00
Cargo.toml fix blocks_in_conditions clippy lint 2024-01-17 14:26:26 -05:00
Cross.toml add my Cross config 2023-09-13 21:46:06 -04:00
DEPLOY.md the great persy, sled, and heed purge (and bump MSRV to 1.74.1) 2024-01-14 20:55:56 -05:00
DIFFERENCES.md add missing ban reason to ban events 2024-01-14 20:55:56 -05:00
Dockerfile oops forgot to bump 1.70.0 in flake and gitlab dockerfile 2024-01-14 20:55:56 -05:00
LICENSE remove nightly only feature, small housekeeping stuff 2023-11-29 21:59:18 -05:00
README.md revamp README.md to conduwuit 2024-01-06 14:51:08 -05:00
TURN.md Move appservice howto into whats-next; again, rename placeholder TURN url 2022-02-04 21:11:50 +01:00
conduit-example.toml the great persy, sled, and heed purge (and bump MSRV to 1.74.1) 2024-01-14 20:55:56 -05:00
engage.toml use engage for ci 2023-12-20 21:46:54 -05:00
flake.lock update rocksdb to 8.10.0 2024-01-14 20:55:56 -05:00
flake.nix update rocksdb to 8.10.0 2024-01-14 20:55:56 -05:00
renovate.json chore: Configure Renovate (#15) 2023-12-20 22:26:36 -05:00
rustfmt.toml chore: get rid of warnings 2021-03-18 18:33:43 +01:00

README.md

conduwuit

a well maintained fork of Conduit

What is Matrix?

Matrix is an open network for secure and decentralized communication. Users from every Matrix homeserver can chat with users from all other Matrix servers. You can even use bridges (also called Matrix appservices) to communicate with users outside of Matrix, like a community on Discord.

What is the goal?

An efficient Matrix homeserver that's easy to set up and just works. You can install it on a mini-computer like the Raspberry Pi to host Matrix for your family, friends or company.

Can I try it out?

There are no public conduwuit homeservers available, however conduwuit is incredibly simple to install. It's just a binary, a config file, and a database path.

What is the current status?

conduwuit is a fork of Conduit which is in beta, meaning you can join and participate in most Matrix rooms, but not all features are supported and you might run into bugs from time to time. conduwuit attempts to fix and improve the majority of upstream Conduit bugs or UX issues that are taking too long to be resolved, or unnecessary Matrix or developer politics halting simple things from being merged or fixed, and general inactivity.

There are still a few nice to have features missing that some users may notice:

  • Outgoing read receipts and typing indicators (receiving works)

What's different about your fork than upstream Conduit?

See DIFFERENCES.md

Why does this fork exist? Why don't you contribute back upstream?

I have tried, but:

  • unnecessary Matrix / developer politics
  • bikeshedding unnecessary or irrelevant things in MRs
  • disagreement with how the upstream project is maintained including the codebase
  • infinitely broken CI/CD and no interest in fixing it or improving it
  • upstream maintainer inactivity
  • questionable community members
  • lack of MR reviews or issue triaging and no upstream maintainer interest in receiving help
  • severe bugs, including denial of service and other likely vulnerabilities, not being merged due to things mentioned above
  • no interest in adding co-maintainers to help out

are what are keeping me from contributing. If the state of the upstream project improves, I'm willing to start contributing again. As is, I think if folks want a more polished and well-kept version of Conduit, conduwuit exists for that.

How can I deploy my own?

If you want to connect an Appservice to Conduit, take a look at APPSERVICES.md.

How can I contribute?

  1. Look for an issue you would like to work on and make sure it's not assigned to other users
  2. Ask someone to assign the issue to you (comment on the issue or chat in #conduwuit:puppygock.gay)
  3. Fork the repo and work on the issue.
  4. Submit a PR (please keep contributions to the GitHub repo, main development is done here, not the GitLab repo which exists just as a mirror.)

Contact

If you run into any question, feel free to

Donate

Liberapay: https://liberapay.com/girlbossceo
Ko-fi: https://ko-fi.com/puppygock
GitHub Sponsors: https://github.com/sponsors/girlbossceo

No official conduwuit logo exists. Repo and Matrix room picture is from bran (<3).