steepdawn on Nostr: Having set up an own AlbyHub (on Desktop), I was still required to create an ...
Having set up an own AlbyHub (on Desktop), I was still required to create an getalby.com account which i didn't have. I had thought that "AlbyHub" gives me essentially a self-hosted version of the getalby.com - which I can run under my own domain.
So the stack is as follows (plz correct me if I'm wrong!):
1) getalby.com Account is always required. This acts as the "management UI" of my underlying hub
2) Alby Hub: that's the backend server my mandatory getalby.com Account connects to (through NWC). I can self-host, or use the alby cloud one.
3) LN Node: that is funding source beneath the Alby Hub. Can be bring-your-own-node (LND, CLN, phoenixd, any node via NWC ), embedded (LDK), external (Breezsdk, Greelight) and connects via the methods the my chonse implementation supports: gRPC, REST, NWC etc.
If so, then I know where my confusion came from. My natural association with the term "Hub" is essentially "management UI", i.e. 1).
What you call "AlbyHub" , I would call "Alby Server".
let me know if i got this correct
So the stack is as follows (plz correct me if I'm wrong!):
1) getalby.com Account is always required. This acts as the "management UI" of my underlying hub
2) Alby Hub: that's the backend server my mandatory getalby.com Account connects to (through NWC). I can self-host, or use the alby cloud one.
3) LN Node: that is funding source beneath the Alby Hub. Can be bring-your-own-node (LND, CLN, phoenixd, any node via NWC ), embedded (LDK), external (Breezsdk, Greelight) and connects via the methods the my chonse implementation supports: gRPC, REST, NWC etc.
If so, then I know where my confusion came from. My natural association with the term "Hub" is essentially "management UI", i.e. 1).
What you call "AlbyHub" , I would call "Alby Server".
let me know if i got this correct