nostr:npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8 How we can manage pushes, if, say, apns server timeouts or unavailable? Maybe introduce local ones, with open-source push server user can install and manage, or maybe look at unified push way, etc.?

Reply to this note

Please Login to reply.

Discussion

https://github.com/KoalaSat/pokey

Do you mean something like Pokey? But in Keychat, the receiving address keeps rotating, so Pokey can’t be used.

If you’re using an Android phone, maybe we can explore how to keep Keychat running in the background.

Unfortunately, I cannot use Android version, cos API level in your project set too high, and it won’t run on Android 10. If you can lower it, just by setting minSdk in flutter config, I’m eager to participate in testing.

Nope, I’m using iOS version. But even for iOS unified push tech does exist. unifiedpush.org

We’re also keeping an eye on unifiedpush.org

But something stops you to use it as an option to fcm/apns pushes?

Other than the fact that we don’t know how stable it is, there are no other obstacles.

As for message notifications, the most challenging issue is the following.👇

nostr:nevent1qqszw62mg8zznrzq5vmuqmk3pq567mtmz057uk60waspef0tr6kmskqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgfswcp5

Suppose we can start trying? ‘Cos GrapheneOS indeed don’t have Google services.

We’ll give it a try once we’ve finished the tasks we currently have on hand.

And I think the idea of making notification server available for self-host is also good 👍🏹

Do you mean, like how users can choose their own message relay, they could also choose their own message notification server?

Yep, exactly. 🍷🏹