- 6 Posts
- 7 Comments
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX 1.3-beta — reactions, blocking, and notification privacyEnglish
3·21 days agoMessages are stored on the server only until the recipient comes online. Once they connect, a 30-second timer starts — after that the message is permanently deleted from the server. There’s no copy left server-side after that point. Since private chats use E2EE, the server only ever sees ciphertext anyway. After delivery, messages exist only locally on both devices. If you want no local record either, you can delete the conversation manually from within the app.
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX: self-hosted messenger with LAN mode and E2EE — an indie project storyEnglish
3·2 months agoWrite to @support directly in ONYX, using the search field, and we’ll discuss this in detail.

wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX: self-hosted messenger with LAN mode and E2EE — an indie project storyEnglish
42·2 months agothat’s a great idea, I’ll consider adding it in one of the upcoming updates.
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX: self-hosted messenger with LAN mode and E2EE — an indie project storyEnglish
99·2 months agoFair skepticism, but no - I used AI for the English translation of my post, since I’m not a native speaker.
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX: self-hosted messenger with LAN mode and E2EE — an indie project storyEnglish
23·2 months agoJust to clarify — E2EE in ONYX is only for private chats. Groups and channels (both built-in and self-hosted) don’t have E2EE, which is actually closer to your point — for groups it’s a deliberate tradeoff for simplicity and reliable sync. So you’re right, for that use case TLS is enough.
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX: self-hosted messenger with LAN mode and E2EE — an indie project storyEnglish
317·2 months agoFair point! Yes, Claude was used as a coding assistant throughout the project. That said, every single line went through strict manual review — nothing was blindly copy-pasted into the codebase. All architectural decisions, the crypto stack choices, and the overall design are my own. Claude helped with boilerplate and speeding things up, but the project is not “vibe-coded”.

This update actually wouldn’t have happened without your suggestion — you pushed me to finally implement it. Thank you!