Upcoming Announcements & Project Information

[jevolk]

We'll soon be making announcements about the future direction of the project, including new server and room locations, and whatever other transitional materials are requested in this thread.

Due to the abrupt termination of conduwuit preceding the holiday weekend we won't have more information until next week.

Thank you for your patience.

[jaen]

Out of curiosity, does e873c77 mean you plan to stop using nix for this project? I mean, it's your project and ultimately your decision, but would be nice to know as it would certainly factor into my decision which server to use (or give up on matrix).

[jevolk]

Out of curiosity, does e873c77 mean you plan to stop using nix for this project? I mean, it's your project and ultimately your decision, but would be nice to know as it would certainly factor into my decision which server to use (or give up on matrix).

Thanks for fielding this concern Jaen, we are currently working on the new nix package to distribute tuwunel itself. That commit is on a development branch and only removes nix from the integration test suite purely on the grounds that it's just not necessary to run the test suite (only docker is). The distribution package is separate, though will likely be invoked by another target in that recipe at some point (which is not complete yet).

Again I appreciate this question and being able to hopefully provide clarification. Since this thread is not intended for discussions, feel free to open up a new issue with any follow-up concerns if necessary.

[143mailliw]

It would be nice if the documentation could be put back up in a more user-friendly format (I believe the conduwuit documentation used mdbook?). Browsing the GitHub works but it isn't ideal.

[jevolk]

Just an update, I have created two tags in the interim:

• v0.5.0 is the last (un)-official commit of conduwuit, This also contains a new fix for a bug in the spaces rooms list (courtesy @Aranjedeath).
• v0.4.7 is the old stable commit prior to the async-refactor. This is listed as a courtesy, there is no reason to run this anymore; downgrading is also not possible.

After these the project and binary has been renamed to tuwunel. The old environment variables for CONDUIT_ and CONDUWUIT_ are still recognized in addition to TUWUNEL_.

We're currently working on CI/CD to get packages and images for these tags and the upcoming post-migration release. Thanks again for everyone's patience.

[jevolk]

The warm reception of this project by everyone has been so incredibly motivating 🙏🏻 I have decided to make this post with everything I can disclose so far.

• This project is sponsored so I can maintain it full-time. 🎉
• The sponsors do not wish to have their identity disclosed until they make the announcement in conjunction with their own products in three to five weeks.
• In two or three weeks we will have the chatroom and website online. This is a business-grade community expecting professional conduct. Wear your suit, and represent the best of Matrix.
• We will continue through this week to get release packages back online and the proper amount of CI/CD infra secured. 🙏🏻
• I will then start on SSO / OIDC support #7 as the first feature-item.

[filipesmedeiros]

@jevolk to clarify, is it safe/OK to simply migrate the binary from conduwuit 0.5.0-rc4 (https://github.com/girlbossceo/conduwuit/releases/tag/v0.5.0-rc4) to tuwunel 0.5.0 (when it gets released as a binary)? Thanks!

Also, congratulations on the sponsorship! Can't wait to see who it is 👁

[jevolk]

@jevolk to clarify, is it safe/OK to simply migrate the binary from conduwuit 0.5.0-rc4 (https://github.com/girlbossceo/conduwuit/releases/tag/v0.5.0-rc4) to tuwunel 0.5.0 (when it gets released as a binary)? Thanks!

Right now the 0.5.0 tag is not renamed to tuwunel so it requires nothing; it's identical to conduwuit. When the CI/CD packaging is done (90% there!) that release/tag will require changing some names to tuwunel, but we try to maintain name-compatibility where possible (even going back to Conduit). I'll try to remember to include an insert (re: #28) with any instructions.

Also, congratulations on the sponsorship! Can't wait to see who it is 👁

Thanks! I'm probably going to make a more detailed statement about this along with a personal pledge. I've been involved in FOSS for 25 years and have witnessed companies pilfer projects, but I've also seen very positive relationships that benefit everyone. This is a deal I've thought a lot about. So while this project has taken the "Enterprise Conduit" direction it's not Commercial Conduit. There are items the sponsor wants accomplished, and if that means I have to deprioritize other features or my own ideas, that's the deal. It's still an open project and anyone can add what they need on their personal or company's dime too.

Overall this is not a new thing for the Matrix ecosystem, and I think it's very fitting for its current trajectory. It foremost brings stability to the Conduit lineage. This is the second time in as many years where users are faced with a major disruption and uncertainty. Each time it happens it's not just an inconvenience to users, it's an ugly process with "fork wars," clout-chasing, and popularity grifts that confuse users and ultimately detract from the credibility of the platform. I see this direction as a hedge against the cycle repeating, and ultimately a way to rise above many of the issues June wrote about for her departure.

[jevolk]

Good things come to those who wait! The sponsor has just provided a massive dedicated development server and I've been able to roll out a few preliminary images to DockerHub for anyone who wants to compare with the legacy conduwuit images. docker pull jevolk/tuwunel:main. There should be no migration and all configuration variables you're currently using should remain unchanged. If you encounter an error or noticeable difference from the legacy images, stop immediately and return to the prior images, then open an issue here so I can assist you.

Unfortunately I've had to expend a bunch of effort refactoring the primary release pipeline away from Nix. This has been tedious and I can't wait to get back to real programming 😇. I know it has ruffled a lot of feathers, but this is strictly business. Industry considers docker a standard with a market of qualified operators ready to go, and existing infrastructure embedded just about everywhere. I welcome any effort to continue maintaining Nix as an alternative pipeline, and the Nix package and development environment is still fully endorsed by this project.

Thank you all for your continued patience. The next time I have more to update here, the migration activities should be fully complete and the list of related issues closed-out.

[filipesmedeiros]

@jevolk will there still be "single binary" releases from now on?

[jevolk]

@jevolk will there still be "single binary" releases from now on?

@filipesmedeiros A workflow has been contributed for generating and uploading a single-binary artifact to github in addition to the other release artifacts and images. I'll be doing a dress-rehearsal for releases on my personal repo and I'll link to that for drop-in testing on #28 if it's viable. As for the aforementioned images, they are already less than half the size of the legacy images, but could indeed be further optimized, perhaps by an order of magnitude.

In any event I think I'll open #28 for other migration topics that don't warrant their own issue too, since I don't want to miss any details.

[Glandos]

Industry considers docker a standard with a market of qualified operators ready to go

OK, but a daemon written in Rust with an output as (conf_file, binary) is really easy to distribute as-is.

Right now, uncompressed size of docker image is roughly 200MB:

docker inspect -f "{{ .Size }}" docker.io/jevolk/tuwunel:main
201975276

This is more than double the size of the binary.

I know that MB are cheap this day, but we could cut in half all resources we need, it would be very welcome :)

Hello! Sorry to interrupt, but if I want to deploy tuwunel now, which docker image should I use, and what prefix should the env variables have (e.g. CONDUWUIT OR TUWUNEL) ? Thanks! :)