@LWB
Est. block 780641
Relays (4)
- wss://nos.lol – read & write
- wss://nostr.wine – read & write
- wss://relay.damus.io – read & write
- wss://relay.snort.social – read & write
Recent Notes
We’ve been in a bear market for a year.
i dunno, i was never zapped much because i'm not an influencer. but yes, there was a great decrease of those cheap 21 sats that used to be "likes". between people going back to xitter and a massive decrease of usage in general, it was to be expected. i also do not like the nwc feature that many clients have, in my experience, that is a barrier for zaps and a thing that i hate in most clients.
2
I know there are probably many and I don't want to hear all of them at once, but if you can tell me one bug that you remember that would help.
video are cropped weird and I can't see a expand button
GM Bear. https://blossom.primal.net/1b8b64658a944e8e8a9d62a53ac0f964c811d3e9a686a6e94e84670270c0cb1b.jpg
He doesn't even want wine, he's in just for the chaos
❤️1🧡1
This has already been done.
You don't need to invent zaps for Monero. You can integrate Monero right into the app, no Lightning wallet or Nostr Wallet Connect needed.
Amethyst was branched a year o...
I'd say not even the Monero community is interested in developing for the Monero folks unfortunately.
I know there are probably many and I don't want to hear all of them at once, but if you can tell me one bug that you remember that would help.
Sure, the one that I encountered and remember is that I went into my notifications, went back on the "Home" by clicking the Monero logo and it got stuck like it was still waiting on a timeout of a task. When I am back at my PC I'll let you know about any that a I come across.
I made a Monero themed client: https://moneroh.netlify.app/
Love the pixel art, it's a bit buggy, but usable.
Now to make the Monero folks happy, you need to invent "zaps" for monero and monero invoices instead of zaps lol
Now to make the Monero folks happy, you need to invent "zaps" for monero and monero invoices instead of zaps lol
4🔥1
I love how this environment is evolving so fast.
LibreNostr 0.1.3 is out.
Actually de-Googled now. Play Billing, ML Kit, Cronet and Firebase are gone, but the interesting one is what survived the first pass: Google Play Services was still being pulled in transitively by the Breez Spark SDK, through credentials-play-services-auth. That wallet backend was already disabled in code and returning a stub, so it cost 17.8 MB of native code per ABI and the whole play-services auth stack for nothing. APK went from 78.6 MB to 55.2 MB.
Primal Premium is gone too: 138 files, 14,742 lines that could not work without their servers anyway.
Three privacy fixes:
1. Photos are stripped of metadata before they reach a Blossom server. A camera shot carries EXIF with GPS to a few metres, capture time, device make and serial, often the owner's name. Byte-level rewrite for JPEG, PNG and WebP, so pixels are copied untouched and nothing is re-encoded. Now LibreNostr deletes everything before sending them the a Blossom server.
2. Direct message queries no longer go to the hardcoded public fallback relays. Opening the messages tab used to tell seven third-party relay operators your pubkey and that you were reading DMs, whatever relays you had configured.
3. Long-form feeds fell back to the global firehose whenever the author list came out empty, and the public long-form firehose is mostly spam and pr0n. Reads now come from your follows, widened at most to their follows. Never global.
Also in 0.1.3: notifications are faster and no longer truncated (one REQ instead of five, with each kind no longer competing for the same page), zaps are credited to whoever actually zapped rather than to the recipient's LNURL server, and NIP-84 highlights finally work with Amber, which was rejecting kind 9802 locally before the signer was ever asked.
github.com/Lwb89dev/librenostr
Get it on @Zapstore as usual
Actually de-Googled now. Play Billing, ML Kit, Cronet and Firebase are gone, but the interesting one is what survived the first pass: Google Play Services was still being pulled in transitively by the Breez Spark SDK, through credentials-play-services-auth. That wallet backend was already disabled in code and returning a stub, so it cost 17.8 MB of native code per ABI and the whole play-services auth stack for nothing. APK went from 78.6 MB to 55.2 MB.
Primal Premium is gone too: 138 files, 14,742 lines that could not work without their servers anyway.
Three privacy fixes:
1. Photos are stripped of metadata before they reach a Blossom server. A camera shot carries EXIF with GPS to a few metres, capture time, device make and serial, often the owner's name. Byte-level rewrite for JPEG, PNG and WebP, so pixels are copied untouched and nothing is re-encoded. Now LibreNostr deletes everything before sending them the a Blossom server.
2. Direct message queries no longer go to the hardcoded public fallback relays. Opening the messages tab used to tell seven third-party relay operators your pubkey and that you were reading DMs, whatever relays you had configured.
3. Long-form feeds fell back to the global firehose whenever the author list came out empty, and the public long-form firehose is mostly spam and pr0n. Reads now come from your follows, widened at most to their follows. Never global.
Also in 0.1.3: notifications are faster and no longer truncated (one REQ instead of five, with each kind no longer competing for the same page), zaps are credited to whoever actually zapped rather than to the recipient's LNURL server, and NIP-84 highlights finally work with Amber, which was rejecting kind 9802 locally before the signer was ever asked.
github.com/Lwb89dev/librenostr
Get it on @Zapstore as usual
