https://github.com/joshjarabek7/solstice-accounts-backend

https://github.com/joshjarabek7/solstice-accounts-backend

Last synced: 9 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/joshjarabek7/solstice-accounts-backend
• Owner: JoshJarabek7
• Created: 2024-06-26T04:10:04.000Z (8 months ago)
• Default Branch: main
• Last Pushed: 2024-06-26T04:28:33.000Z (8 months ago)
• Last Synced: 2024-06-26T05:35:37.557Z (8 months ago)
• Language: Python
• Size: 50.8 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
Early Works for Solstice Account Backend Service

Since we are going to be an Apple Exclusive app, we will exclusively use Sign In with Apple ID to simplify things, and we can take advantage of MongoDB Realm to keep data local to the device, keep their data in-sync, and offload a lot of risk to MongoDB, rather than accessing it on our servers.

## Planning

Features/Services:

- Users should not be able to see accounts they've blocked and users who have them blocked shouldn't be able to see them

- Authentication with Apple Sign-In JWT

- User Deactivation

- User Deletion

- Retrieval of User's Data when requested

- Banning Users

- Reporting of Users

- Suspension

- Notifications

- User Search by handle

- Background Checks and ID Verification

Determine what can and cannot be done on the device with MongoDB Realm.

We should strive to keep most data and compute local to the user's device.

Only try to collect the minimal amount of data required to make the application work.

Keep other backend services to a minimal in terms of their MongoDB classes.

This will keep the bson ID for that user, which can be passed to the other services.

Separate Account from Profile to keep PII to a minimum.

Hopefully we might not even really need to build this ourselves by and instead use MongoDB functions.