continuwuation/continuwuity

Fork 34

Comparison with tuwunel #849

New issue

Closed

opened 2025-06-13 15:40:51 +00:00 by ansiwen · 4 comments

ansiwen commented

2025-06-13 15:40:51 +00:00

Thanks for taking care of conduwuit!

Would it be possible to give some insights to why there are two forks now, and what the differences are? It would be great to have some guidance on how to choose one or the other with regard to possible differences in planned features, governance, risks and so on.

Thanks again!

(I asked the same tuwunel here: https://github.com/matrix-construct/tuwunel/issues/63 )

Thanks for taking care of conduwuit! Would it be possible to give some insights to why there are two forks now, and what the differences are? It would be great to have some guidance on how to choose one or the other with regard to possible differences in planned features, governance, risks and so on. Thanks again! (I asked the same tuwunel here: https://github.com/matrix-construct/tuwunel/issues/63 )

Jade commented

2025-06-13 16:37:05 +00:00

Owner

Hi there. This is a question that's been asked a lot in the Matrix chat, and the user-facing difference has changed over time.

The main difference at the moment is that tuwunel has LDAP support, whereas we have more user-facing bug fixes and things like next-gen OIDC support in the pipeline.

Back in April, this was the answer:

(Tom Foster)

There is presently no relationship, but they're both open-source projects and do borrow commits from each other. There may be more active collaboration in the future, we'll see what happens. 🙂

It's also worth noting that this team is composed entirely of contributors to conduwuit. All of us are in the commit history over the past couple of years for various reasons, whether it's implementing the new sliding sync, rewriting the CI, or updating docs.

We're completely open to new contributors, of course, and have had new contributors already, but we've got plenty of history with this server and we're all here because we use it and wanted to keep using it for the foreseeable future. 🙂

In the time since, however, Jason has made threats against multiple members of our team, so I can't foresee any active collaboration.

tuwunel and continuwuity were both started in private shortly after the archival, although from what I understand, Jason had wanted to take conduwuit in his own direction long before then.

Behind the scenes, we have things like a security policy (I can't say much, but that is actively being used right now and tuwunel needs to have one but doesn't), code review, an active and official community chat room, detailed changelogs, etc.

Hi there. This is a question that's been asked a lot in the Matrix chat, and the user-facing difference has changed over time. The main difference at the moment is that tuwunel has LDAP support, whereas we have more user-facing bug fixes and things like [next-gen OIDC support](https://forgejo.ellis.link/continuwuation/continuwuity/pulls/810) in the pipeline. Back in April, this was the answer: (Tom Foster) > There is presently no relationship, but they're both open-source projects and do borrow commits from each other. There may be more active collaboration in the future, we'll see what happens. 🙂 > > It's also worth noting that this team is composed entirely of contributors to conduwuit. All of us are in the commit history over the past couple of years for various reasons, whether it's implementing the new sliding sync, rewriting the CI, or updating docs. > > We're completely open to new contributors, of course, and have had new contributors already, but we've got plenty of history with this server and we're all here because we use it and wanted to keep using it for the foreseeable future. 🙂 In the time since, however, Jason has made threats against multiple members of our team, so I can't foresee any active collaboration. tuwunel and continuwuity were both started in private shortly after the archival, although from what I understand, Jason had wanted to take conduwuit in his own direction long before then. Behind the scenes, we have things like a security policy (I can't say much, but that is actively being used right now and tuwunel needs to have one but doesn't), code review, an active and official community chat room, detailed changelogs, etc.

👍 6 ❤️ 4

ansiwen commented

2025-06-13 19:00:57 +00:00

Author

Thanks a lot for taking the time for that extensive and helpful answer!

nex

2025-06-14 00:06:32 +00:00

closed this issue
added the
Meta
label

Henry-Hiles referenced this issue

2025-11-03 16:31:36 +00:00

This vs Tuwunel? #1143

doasu referenced this issue

2025-11-04 19:47:37 +00:00

Migration from tuwunel #1146

doasu commented

2025-11-04 19:56:05 +00:00

Hi! It was fairly difficult for me to find this issue.

As a newcomer and potential user, I think it'd be good if this information was more accessible.

For example, it could be mentioned in the README/docs.
Pinning this issue would also make it more visible.

I could draft a documentation PR in my free time, but I think it should be written by someone with a little more background/knowhow than me.

Hi! It was fairly difficult for me to find this issue. As a newcomer and potential user, I think it'd be good if this information was more accessible. For example, it could be mentioned in the [README/docs](/continuwuation/continuwuity/src/branch/main/README.md). Pinning this issue would also make it more visible. I could draft a documentation PR in my free time, but I think it should be written by someone with a little more background/knowhow than me.

Jade commented

2025-11-04 20:15:46 +00:00

Owner

Hey, we don't keep this information pinned as it goes out of date very quickly - for example, we have LDAP support now, and there are other major changes both projects have worked on. I personally would rather spend the time on this project improving it, rather than constantly comparing our work to other people's! When we add something new, we try to mark that in our changelog.

👍 2