Comparison with tuwunel #849
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#849
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 )
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)
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.
Thanks a lot for taking the time for that extensive and helpful answer!