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-presence-heartbeat.md explaining services/presence.ts and services/heartbeat.ts — the Redis-backed per-device/per-user presence model, TTL-based liveness, the 30s/90s heartbeat timing, and how multi-device aggregation works.
Acceptance criteria:
Explains the Redis key structure used for presence tracking (which keys exist, what each holds, TTLs)
Explains the heartbeat timing contract with the actual current interval/timeout values
Explains multi-device aggregation and the transition-broadcast behavior
Congratulations, @Samuel-21-eng! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.
🧑💻 @Samuel-21-eng: 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.
@ChukwuemekaP1 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Good day, my name is Chukwuemeka and I'd love to work on this issue.
I have experience with backend development, Redis-backed systems, and technical documentation, so I can approach this from both the implementation and documentation sides. The important part of this issue is documenting the actual liveness model rather than describing a generic presence system.
I'll trace "services/presence.ts" and "services/heartbeat.ts" to document the Redis key structure, stored values, TTL behavior, and the current 30s heartbeat/90s timeout contract. I'll also explain how presence is aggregated across multiple devices and when transition broadcasts are triggered, keeping the documentation aligned with the current implementation.
ETA: 24 hours from assignment. Looking forward to your reply!
Congratulations, @Dannyorji! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @Dannyorji: 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.
Activity
Samuel-21-eng commentedon Jul 29, 2026
@Samuel-21-eng has applied to work on this issue as part of the Stellar Wave Program's 7th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Samuel-21-eng to this issue.
drips-wave commentedon Jul 29, 2026
Congratulations, @Samuel-21-eng! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.
🧑💻 @Samuel-21-eng: 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 🌊
Confidence001Jewel-cmd commentedon Aug 27, 2026
@Confidence001Jewel-cmd 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 @Confidence001Jewel-cmd to this issue.
KHALLEY commentedon Aug 27, 2026
@KHALLEY 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 @KHALLEY to this issue.
VictorEzenma commentedon Aug 30, 2026
@VictorEzenma 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 @VictorEzenma to this issue.
DrSa7ag3 commentedon Aug 31, 2026
@DrSa7ag3 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 @DrSa7ag3 to this issue.
ChukwuemekaP1 commentedon Sep 24, 2026
@ChukwuemekaP1 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @ChukwuemekaP1 to this issue.
flare-999 commentedon Sep 28, 2026
@flare-999 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @flare-999 to this issue.
Dannyorji commentedon Sep 28, 2026
@Dannyorji has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Dannyorji to this issue.
drips-wave commentedon Sep 28, 2026
Congratulations, @Dannyorji! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @Dannyorji: 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 🌊
github-actions commentedon Oct 2, 2026
Closed by #615, merged into
dev.