When VI
npub1e2yuky03caw…
npub1e2yuky03caw4ke3zy68lg0fz3r4gkt94hx4fjmlelacyljgyk79svn3eef
Nobody knows. Google likes to keep it like that
I hear you but I actually prefer this way of working.
I am the domain expert, I help shaping the architecture, application security and scaling... But I don't have to write all the tedious tests and inplemtations.
Tech stacks are rapidly changing and I wasn't able to keep up with all the minor update changes anyway. AI can.
I can work on 4 big projects in parallell now... And it's getting faster since the workflow cross-pollinates.
I'm a manual test monkey and clicker for the AI 😂
I am the domain expert, I help shaping the architecture, application security and scaling... But I don't have to write all the tedious tests and inplemtations.
Tech stacks are rapidly changing and I wasn't able to keep up with all the minor update changes anyway. AI can.
I can work on 4 big projects in parallell now... And it's getting faster since the workflow cross-pollinates.
I'm a manual test monkey and clicker for the AI 😂
Are you thinking multiple addresses for yourself... Or seperate accounts for multiple users (friends / family).. Or a hosted solution for the public?
Not yet.. There is a specced epic for it but waiting for first actual need to be built.
Workaround is to serve a static JSON file at https://other.example.com/.well-known/lnurlp/<name> that copies your BrollyZapper LNURL document, callback included, so wallets fetch the address from the second domain but pay through the first.
Workaround is to serve a static JSON file at https://other.example.com/.well-known/lnurlp/<name> that copies your BrollyZapper LNURL document, callback included, so wallets fetch the address from the second domain but pay through the first.
That's odd. I didn't see any codepath via nwc. Can you describe it?
EDIT: Fixed in 90.6
Omg.. That's so funny. Totally woshed over my head 😂
Check again.. Should be another 112
Yes, thank you for reporting it.