Post Aoi5OnO61GsG2AdVDs by 726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11@mostr.pub
 (DIR) More posts by 726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11@mostr.pub
 (DIR) Post #Aoi5OnO61GsG2AdVDs by 726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11@mostr.pub
       2024-12-04T13:41:00.000Z
       
       0 likes, 0 repeats
       
       Actually, it would be great to completely bypass NIP-46 and relays and ask Knox directly to sign an event (given an authorization token)My usecase is having Knox run as daemon in a server without pasting the nsec in a file. Then have other local services request signatures, and it needs to be fast.
       
 (DIR) Post #Aoi6N7PUhmEdVY3Qe0 by 0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd@mostr.pub
       2024-12-04T18:26:18.000Z
       
       0 likes, 0 repeats
       
       It sounds like what you want is actually an HTTP signer, not knox. I started working on something like that for the Mostr bridge a while back but never finished it. The idea being that you leverage firewalls and local network security so this thing is only accessible to internal services, then they can just POST to it from your services without authorization to get events.
       
 (DIR) Post #AoiHoCyJEb844TSV0K by 726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11@mostr.pub
       2024-12-04T18:28:28.000Z
       
       0 likes, 0 repeats
       
       This sounds much more like what I need. However, I liked the idea of having a NIP-46 bunker in case I wanted to sign events from a social client too