Just got cashu pilled #feelsgoodman
Hmm so I’ve got LNBits on my node in my basement but have a VPS forwarding Clearnet traffic down a WireGuard tunnel to that node. I think that’s functionally the same as having the LNBits instance on the VPS, right?
And yeah I’d love to get a small bit of DNuts just to mess around with it!
How are you using cashu? I’ve got a mint installed on my LNBits instance but don’t know what to use it for yet 😂
All I can think is either a wallet built into Damus sort of like the Fountain app, or (hopefully) a direct integration with your node, I.e. via LND REST, CLN commando etc.
?cid=2154d3d7r1xckvdt45novtkn1kzrexm3y9lsbd4ed887fr5s&rid=giphy.gif&ct=gMy wallet tells me it’s having trouble decoding your LNURL otherwise I’d zap the shit out of this gif. For now though I’m just going to right click and save 😎. Fix that Lightning address when you get a sec so I can give v4v!
#onlyzaps snitchez LFGGG ⚡️⚡️⚡️
Should clarify: encrypted end to end, not only at rest! This part is crucial. Unless someone gains access to your account key (much like your bitcoin private key), even if 1password itself is breached, the data the attacker finds will be useless.
Yes. I don’t know any of my passwords and that makes me feel good. I used 1password but recently migrated to self-hosted Bitwarden. 1password is excellent as a starting point. Everything is encrypted at rest and it’s *highly* unlikely that that service would be the point of failure in your personal security setup.
Been working a bunch on this LNbits extension with the boring name "nostrclient" which is a nostr relay multiplexer.
One relay in, twenty relays out!
It acts as a bridge between your client and a bunch of nostr relays. You can add one single relay in your nostr client (this nostrclient running on your own server) and connect the nostrclient itself to 20 relays.
In LNbits, we also use it to give other extensions always-on nostr functionality!
Try it out and help me find bugs!
https://github.com/lnbits/nostrclient
Not sure if a bug or user error but there’s an issue on GitHub that I believe is related to some funny business I’m seeing. Not sure exactly what’s going on but I get the impression that most notes and events are not making it from the multiplexer back to my client. https://github.com/lnbits/nostrclient/issues/14
Well looks like I’ve found the next fun Nostr thing to tinker with while I should be working. https://zine.wavlake.com/introducing-wavman/
Fren, I have no idea what your words mean but I want to understand. I think your app is banned in the US. I feel like I’m missing out on some secret gospel or something.
Because he knew that they were actually ancient alien motherships hidden in plain sight 
Welp that’s the listening material for tomorrow’s commute to the fiat mine sorted 👍
120K sats deployed 🫡 
Nostrclient LNbits extension at peak performance 🔥
Give it a try: https://github.com/lnbits/nostrclient
Question about this. Let’s say I moved all my subscribed relays from Damus to the LNBits client, then connected to the LNBits client from Damus such that it was my only relay added in that client.
All the connections in the LNBits client appear ‘green,’ and Damus shows it is connected to the LNBits client, but in Damus and other clients I try, most recent notes and events appear to be missing.
Is this expected? Does the LNBits client need to cache events or something, or is there some troubleshooting I need to do?
Wait wtf I seem to have totally missed the fact that LNBits has a kinda-sorta awesome set of Nostr tools that are easier to use than anything else out there.