{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiazxb7xan4wvsysymot5ouu4njflhloxhexqcsysrq7hexcdquxcy",
    "uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3mfh44xkr6na2"
  },
  "path": "/post/46160542",
  "publishedAt": "2026-02-22T10:39:35.000Z",
  "site": "https://programming.dev",
  "tags": [
    "Opensource",
    "xoron",
    "0 comments",
    "github.com/positive-intentions/signal-protocol",
    "github.com/signalapp/libsignal"
  ],
  "textContent": "submitted by xoron to opensource\n7 points | 0 comments\n\nId like to share my implementation of the signal protocol that i use in my messaging app. The implementation is in rust and compiles to WASM for browser-based usage.\n\ngithub.com/positive-intentions/signal-protocol\n\nIts far from finished and im not sure when its a good time to share it, but i think its reasonable now.\n\nThe aim is for it to align with the official implementation (github.com/signalapp/libsignal). That version was not used because my use case required client side browser-based functionality and i struggled to achieve that in the official one where javascript is used but is targeting nodejs.\n\nThere are other nuances to my approach like using module federation, which led to me moving away from the official version.\n\nI am using AI to do this so its important to be clear that im not asking you to audit or review my vibecoded project. While i have made attempts to create things like audits and formal-proof verication, i know better than to trust AI when it tells me its working correctly.\n\nSharing it now if there is feedback about the implementation. Anything i may be over looking? Feel free to reach out for clarity on any details.",
  "title": "Signal Protocol in Javascript for Browsers"
}