search

smswithoutborders / SMSwithoutborders-BE

Here is the cloud API and User management services. It is directly configurable with MySQL databases for managing users. Also provides out of the box integrations of Google OAuth end-points and Account authentication
GNU General Public License v3.0
12 stars 3 forks source link

Data should be consistent across all third parties and API DB #60

Closed sherlockwisdom closed 1 year ago

sherlockwisdom commented 1 year ago

When users access their stored platform information, the checks should not rely only on the DB's records but also the third party. This would be handy in cases where the user has revoked their tokens or have undeleted files for platforms such as telegram (failed deletion). The user data should always reflect the 'true' nature of their token with regards to SMSWithoutBorders. Improvement could be making the records on the third party match what's available in the DB. For example, if user has revoked but data available on db, user record be deleted. If user not available in DB but yet has a dir in telegram records dir/session should be deleted.

PromiseFru commented 1 year ago

Hi there,

Since there hasn't been any new activity or updates for a while now on this issue, I'll be closing it as resolved. However, if you're still running into this problem or have other relevant details to add, you can reopen this issue or open a new one.

Thanks