Avatar
bumi
330fb1431ff9d8c250706bbcdc016d5495a3f744e047a408173e92ae7ee42dac
working on getalby.com - a browser extension with lightning and Nostr support

that's likely apps caching the profile information and it will take a bit.

Or relays not having the new information?

you mean because of programming language?

or what should be changed?

Our NWC implementation is open source and supports multiple backends. You can already easily self-host it with your LND node for example.

If you miss some features or want to see other node backends please open an issue.

https://github.com/getAlby/nostr-wallet-connect/

nice, great to see more NWC implementations.

is there anything that you dislike on our LND implementation? https://github.com/getAlby/nostr-wallet-connect/

it supports the LND backend (which is also used for Umbrel for example)

true, I heard Damus needs to be once restarted before it works.

payment was sent, but the zap event was not received, yet.

this is the first time it really feels like value is flowing freely as it should and as information is since we have the web.

There is currently a PR for that and I guess it will be merged in the ~next week.

You'll be able to define allowances/limits and expiry times.

any specific setting you would like to see?

let the zaps flow

could you share this on a GH issue?

I think we might need to process payment requests sequentially in that case - which should be fine on personal nodes.

Here are the logs! 🐢🐾🫑

2023/05/16 00:49:49 /build/service.go:103 database is locked (5) (SQLITE_BUSY)

[0.355ms] [rows:0] SELECT * FROM nostr_events WHERE nostr_id = "4859dc6f74f0b43b47e4a1b8b2d04a4593b81a01461b891afc60bfc7f3aae67c"

2023/05/16 00:49:49 /build/service.go:112 database is locked (5) (SQLITE_BUSY)

[0.348ms] [rows:0] SELECT * FROM apps WHERE apps.nostr_pubkey = "71143dc6a4053f80eb86b86266bc986a7977f38612e9ed7e59f592033647d93e" ORDER BY apps.id LIMIT 1

2023/05/16 00:49:49 /build/service.go:70 database is locked (5) (SQLITE_BUSY)

[0.383ms] [rows:0] SELECT * FROM nostr_events WHERE nostr_id = "4859dc6f74f0b43b47e4a1b8b2d04a4593b81a01461b891afc60bfc7f3aae67c" ORDER BY nostr_events.id LIMIT 1

{"level":"error","msg":"database is locked (5) (SQLITE_BUSY)","time":"2023-05-16T00:49:49Z"}

{"eventId":"0a0344730654cd7d837c207166a206735871a89ec017306ac0a4078ba4e390bc","eventKind":23194,"level":"info","msg":"Processing Event","time":"2023-05-16T00:49:50Z"}

2023/05/16 00:49:50 /build/service.go:103 database is locked (5) (SQLITE_BUSY)

[0.362ms] [rows:0] SELECT * FROM nostr_events WHERE nostr_id = "0a0344730654cd7d837c207166a206735871a89ec017306ac0a4078ba4e390bc"

2023/05/16 00:49:50 /build/service.go:112 database is locked (5) (SQLITE_BUSY)

[0.416ms] [rows:0] SELECT * FROM apps WHERE apps.nostr_pubkey = "71143dc6a4053f80eb86b86266bc986a7977f38612e9ed7e59f592033647d93e" ORDER BY apps.id LIMIT 1

2023/05/16 00:49:50 /build/service.go:70 database is locked (5) (SQLITE_BUSY)

[0.334ms] [rows:0] SELECT * FROM nostr_events WHERE nostr_id = "0a0344730654cd7d837c207166a206735871a89ec017306ac0a4078ba4e390bc" ORDER BY nostr_events.id LIMIT 1

{"level":"error","msg":"database is locked (5) (SQLITE_BUSY)","time":"2023-05-16T00:49:50Z"}

that's super helpful. I see you use sqlite is there a chance you can run on PostgreSQL?

in the extension we currently only show the outgoing ones made with the extension.

We will update that in the next release hopefully.

We wanted to add more website metadata there and that's why only initially focused on that data.

But now with zaps being everywhere and more apps integrating lightning we need to revisit this as it is confusing.

yeah! I think getting the incentives right for all parties involved is essential and we now have the chance to do this.

Imagine not only relays but any micro service in the ecosystem like for example image/file hosting sites.