rainbownapkin/canopy
1
0
Fork 0
Code Issues 2 Pull requests Actions Packages Projects Releases Wiki Activity

Create back-end status tracking #177

New issue
Closed
opened 2025-09-16 20:30:33 -04:00 by rainbownapkin · 3 comments
rainbownapkin commented 2025-09-16 20:30:33 -04:00 (Migrated from gitlab.com)
Copy link

Add RAM-backed map of current status of each user.

Each entry in the map should be keyed by username, and contain an array of all connectedUser objects across all channels.

Item should be unset once all connected users have been disconnected.

This should both improve performance, and also enable features like visible status on profile pages.

Add RAM-backed map of current status of each user. Each entry in the map should be keyed by username, and contain an array of all connectedUser objects across all channels. Item should be unset once all connected users have been disconnected. This should both improve performance, and also enable features like visible status on profile pages.
rainbownapkin commented 2025-09-16 20:30:33 -04:00 (Migrated from gitlab.com)
Copy link

added #176 as parent issue

added #176 as parent issue
rainbownapkin commented 2025-09-16 21:20:58 -04:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
rainbownapkin (Migrated from gitlab.com) closed this issue 2025-09-17 20:22:34 -04:00
rainbownapkin commented 2025-09-17 20:22:35 -04:00 (Migrated from gitlab.com)
Copy link

Created back-end status tracking map of connectedUser objects: 6222535c47

Created back-end status tracking map of connectedUser objects: 6222535c4790d37b263407a43e950e011179e394
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dev
0.4-indev-hotfix-3
0.4-indev-hotfix-2
0.4-indev-hotfix-1
0.4-indev
0.3-indev-hotfix-1
0.3-indev
verbose-queue
0.2-indev
0.1-indev
No results found.
Labels
Clear labels   
Bug

   
Cleanup/Refactor

   
Core Feature

   
Documentation

   
Feature

   
Performance Improvement

   
Security Improvement

   
UX/Accessibility

   
Unreproducable Bug
No labels
Bug
Cleanup/Refactor
Core Feature
Documentation
Feature
Performance Improvement
Security Improvement
UX/Accessibility
Unreproducable Bug
Milestone
Clear milestone
No items
No milestone
Canopy v0.4-Indev
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: rainbownapkin/canopy#177
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?