Correct. And I'll also implement local broadcasting, as suggezted by nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tch2deau, the idea is that ither apps can receive inbox relay events and forget about maintaining that part on their apps.

nostr:nevent1qqsfqngcaejckfysugszde6q2u32eexmhrl2htc9ppsq6chr2xrj6qspz4mhxue69uhkummnw3ezummcw3ezuer9wchsygxdz6da3774z70z4r2f3l7rr5awpeqgyhljhz59ag6ec3z45yru4qpsgqqqqqqssjer2g 

 It also simplifies your life, since you don't need to code rendering and in-notification replies for every single event kind out there.  

 Interesting. So with local broadcasting you can send data between apps directly? 

Does this reliably work for you? Did you need to change the battery optimizer settings? I've read quite some stories about mobile OS killing your background processes to prevent battery drain etc. 😅  

 There are some tricks and Android gives you sone space. You can check how Telegram FOSS, SimpleX or Amber stays always alive in your phone. 

 Hopefully, Amber can now deleta that online code and stay completely offline, for the safety of the key.  

 Still need it for nip 46, unless I can send the event back to the push server and the push server broadcast it 

 Ohh interesting 🤔 

 Also the relays from nip 46 can change per app, it's not a fixed list of relays
We will need a way to keep track of this too 

 Need to figure out how to add those settings to pokey automatically  

 So far I'm identifying in a DB relay url and kind where it came from. So it should be fairly easy to keep track of all this. 

About sending events, what about configure Pokey to listed for external broadcasting and push received events to defined relays? 

Pokey can act as a proxy for apps. Including a built-in Tor engine that can potentially provide Tor access to any nostr app out there. 

 Yep, super common on Android. Broadcasting is protected by Android in these OS killing stuff