Replying to Avatar Minibits

If you see them only when wallet is in active use, those are local ones, trigerred by the app itself. Check if you see the device token under the push notification switch in the Settings.

For NWC to work when Minibits is killed or backgrounded, you'd need to be able to recieve them from the server, through firebase messaging - the same way push are delivered on incoming zaps no matter the state Minibits is in.

Most android devices are supported, but there are some that don't: i.e. if you use a device that has no Google Play services installed (some chinese brands or privacy operating systems such as Graphene and similar). Those can not obtain the so called device token to which the messages are addressed.
Avatar
TheRealFaketoshi 1y ago

okay so no NWC for us Graphene users :,( Not so cypherpunk if dependend on Google play services imho

Reply to this note

Please Login to reply.

Discussion

Avatar
Minibits 1y ago

For cypherpunks there is of course a fallback - if notification permission is not granted, NWC messages keep going over the standard websocket subscription.

Now it is upon the real ones to kick their OS not to close it when the app is backgrounded and then open source that for all others.

Avatar
Max 1y ago

You can install ntfy and rely on a non-google server, even self host it.

Avatar
Minibits 1y ago

Thank you for headsup, checked ntfy, nice project. It would be unfortunately unusable for NWC use case, as the wallet do not have access to the received notifications.

In case of NWC my server subscribes to encrypted NWC commands published to minibits relay, reencrypts them with own keys and routes them to the right device based on event recepient tag. They are not shown to the user, just used as data carrier passing the commands from relays to the device.