the-draupnir-project/Draupnir

Warn explicitly in the chat when `experimentalRustCrypto` is enabled and the kinds of bugs they might experience

Open

#1,110 opened on Apr 29, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)TypeScript (28 forks)auto 404
L3 Some UsersP3 Outrageous / Cannot continue to or start to useT6 Crasheasily incrementedgood first issue

Repository metrics

Stars
 (239 stars)
PR merge metrics
 (PR metrics pending)

Description

Since we're probably unlikely to make a decision to remove it entirely we should write this. And we should remove it from the default.yml config or whatever

See https://github.com/the-draupnir-project/Draupnir/issues/1104 among other issues

We should also tell them about why an encrypted management room won't hide what commands are being used and also that for server acl, ban sync, and protections that dont' scan content, draupnir works fine in encrypted rooms without the encrypted device.

Contributor guide

Research direction
Locate the existing configuration handling and warning message mechanism in the codebase, then add a warning when experimentalRustCrypto is enabled and remove it from the default.yml config.
Tech stack
typescript
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75