Alby Hub Events table
Open
needs planning
- Dominant language
- TypeScript
- Stars
- 280
- Forks
- 132
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 11
Description
This could be a nice feature to have (not just for node events as per https://github.com/getAlby/hub/issues/675) but needs planning as would be a brand new part of the architecture and see what the other possibilities / potential of this feature could be and how it improves user experience with Alby Hub.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the related node-events discussion in issue #675 and the existing Alby Hub architecture. Define the event types, scope, and user-experience goals before implementation; done means the project has an agreed design and implementation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100