Geek on Nostr: Every Hanami instance creates its own npub on first start which is used to identify ...
Every Hanami instance creates its own npub on first start which is used to identify and authenticate with other instances. This way, you can have private Blossom servers that don't appear in your public media server lists. Add peers via IP (local or Tailscale) or via FIPS domain (npub.fips) and immediately mirror across instances. You can also set instances to be backup-only so they only ever communicate with defined peers.
The Docker image has a built in FIPS sidecar that makes using FIPS instances simple. If you choose to run the Hanami Go binary, there will be some additional, but simple steps to run.
https://github.com/Letdown2491/hanamiPublished at
2026-07-25 18:30:00 UTCEvent JSON
{
"id": "a07935ae3425aefd2540fd5b4bfefea42f4e0b7637a27add09618f597c1a0e34",
"pubkey": "daa41bedb68591363bf4407f687cb9789cc543ed024bb77c22d2c84d88f54153",
"created_at": 1785004200,
"kind": 1,
"tags": [],
"content": "Every Hanami instance creates its own npub on first start which is used to identify and authenticate with other instances. This way, you can have private Blossom servers that don't appear in your public media server lists. Add peers via IP (local or Tailscale) or via FIPS domain (npub.fips) and immediately mirror across instances. You can also set instances to be backup-only so they only ever communicate with defined peers.\r\n\r\nThe Docker image has a built in FIPS sidecar that makes using FIPS instances simple. If you choose to run the Hanami Go binary, there will be some additional, but simple steps to run.\r\n\r\nhttps://github.com/Letdown2491/hanami",
"sig": "039fcaa7998971d7b6277e154ef652c3bfe96cb15e24073e342d89c20d13569b7b3ae73ee72610f59938bb29e58c45f96eafd81a39d0cfdee8f5c8dd41b5e575"
}
