#[0] Question about the LNLink app.
I see it constructs the link using a URI that consists of "nodeid@hostname and optional port"
Does this require my node to be running on clearnet or hybrid mode, or can it be behind Tor?
I'm trying to send payments from my node without needing to expose it over clearnet and without needing to set up e.g. a VPN tunnel from a VPS.
LNLink seems like a perfect solution but idk what expected behavior is if I'm trying to use it on my phone while away from my home.
Currently only clearnet but supports tor in the underlying lib, i just haven't connected it to tor because i hate tor
Alright follow-up Q then... what say I set up some subdomain, i.e. lnlink.domain.tld, then I point that at my VPS, tunnel it through to a server on my home network that runs nginx proxy manager & terminates SSL. My node would be running in tor mode only; not clearnet.
Then let's say I create a proxy host in nginx that routes stuff from that subdomain to [nodeIP]:9735, with web sockets support enabled.
Would LNLink work properly with a URI like e.g. [nodeID]@lnlink.domain.tld ?
If it looks like that'll work then it's by far the easiest way for me to use my home node remotely, leveraging my existing VPS and tunnel setup. Asking these Qs now before I dive in to the project of setting up c-lightning on a VM!
Who is he? Oh that’s right Bram Cohen.
