This is odd. Anyone on #mastoadmim notice that Android notifications via @Tusky are really delayed? About 15 mins after I had the Chrome notification the app notification happened. I don't even know where to start debugging this issue.
@xrobau @Tusky i think tusky defaults to polling if no UnifiedPush provider is available. Install ntfy on your phone and relogin to your account in Tusky.
@bitpirate @Tusky it looks like it should be using the Google push API in this case, as I'm on a standard pixel 7, and there's no warning about push services not being available. I'm trying to figure out if there's something wrong on my instances, or if the tusky endpoint is overloaded
@bitpirate @Tusky yeah I saw that, but that was 8 months ago, and since then it's been implied that it will use the Google push API. Maybe I misread.
@xrobau @bitpirate yeah, no. No Google Push API.
We're using unified push. But you need to set up stuff on your side too.
@Tusky @bitpirate my side as on the server? Or the client? I'm trying to figure out the best UX for clients, and only just noticed the delay.