hmm. it says 1.8.0 in the UI for you? during the onboarding you should be prompted about the account and also in settings you can now disconnect.

btw. 1.9.0 was just shipped.

and then this from 1999:

https://www.youtube.com/watch?v=8tCC9yxUIdw

nostr:note1rmu6d0aszf7v4fdzfzxkthn25z4de6yjp5mwjg2s89zwgv0gzk0svjd26c

and then this from 1999: https://www.youtube.com/watch?v=8tCC9yxUIdw

After the last update ditto.pub works so nicely with the Alby Extension! thanks nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p

yeah. thanks a lot! very helpful. We need to learn if/how people want to use this.

please report more whatever comes to your mind! thanks!

you can. or use the cloud version. whatever is a good fit for you.

oh nice! sounds interesting!

here is an invite: https://getalby.com/auth/users/new?invite_code=b109e189

It will guide you to setup Alby Hub. Let me know if you have questions and feedback. ;)

You might need to add your lightning address in the nostr profile - this does not happen automatically.

it will allow you to setup your own lightning wallet (Alby Hub) and give you an account with a LN address

here is an Alby invite code for you: https://getalby.com/auth/users/new?invite_code=9bf19a5b

yes, you can use the wallet in the hub to pay an invoice of a sub account.

we have to learn and see what’s the usage pattern and if/how users want to use it.

so thanks for that feedback!

just trying to investigate what happened and how it can be improved.

so I appreciate that feedback.

yes, best is to use then subaccounts for everyone to have this separation.

the "main" account will always see everything.

I've inspected this further and also chatted with the LSP.

You are having a self-hosted hub there, your Alby account is connected. I see a lot of restarts of your hub there. It even looks here like you have started the Alby Hub twice in parallel. I think the hub does not protect against this, yet. But this for sure causes problems due to the nature of how nodes connect and manage state.

One channel was closed by your node actually (which indicates that there was an issue running the node).

Where do you run this hub?

And actually if you don't want or need a self-custodial lightning node, then there is no point in running it. At the state that we and lightning is at there will be some channels involved and an assumption is you want to connect to the network otherwise you would not run it.

Alby did not close any channel. Alby Hub recommends LSPs but you do not have any Alby channel.

And channel closure issues is something that all lightning teams are working on (LND, LDK, etc.) We put a lot of effort in trying to optimize this - also recommending those LSPs where we know that they work hard on providing good channel availability.

That's the state that lightning is still in and can not fully be prevented just yet in a decentralized, diverse network.

Alby Hub is also not "logging out" your system might stop/restart it which requires an unlock again to decrypt the data.

hope this clarifies some things. if you don't like it, that's fine... - actually the great thing of the open network that people can choose the tool what works for them. :) - just wanted to provide some help/clarification here.

it works without Alby's backend!

We specifically use NWC in Alby Go as a protocol that directly can talk to your self hosted Alby Hub and in v1.8 you also no alby account is required anymore with the hub. (you might want an account for notifications, ln address, etc. but it is not required.)

So Alby Go talks directly to your Alby Hub wherever you host it.

any ideas on better texts? (which also seems not to be read)

that button explicitly says “open a channel”. and not “next” or something.

the edge case here is a bit that the user has a alby hosted balance which is used instead of showing the invoice QR. we wanted to make this smooth. feedback is also that people don’t like complicated long onboarding steps. one-click done.

but there is put a lot of work in these processes. feel free to open an issue or PR.. all open source and early versions.

thanks for the feedback. seems people don’t read the text…

channel opens are also sadly still hard. and some want one-click and some want big scary second warnings.

It’s open source, ideas and pull requests are also very welcome.

everyone works hard on those things to get right for the different cases and users.

which LSP did you use? we don’t run the LSPs. but this is likely a wrong email. could it be that you tried to open a public channel from a LSP that does not support it?

in that case you also did not pay.

meh, sorry to hear that.

what channels do you have? public or private? with what peer?

I am rather sure that no nwc client supports multiple relays at this point.

and the implementation like in the spec would have issues because of underlaying query parsers.

I was also looking into that one yesterday! pretty cool

sounds interesting:

https://decentraleyes.org/

"Protects you against tracking through "free", centralized, content delivery. It prevents a lot of requests from reaching networks like Google Hosted Libraries, and serves local files to keep sites from breaking. Complements regular content blockers."

afaik those are default of the shelf components.

one has to assume any device is compromised - this just became more obvious.