It's been working well for me though, so I'm keeping the fork alive. If you want to try it, you'll have to build it yourself from my repo for now:
https://gitworkshop.dev/npub1k0y4eceal2zryes3azm6nsgt0r0jsa2v8zcsdf9uqxttn0jlfe9q04c9h8/grasp.t5.st/amber-up
Same app, same signer, purple icon — just with the ambersocket/UnifiedPush wake-up layer on top. Build steps are in the repo.
#amber #nostr #unifiedpush #nip46
quotingI've been using Amber a lot lately — signing commits, issues, and pull requests all the time. And because of that, I burned through my battery way faster than before I started using `ngit`. The always-on relay connection in the background was quietly eating it.
nevent1q…kvls
When I recently switched my Molly from websocket to UnifiedPush and saw the battery improvement, I thought: why not build the same thing for Amber?
So here's v1: Amber no longer needs to keep relay connections open 24/7. A tiny self-hosted Rust daemon called *ambersocket* watches relays for your kind 24133 requests and wakes the app on demand. No foreground service burning battery in the background.
The part I care about most: **ambersocket never has your keys.** It just sees that a request exists and forwards it verbatim. Only Amber on your device can decrypt (NIP-44) and sign.
To use it you need a UnifiedPush distributor (ntfy works great) + an ambersocket instance, then paste the config from Amber → Settings → UnifiedPush → copy config.
ambersocket: https://gitworkshop.dev/npub1k0y4eceal2zryes3azm6nsgt0r0jsa2v8zcsdf9uqxttn0jlfe9q04c9h8/grasp.t5.st/ambersocket
Amber: https://gitworkshop.dev/npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5/relay.ngit.dev/Amber/prs/nevent1qy28wumn8ghj7un9d3shjtnwva5hgtnyv4mqqgyzqzqlrfydhlyuccrtpfsaam30txqhvsjsxeyv589elwv9rvy3cvlhrjtr
PS: it only works if you build Amber yourself from the PR I submitted.
#nostr #amber #unifiedpush #nip46