spacebarchat / spacebarchat/server
[Feature] Connections Part 2
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.2k
- Forks
- 323
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 4
Description
Part 2 is the followup to #1009, bringing new features like Linked Roles, new core connection services, and new addon services.
- Core Connection Services
- PayPal
- Steam (uses old OID 2.0, ew)
- TikTok
- eBay
- Crunchyroll
- Xbox (Activity status)
- League of Legends
- Contacts
- User Routes
- Connection Routes
- Update Connection
- Update Status Visibility
- Update Metadata Visibility
- Update Connection
- Connection Metadata
- Steam
- PayPal
- TikTok
- eBay
- Linked Roles
- Get Configuration (GET
/guilds/:guild_id/roles/:role_id/connections/configuration) - Update Configuration (PUT
/guilds/:guild_id/roles/:role_id/connections/configuration) - Application Role Connection Metadata
- Get Configuration (GET
- State timeout?
- Two Way Links
Addon Services:
- Multi instance connections (ex multiple Fosscord instances)
- Mastodon
- Revolt.chat
- OpenStreetMap
- Skype
Other TODOs:
- Response code should be checked against all 400 codes instead of just 401, and 400 (Refresh error responses)
-
connection_idurl parameter should be renamed toprovider_idto match Discord and the existing error messages - Create custom app to handle /connections route, to allow connecting to different FC/Mastodon/etc instances?
Making this an issue since theres obv no pr for part 2 yet
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
Start by reading the scope in this issue and the referenced follow-up issue #1009, then use the linked Discord API documentation for the listed routes, services, and metadata. No repository files or tests are named, and the work is complete only when the selected checklist items and related TODOs are implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100