Come on nostr:nprofile1qqsdv8emcke7k3qqaldwv956tstu40ejg663gdsaayuuujs6pknw7jspp4mhxue69uhkummn9ekx7mqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzfmhxue69uhhqatjwpkx2urpvuhx2uc86mqq0 

 Fair criticism; we'll implement Amber support for the next Android build. 🫡  

 Thank you 

 👀 

 🙏🙏🙏 

 Go to Amber and revoke all permissions for the Foutain app, then try again... But I deleted the first account that was linked to my email before doing that, I don't know if it would work without doing that. 

 I already raw dogged it. Just have to trust them now  

 Why trust Amber with nsec? What's the diff between them and a client?  

 It's an open source app whose devs can be contacted here for any questions. Though most nostr clients are the same... But it's some kind of way to centralize your nsec and not insert it everytime in each client. Same with the browser signing extensions. 

 Have you seen the logging in with NFC card - looks cool 

 that's how they get your nsec 😂😭 

 It used to work. This is a known new bug. Another one nostr:nprofile1qqswfa547pdmqkerzf2uen3agudc67wxffjmenqpge3dylc006fppyspzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqghwaehxw309aex2mrp0yhxvmm4de6xz6tw9enx6qgkwaehxw309aex2mrp0yh8qunfd4skctnwv46qj40rct. 

 It looks like we're getting a different data structure sent back from the Amber signer since version 2.0.6 -  @greenart7c3 has anything changed on your side since this version?

It looks like when we call sign_event we are getting the npub returned in the 'event' field rather than the signed event json. 

 Yep, we changed the name signature to result. :( 

 I'm not sure I'm following - was something in the NIP-55 spec changed?

According to the NIP it seems like we should still be looking for the 'event' field - https://github.com/nostr-protocol/nips/blob/master/55.md 

 Two PRs: 
https://github.com/nostr-protocol/nips/pull/1341
https://github.com/nostr-protocol/nips/pull/1533 

 I'm returning the same data structure still.
I tested with old amber version and fountain is not working its something on their side 

 Hmmm ok that's odd as it seems to work for me on Amber 2.0.5 but not on Amber 2.0.6. Is it definitely not working for you on Amber 2.0.5? What version of Fountain are you using? 

 Tested with amber 2.0.4 and 2.0.5
Fountain 1.1.5 

 Ok so it looks like it's the content resolver method that's not working - and we do have an issue on our side where if the content resolver fails we're not properly falling back to the intent method.

I think maybe it was failing every time for you on 2.0.5 because the content resolver was never used because "remember my choice" option was not selected.

But if you install Amber 2.0.5 from a fresh state and select this option it works.

We'll get a fix out ASAP for the intent fallback - but can you think of something that might have changed with the content resolver logic? 

 How is the event you are sending to the content resolver?
I changed recently to check for id and pubkey 

 Aah ok maybe that's it then - we weren't sending the event id through originally and it was working - will update and confirm if that fixes it. 

 ok  @greenart7c3  @Vitor Pamplona  @Derek Ross  @sourcenode we have a fix for this now - new version will be available in beta later today 

 Thank you for your hard work on this. 

 I forgot about nostr:nprofile1qqsdvl5ghyne55mzdj0hzmyhvuv26fzughl7y333r9py6xdnf0uyttqppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnhd9hx2qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7ux0msg. Can we get Amber support nostr:nprofile1qqsrmd0ph8d22lxx5l2492r2sat5a63xtcr4nh0tsl2yupe8770d3rgpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny2vzgth 🥹 

 With Amber, you don't need to insert your nsec in any client. You can have 100s of them installed in your phone and your key will be safe.