The downtime was not exclusive to AlbyHub paid accounts.
Self-Hosting of AlbyHub still requires a connection to their relay in order for NWC to function. This is why running your own relay is so important!
I am still researching on exactly how to get NWC to function with your own relay to create the connection. It doesn’t appear that AlbyHub allows you to change which relay your point you’re instance to.. yet..
You still also need the Lightning address to function, and that’s dependent on Alby’s web infrastructure. There ought to be a way to self-host that too.
For receives… yes very true.. I forgot about this fact (I don’t personally use AlbyHub for receives)
Very interesting.... At least for what I have seen on how they move forward to self custodial, open source, etc... I would think they will work in giving users a way to take control on this as well. At least tutorial based.
As I figure out more, I’ll make a video about it 🫡
I have a shared webserver and a domain, so if there’s a simple way to configure an alternate Lightning address, I could use that.
If you run your own node, you can use nostr:npub10efcj7x65z2ak6vd69xr8f2hvqwuaqrhlygl3yqa4y63hfvc02mqwzaeh3 to create your own Lightning address with the PayLinks extention
courios what cloud provider are you using for you server? or is home base?
This has been my biggest hang up on start experimenting. As I do not have the hardware to run 24/7 from home.
Have many open sources software that currently I am paying for managed services, like alby hub for example and others, that would love to try to manage my self.
You can run a home node with a $250 Mac Mini and a few channels with plebs
Remember, Not your rack, not your stack!
I have a shared hosting Linux server running Apache where I can deploy an unlimited number of domains and small websites, anything that doesn’t require much bandwidth. It costs me about $12/month and I’m underutilizing it at the moment.
looking forward to it.
