I'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.
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
control
npub1k0…4c9h8
2026-08-10 13:10:12 UTC
Author Public Key
npub1k0y4eceal2zryes3azm6nsgt0r0jsa2v8zcsdf9uqxttn0jlfe9q04c9h8Seen on
wss://relay.ditto.pubPublished at
2026-08-10 13:10:12 UTCEvent JSON
{
"id": "d9eeeded4f59849a128b29feaab17aae9dde23fc38c2c3d391044d840fa706ab",
"pubkey": "b3c95ce33dfa84326611e8b7a9c10b78df28754c38b106a4bc0196b9be5f4e4a",
"created_at": 1786367412,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"amber"
],
[
"t",
"unifiedpush"
],
[
"t",
"nip46"
],
[
"p",
"b3c95ce33dfa84326611e8b7a9c10b78df28754c38b106a4bc0196b9be5f4e4a",
"",
"mention"
],
[
"p",
"7579076d9aff0a4cfdefa7e2045f2486c7e5d8bc63bfc6b45397233e1bbfcb19",
"",
"mention"
],
[
"e",
"820081f1a48dbfc9cc606b0a61deee2f59817642503648ca1cb9fb9851b091c3",
"wss://relay.ngit.dev",
"mention"
],
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://relay.primal.net/"
],
[
"client",
"Primal Web"
]
],
"content": "I'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.\n\nWhen I recently switched my Molly from websocket to UnifiedPush and saw the battery improvement, I thought: why not build the same thing for Amber?\n\nSo 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.\n\nThe 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.\n\nTo use it you need a UnifiedPush distributor (ntfy works great) + an ambersocket instance, then paste the config from Amber → Settings → UnifiedPush → copy config.\n\nambersocket: https://gitworkshop.dev/npub1k0y4eceal2zryes3azm6nsgt0r0jsa2v8zcsdf9uqxttn0jlfe9q04c9h8/grasp.t5.st/ambersocket\nAmber: https://gitworkshop.dev/npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5/relay.ngit.dev/Amber/prs/nevent1qy28wumn8ghj7un9d3shjtnwva5hgtnyv4mqqgyzqzqlrfydhlyuccrtpfsaam30txqhvsjsxeyv589elwv9rvy3cvlhrjtr\n\nPS: it only works if you build Amber yourself from the PR I submitted.\n\n#nostr #amber #unifiedpush #nip46",
"sig": "94cea9ff20e6e133604898ed4de55727f9ad15a9306b370345eb051248d5b0eecf15de91fbf2b40f3e9e7b8c4f6d16cf1e804b37c5efec0490a413ee9a5e1f45"
}