Use my branch of getalby until this gets merged
https://github.com/getAlby/lightning-browser-extension/pull/2063
cc #[2]
sorry, got a bit of delay there. we roll out zaps and then I will also look deeper into that. (end of the week likely)
I got it with too many. that's why I am wondering and somehow can't really understand the SSL cert issue.
Has anybody else experienced some websocket HTTP 525 errors when connecting to relays?
"expected server to reply with HTTP status code 101 (switching protocols), but received 525 instead"
So what is the status on paid relays and zaps? which relays do I have to pay to publish zaps?
sorry, Lightning Node Connect. - it can also be used to connect to LND within Alby. - was wondering if you might have used that because I had another user report something similar the other day.
Do you also use LNC by any chance?
Did somebody already build a HTTP to Nostr websocket bridge?
Everything is working smoothly here.
Did you set the setting to use Alby only on specific sites?
If so you might need to whitelist it.
this will not go away. not all lnurl tools and providers will quickly implement nostr.
maybe the big ones, but we want an open network here and not force people to use some limited lnurl providers/tools.
do you have set the config that Alby only works on click?
if so maybe whitelist snort.
did this get solved?
actually I don't think this Alert is a good practice - it looks like an error to the user. And most lightning addresses will for a long time not be able to support this NIP57.
(I appreciate the push though :) )
I am not the right person to give a good answer on privacy and anonymity there. "privacy" is also always a range.
Alby stores data in the browser. Seems the Tor Browser has become stricter there and requires user to explicitly allow that.
So if you use a Tor Browser from some public computer, then you might not want that - but then you also don't install Alby there.
can you share your secret how you can be so productive and still post so much? ;) I could use some help there :D
To the Alby Tor Browser users: The latest Tor Browser update 12.0.3 made some changes that causes errors in Alby.
If you see an error: "(Could not establish connection. Receiving end does not exist.)" it means "Error: Please set webextensions.storage.sync.enabled to true in about:config"
So to work around this, go to "about:config" and search for "webextensions.storage.sync.enabled" and enable this.
we will look into ways to work around this new limitation.
@note1cm0xud7z3489w7fkvefer8h9wgj46fp0vkuua74u5sa9t0u8kstqr4vwec