You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Write apps/backend/docs/concepts-caching.md for lib/conversationCache.ts and the Redis cache keys in lib/redis.ts: what is cached, the key format, the TTL, and every path that invalidates it.
Acceptance criteria:
Documents each cache key, its shape, TTL and payload
Lists every call site of invalidateConversationCaches and the event that triggers it
Explains the degraded behaviour when Redis is unavailable — the cache is an optimisation, not a correctness dependency
Documents the per-device scoping hazard: a conversation preview is device-specific, so a cache key that omitted the device would leak the wrong ciphertext to the wrong device
@blizzj has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
Hi Maintainer,
I’d really appreciate the opportunity to work on this issue. Having reviewed the acceptance criteria, I’m confident that I can submit a PR after being assigned.
Please kindly assign this issue to me.
Thank you!
@AdaBliss has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
I’d like to take this issue on. I’ll review the current implementation and relevant project guidelines first, then implement a maintainable solution with tests covering the expected behavior and edge cases
Congratulations, @AdaBliss! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @AdaBliss: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
😎 @AdaBliss: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
Activity
Awwal-dev34 commentedon Aug 29, 2026
@Awwal-dev34 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Awwal-dev34 to this issue.
blizzj commentedon Aug 29, 2026
@blizzj has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @blizzj to this issue.
AdaBliss commentedon Aug 30, 2026
@AdaBliss has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @AdaBliss to this issue.
drips-wave commentedon Aug 30, 2026
Congratulations, @AdaBliss! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @AdaBliss: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
docs(backend): add protocol negotiation, replay protection, caching, …
github-actions commentedon Aug 31, 2026
Closed by #600, merged into
dev.drips-wave commentedon Aug 31, 2026
This issue has been completed by @AdaBliss as part of the Stellar Wave Program's 8th Wave 🥳
😎 @AdaBliss: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.