@bumi
28,302 sats stacked
stacking since: #8765longest cowboy streak: 2
by
for
let me know if you want to test it and need help.
You can connect the Alby lightning address to your LND node. But the UX is not as good as we want it to be so far. (current sats are not forwarded for example). We push for NWC there and it will become quite easy then.
yeah, a lot is happening there. it will get easy. check out NWC I think this could be helpful for you - more universal and future proof.
We are currently deploying an update there that allow users to specifically create lndhub credentials when needed. One issue that lndhub currently has is that there are no permissions and that credentials can not be revoked. This is a first step to give the user more control. Please give us a bit and sorry for this.
Even though going forward I believe lndhub connections will be soon be replaced with NWC.
whoot! looking forward to it and have fun!
If somebody wants to run their own lndhub: we maintain an API compatible version written in Go: https://github.com/getalby/lndhub.go It is has no run-time dependency and is deployable. Currently it is using PostgreSQL for data storage - but SQLite would actually also be supported.
that's great to hear. would for sure love to support it. Rust is just not my main language and it was easy to write those lines of JS.
Can the relay be disabled? because I assume if it gets used as a relay it needs much more resources and has more traffic.
My use-case is mainly that existing apps can publish events to Nostr without the requirement to add the websockets handling. Potentially also loading specific notes through a HTTP get.
fetching notes? It would be possible I think, but that was not my use case so far.
I didn't really know about blastr. thanks for sharing it. Is it correct that blastr sends to as much as relays out there? here the client defines the relays that an event should be sent to. It is also NOT intended to be used in a Nostr client but simply tries to be a tiny, stupid HTTP function that takes an event and an array of relays and publishes to those. So the goal is a bit different.
I had built a demo music player using LSAT-LNURL-WebLN: https://mixtape.albylabs.com/
heja, I am working on Alby and as a open source project and company we take this very seriously. Where do you feel like we did not attribute something or even where we rip something off?? Yes, we screwed up in a podcasting guide where copied parts were published under our name. This was bad and I did not do the necessary review there, but this was resolved (here on stacker news) and corrected. Our software and contributions are published under open licenses, we build in the open on GitHub, etc. so this is very important to us. If you have feedback there, please let us know.
WebBTC/WebLN enables web apps to integrate lightning and allows building lightning integrated web apps. Alby (and others) implement this standard.
I think one idea to grow the LN network is to bring lightning to existing products/industries where the lightning solves existing problems and is an enabling technology. Do you have thoughts on industries or markets where the lightning network is a good fit or where you see potential for new developments?
What technology or products outside of the Lightning/Bitcoin space are you most excited about?
What would bots do with the search results? bots are generally a problem I guess?
yes, sharing the revenue with the publishers would be a nice USP and solves some of the criticism of how it currently works. maybe the user even only pays when they actually click the link - assuming this means the result looks relevant to them.
I would like to drop sats for each search or maybe also more sats for some special features. To me buying a subscription and topping up an account then can also be done with card and is a big barrier of entry for me.
with https://www.webln.guide/ you could simply requests sats from the user onclick.