Got myself a ghost πŸ‘» address now since alby is invite only at the moment. Random ones are free, if your paying for Amboss already you could even choose your own 🀞 hope it works better from now on

Reply to this note

Please Login to reply.

Discussion

Not working for me at all 🐢🐾🫑

Wow what a great start, thanks for trying.

Any time πŸΆπŸΎπŸ«‚πŸ˜­

I even know what the problem is. https://ghst.to/.well-known/lnurlp/royal-tan-bandicoot you can check callback, and see that they use irl parameters for the user, where it would have been better to use path. Since I assume many LN implementations just blindly add ?amount=12344&…. Instead of parsing the url and adding the additional parameter, you end up with broken request for invoice. So unless they make it a path or all implementations do it right, it will not work as it should 🐢🐾🫑

Callback for you is: https://ghst.to/api/pay?user=royal-tan-bandicoot

The client must add amount parameter and they do it wrong

Ah I see, thanks for looking into it. If I understand right that’s something I can’t change?

Unless you proxy your address like I am, not possible πŸΆπŸΎπŸ«‚

Not too sure what it means to proxy the address or if I could do so 😜

If you really want, I can setup one for you to try. I have fishcake@ln.do as my address, and it proxies to my nodes ugly lnbits address. And I have WoS as a backup, so if proxy cannot fetch from primary, it falls back to WoS . Simple 🐢🐾🫑

Ah ist that similar to ip2tor and https service with duck dns? Got my btc pay Shop on that set up but the home network got issues so that’s most of the time not available. Maybe the Amboss ghost addresses have the same network problems?

Unlikely, I can’t even fetch the invoice 🐢🐾🫑

Wired, I’ve double checked the royal-tan-bandicoot@ghst.to and successfully sent 50 sats last night 🧐

From Phoenix wallet…

Please read what I wrote about why it might fail for me on Damus using Zeus 🐢🐾🫑

I’ll do my best trying to understand πŸ™

πŸΆπŸΎπŸ«‚πŸ’œπŸ™ŒπŸ»

Just received my alby invite Code while we where writing πŸ˜‚ plan alby should work now maybe

I think it worked for me to zap you this time, but since I am on my own node with only single channel, I am not sure. Recently routing to/from alby is not great for some reason 🐢🐾🫑

πŸ˜•

Why the long face? 🐢🐾🀣

Incoming is working, now time to set the outgoing πŸ”₯

Yes, can confirm! Works like a charm! πŸΆπŸΎπŸ«‚πŸ€£

No need to set one up for me, thank you. Should be abele to work it out somehow; sometime πŸ˜†

nostr:npub19tcpurtt6xulhw0r6sc404j9jraj0h8me2lzs7z2tqewz7l0hpas59nlea is this maybe interesting feedback for your new tool?

Thanks for the tag and the suggestion! We've now switched to using path.

Glad I could help! Congrats on the launch! πŸΆπŸΎπŸ«‚πŸ™ŒπŸ»

If I try to zap ⚑️ with Zeus 😞

We recommend moving away from Tor for remote connections to LNC or Tailscale

These docs should help https://docs.zeusln.app/category/remote-connections

It was working for me most of the time, currently it got really bad unfortunately 🀷

Tor is unreliable. You’ll see a huge speed and reliability improvement with the other two.

Thanks heaps for reaching out πŸ™ I’ll have a look into it tomorrow. My head had enough for a day 🀯 the rabbit hole gets deeper and deeper ❀️

Inbound channels too expansive maybe?

No, this is due to invoice fetching, as it states. See my other note for explanation 🐢🐾🫑