Egor Poderiagin

I made a pr https://github.com/xaralis/django-static-sitemaps/pull/79 > Until this gets removed you can set [STATICSITEMAPS_PING_GOOGLE](https://github.com/xaralis/django-static-sitemaps/blob/dd4dc66da78bd9f394eb8689eff3c406e3c45499/README.md?plain=1#L132) to False in your settings.py. It wont help at latest Django 5 because there's an import...

> I guess, it is good "first PR": just to wrap that import into if condition There's no needs to ping google because that endpoint is deprecated on google side....

@cordery sorry about that

Seems that `date_created` is enough for tracking expired tokens. Or @nachov99 is there specific case where that field could be helpful to have `updated_at`? Maybe better instead of bloating models...

> If you name the fields `created` and `updated` they will even be the same as TimeStampedModel from django-model-utils! But is there's a reason for that? I though: 1. there's...

If `updated_at` or any other field is required for your use-case it's possible to achieve via overridden Device model. You can check that at [docs](https://github.com/xtrinch/fcm-django?tab=readme-ov-file#using-custom-fcmdevice-model) or example how that made...

> it sounds like such a common use case @xtrinch To me `and updating this timestamp at regular intervals` sounds like typo. Regular updating timestamps on token doesn't make any...

> If FCM issues new tokens for same app instance, and one would update the token on the same device model instance, then update date would be the one to...

> Let's for example say we'd just update the device instance on a new token - always using the same device instance for all of user's tokens, then update date...

> I'm not sure what you mean by recognize. You'd basically just maintain one device instance per user - it shouldn't be that hard to securely upsert the device instance...