Always up for a new Podcast, just looked at Martyr Made and it looks like they only did a couple episodes in 2024?

nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q seeing this about 50% of the time I try to load yakihonne.com

Oh, sorry, just seeing this comment now. That's interesting. Yes. Any chance you could try the Alby extension with a different browser?

Thanks. Haven't been able to find any problems yet either using automated or manual testing. Pls send me a telegram message, this could be an interesting test case to try to figure out why you can't reach the relay.

We had an outage with Megalith LSP for about 12 hours, starting from about 36 hours ago. That said, during that time, our automated test systems did not flag any issues with Rizful or the Rizful NWC relay. Did you see an issue? Still seeing any issues on your end?

We discovered a vulnerability in the interaction of two different Lightning implementations. It creates a situation close to DOS (denial of service), so we're not publicly disclosing how it works -- if we did, we could enable a bad actor to attempt to bring down other services. But the implementations involved are both aware of the situation and will be patching it in an upcoming release. We also remediated the situation on our end so we're no longer vulnerable.

Heroku or digitial ocean.

I just zapped from Rizful node to you without issue.

Do what?

Thanks to a fix suggested provided by Matt Corallo, I believe that this issue is now fixed and all of the Alby nodes will see that their Megalith LSP channels come back online over the next hour or so. Apologies again for the disruption, but you can remember you were around for an actual discovery of a potential problem in Lightning that had never been discovered before....

For those of you with nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm cloud nodes with Megalith LSP channels ..... we actually discovered a heretofore undiscovered issue with the interaction between two Lightning implementations about 12 hours ago, which led to many of the channels with LSP going down .... thanks to help from nostr:npub185h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qcswrdp , who suggested finally quite a simple solution everyone else had overlooked, this problem should now be behind us. If your channel with Megalith LSP is still down, please note we're bringing up channels slowly out of caution, however all Megalith LSP channels should be back up and running within the next 3 to 5 hours.

Yes. That's correct. We won't give you a NWC code unless you have a channel.. because Lightning needs channels!

Apologies for the disruption. Part of the fun of being early in Lightning is discovering new, undocumented issues, that nobody has found before. We're working with the best minds in Lightning currently to get the channels back online. It's a networking issue specific to an "unfortunate" interaction of two implementations Lightning protocol, that (as far as we know) was a theoretical issue that we realized could possibly happen -- but never actually seen "in the wild" before about 12 hours ago... it's not a failure of the LSP node, a hardware issue, or anything like that. Alby Hub is a pioneer and we're the biggest LSP on Alby Hub, so we have the joy of seeing the interesting/hard problems before anyone else does.

You could also "swap in" with Boltz, but that isn't my usual strategy...

It's an actual Lighting Node has all all the important properties thereof -- it's not a "shared wallet" or "wallet service"..... By "top it up" you might mean "deposit BTC so you can spend it as Lightning". The most low-level way to do that would be to deposit BTC onchain to the Lightning Node, and then open your own channel. But to do this with under, like 150,000 sats is not really a great idea. So another thing you can do is get an *inbound* channel, and then follow either of these "get outbound capacity" strategies here: https://rizful.com/docs/balances-and-capacities#outbound-capacity

Don't have your own Lighting Node yet? Follow our handy and stylish guide: https://rizful.com/get_zaps_with_your_own_lightning_node

DM me your signal usernames pls

Also, in the future, people besides BTC maxis will actually use Nostr, so at that point, we can just auto-follow whoever are the best looking and/or most famous people on Nostr, and then we will have created a produce that average morons finally want to use... This might sound like a joke but I think this is actually the goal, right?

The only thing worse than "automatic follows" is freshly booting up #damus or #primal and finding just "nothing"... just loading content, and nothing loads. This was my entire experience using #nostr during 2024. I literally tried to use Nostr a few times last year and just gave up at this first thing where nothing would load. So given that, I'd much rather be auto-followed to a bunch of BTC maxis who only post "GM'... when the alternative is NO CONTENT!

For any new Nostr developers (such as myself), who can read Javascript, I highly recommend the #yakihonne repository .. For example, for learning how zaps work in practice: https://github.com/YakiHonne/yakihonne-web-app/blob/main/client/src/Components/NOSTR/ZapTip.js ... ZapTip.js is a MASTERPIECE of readability, all in one file! But..... nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q can you push your latest code at some point? For example I think this "relaysOnPlatform" variable is not used like this anymore ... https://github.com/YakiHonne/yakihonne-web-app/blob/571028ae09eafa95fcf1c75922fd11f99ff2193e/client/src/Components/NOSTR/ZapTip.js#L264 ... I cans see when I zap using Yakihonne that you are are somehow pulling in additional relays, like the user's 10002 relays? To understand how this worked, I've been looking at #coracle nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn codebase.... the #coracle codebase in MUCH more difficult to understand, but the actual performance of the web application is also MUCH better than Yakihonne - I think that's a tradeoff of readability vs performance! In Coracle, after quite a bit of digging, I semi-understand how Coracle is aggregating the relays to put into the zap event, I think it is grabbing the "read" relays from the 10002 event.... it involves getting into the "Welshman" repository (perhaps named for a certain developer who might of Welsh descent....) https://github.com/coracle-social/welshman repository, ... All somewhat too complicated for me to fully understand but I think this complexity leads to better performance.... The relays that are added to the Zap Event are aggregated here: https://github.com/coracle-social/coracle/blob/b47ab64a4c7a897eaa1a81980940664797d032b3/src/app/views/Zap.svelte#L93

OK, looks like we could get at least 4 to 5 people which seems like a first step toward critical mass. I have a location we could use near La Brea and Melrose in West Hollywood... would not want to provide address in a public message but could provide via DM.... what is a good date/time for everyone? I'm around except for March 21 to April 5th...