spacebarchat / spacebarchat/server
Forwards incompatible Discord API versions: 0, 1, 2
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.2k
- Forks
- 323
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem? Please describe.
Those API versions have some historical significance.
Describe the solution you'd like
Support for these should be added with an opt-in guild feature/DM channel flag, as the permission system and the scope of the endpoints provided to the client were significantly narrower and the translations involved are lossy in either direction.
Additional context
All those versions had been discontinued within the first months of Discord having started the service.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by mapping where API versions, guild features, DM channel flags, permissions, endpoint scopes, and translations are handled; done would mean opt-in support for versions 0, 1, and 2 while accounting for the stated lossy translations and narrower permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100