Fine grained filters

[matjaz]

More fine grained filters would be great.
Something like

• nwc
• webln
• NWA
• external (lnc, lnbits,..)

Or even list of connector IDs.

[rolznz]

• nwc already exists.
• webln: all connectors implement webln already - what do you mean exactly here?
• NWA: why would it be a required filter? it's just a simpler UX for connecting via nwc isn't it?
• external: why would you only want external connectors?

a list of connector ids IMO is not so great because if bitcoin connect is updated with extra connectors, the developer manually needs to update their list of supported connector ids.

[matjaz]

webln - extension. ability to hide.
nwa - it's not intuitive Alby go & is actually NWA
external. it's a combination of connectors/categories we want to show.

On some point it would make sense to organize connectors (category, filter, order).

[rolznz]

Alby Go is NWC. Just the mechanism to get the NWC connection secret uses NWA.

What is the usecase for adding those extra filters? right now we have nwc which ensures you can only have connections that support automation and can be used even if the site is not open.

[matjaz]

I am thinking Bitcoin connect > NWC. So including LNURL, Auth, window.webln, WebBTC, and maybe even Nostr connect.

[rolznz]

Bitcoin Connect initially was designed to allow connecting many different wallets but exposing a common WebLN interface. Then we realized it's also useful to expose NWC (and more wallets are trending towards supporting NWC). But still the main purpose of Bitcoin Connect is to allow users to connect their wallet to apps to make payments.

I think we need to be careful when adding more features and especially we need to be sure that they will actually be used (for example WebBTC is not even used in the Alby Extension sadly, and there we can have much safer storage of keys)