reset token

[PowerChaos]

Feature Request

Problem Description

i sold a printer and forgot to remove mobileraker from the printer , so i removed it from the app as it can not make any connection ... now i get a lot of notifications and file info and stfuff that i should not receive in first place

Proposed Solution

a way to reset the token with out losing acces to all other printers , with out a fresh clean reinstall

Alternatives Considered

only send push notifications when it can really connect to the printer instead of using a token stored on the printer that never get checked if it still exist ...

as i sitenote i like to add that this is a big security risk , i know exactly how much he is printing and what he is printing,
all because the program is still sending me notifications even when i do not have acces to the printer or his location/ip
and to be fair , i expected it to stop working as soon i removed it from the app

[Clon1998]

Hi,

I acknowledge that the current situation is far from ideal and is directly linked to my decision to minimize the amount of user data stored on my backend. As a result, I currently lack information regarding the mappings between push tokens and printers.

However, I just came up with an idea to address this issue in the future without needing to store the push tokens in my backend.

I propose modifying the system to "register" a hash of the token along with the machine's UUID on my backend. By verifying this information with each request, we could potentially resolve the issue going forward.

[PowerChaos]

That would be nice,
i was just thinking about checking a hash or a simple ping request ( keep alive or refresh token ) on the app side before it dismiss notifications

so as example
User install mobileraker companion on the printer
The user setup the notification progress on there mobile , at this point they are connected somehow ( local/vpn/public )
this is the moment that a token get stored to send the push notifications and to start a timer of 24 or 48 hours ( or custom defined up to 7 days for those extreme long prints ? )

this way the app stops sending live notifications as the token automatic expire after set time unless the app got connected again to the printer to refresh/reset the token

this way there is also no need to store it on your end, and there is a safety net into it as it need to refresh the timed tokens
so with out physical acces or network acces ( like if you delete it from the mobile app ) it stops sending you those notifications, atleast after it times out ( 24H default , up to 168 hours ? )

Thank you

[Clon1998]

That would be nice,
i was just thinking about checking a hash or a simple ping request ( keep alive or refresh token ) on the app side before it dismiss notifications

so as example
User install mobileraker companion on the printer
The user setup the notification progress on there mobile , at this point they are connected somehow ( local/vpn/public )
this is the moment that a token get stored to send the push notifications and to start a timer of 24 or 48 hours ( or custom defined up to 7 days for those extreme long prints ? )

this way the app stops sending live notifications as the token automatic expire after set time unless the app got connected again to the printer to refresh/reset the token

this way there is also no need to store it on your end, and there is a safety net into it as it need to refresh the timed tokens
so with out physical acces or network acces ( like if you delete it from the mobile app ) it stops sending you those notifications, atleast after it times out ( 24H default , up to 168 hours ? )

Thank you

Thank you for your suggestion. Unfortunately, I have been quite busy and haven't had the time to explore this further. I did check, and it turns out that Firebase does not allow me to reset the token, which is disappointing. The idea of physical access is a good one, but I need to evaluate it more thoroughly.