every app having their own websocket is a bad idea. will probably not use whitenoise if this stays true

Reply to this note

Please Login to reply.

Discussion

What's the alternative?

Pokey doesn't support marmot groups out of the box, and if would probably be nontrivial to implement that there.

unifiedpush

Better to implement something in pokey for Android if you need to connect to relays when you receive a notification

When I had unified push in amber the app couldn't connect to the internet unless the user opened the app or it still in memory

To bypass this I had to keep it running as a service all the time

Maybe it works without a always on service if you use something like work manager

Thing is that the outer marmot events only have a random and often changing group ID.

Is it possible for White Noise to give the new group IDs to Pokey in the background for listening?

nostr:nprofile1qqsxg45ph8gx0vdrvtzta6xal7v86frx6jvstsnvhrlvtehmwwh4epqpz4mhxue69uhksar5wpej7tmwdaejumr0dshsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qydhwumn8ghj7mn0wd68ytnnv968xarjv9kxjcfwvdhk6tcgnx79f

i don't think it is a good idea to reimplement everything on nostr and you're probably right, that there would probably be the need for an always on service. molly uses mollysocket for example. maybe a relay can be that always on service. i am not too deep into nostr dev to evaluate that

What are your main concerns with this approach? Is it about the phone battery draining faster?

yes, i think one app having a websocket and dealing with push notifications seems better than every app having a websocket