sipeed/picoclaw

[Feature] use vodozemac instead of libolm

Open

#3,088 opened on Jun 9, 2026

View on GitHub
 (9 comments) (2 reactions) (0 assignees)Go (4,155 forks)batch import
help wantedpriority: highstale

Repository metrics

Stars
 (28,983 stars)
PR merge metrics
 (Avg merge 2d 2h) (114 merged PRs in 30d)

Description

🎯 The Goal / Use Case

Avoid using libolm, as it is unmaintained and insecure.

💡 Proposed Solution

Use vodozemac instead of libolm. Vodozemac is the official replacement library.

🛠 Potential Implementation (Optional)

make libolm optional at compile time

🚦 Impact & Roadmap Alignment

  • This is a Core Feature
  • This is a Nice-to-Have / Enhancement
  • This aligns with the current Roadmap

🔄 Alternatives Considered

💬 Additional Context

In nixpkgs/on nixos users will either have to allow all insecure packages or specifically whitelist libolm or picoclaw to use it. This will likely scare of new users

Contributor guide

Research direction
Identify all uses of libolm in the codebase and replace them with vodozemac's API, making libolm optional at compile time via build tags.
Tech stack
go
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.
Half day
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
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70