Oddbean new post about | logout
 ## Amber 1.1.1

- Support for sending and receiving bunker requests with nip44
- Fix remember my choice not working for reject when not using content resolvers
- Improvements to edit relay screen
- Option to listen to new connections without creating new application
- Option to setup biometrics/pin

Download it with [zap.store](https://zap.store/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v1.1.1)

If you like my work consider making a [donation](https://greenart7c3.com) 
 Thank you for the updates. It seems the issue in Nostrmo indirectly fixed by this update /cc @DASHU 
 Thanks @greenart7c3 
 👀
nostr:nevent1qqszthmgt42rnv3amx39l28630xxwl2jqeuxvfqmkpv6vrwfahzm7zspzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyp6hjpmdntls5n8aa7n7ypzlyjrv0ewch33ml3452wtjx0smhl93jqcyqqqqqqgh6hn7p 
 Hi, If I connect to Amethyst with Amber, should I ad the same relays to both of them?
Thanks. 
 No 
 Thanks 👍 
 I create a new app, toggle the secret connect, then copy the bunker link to nostrudel where it's stuck at connecting, with no activity in amber. 

What am I missing?  
 I think the stable version of noStrudel doesn't support secret but next.nostrudel.ninja does 
 It works when nostrudel creates the connection link, but not when I paste it from amber...  
 Ok, now I got it to work! 
 After I delete an application, but then send a remote signing request, I still get the amber notification, but when I click accept or reject, it says no relays found.  
 The nostrmo client on Android using Amber doesn't work correctly. A popup shows indefinitely to accept a nip44 request, then Amber crash.