#Push Target Handling

11 messages · Page 1 of 1 (latest)

blazing kettle
#

Appwrite handles push targets as user based. The biggest issue the situation where to cant trigger delete_push_target like user deletes an app and reinstalls. Currently am handling push_targets by assigning ID same as session ID so when user logs out i also delete his/her push. But when user deletes an app then i cant delete that push, so the database will be full of targets with expired tokens. Also i cant assign userID to because a user can login to multiple devices. Whats the best way to handle push targets?

#

My suggestion is to allow us to assign target_id to UDID. also allow overrides of targets where by if user logouts and logins with another account. then the target is overriden to a new user account.

blazing kettle
#

@forest wyvern i planned to ask this in office hours but i missed it.

blazing kettle
#

the reason i asked is the about the isssue of handling followers and folllowing with topics. i subscribe to a topic with the target then if i login in two devices then one device will be following and another not following the topic

forest wyvern
forest wyvern
blazing kettle
#

for example if you treat topics as channel for users to follow. if the user follows a certain channel. he/she expects to be following it even on the second device that he/ she has logged in