nostr:npub1864jglrrhv6alguwql9pqtmd5296nww5dpcewapmmcazk8vq4mks0tt2tq please let me know what's going on in the BTC map space. A long time ago I had been excited about coinmap using OSM data and added quite some locations myself (all of which stopped accepting bitcion later) but I think they stopped and switched to a closed DB approach, claiming problems with the OSM maintainers. BTCMap is using OSM. How do these projects relate. Obviously the latter is FOSS using open data listing some 8k venues while the other claims to list 32k venues. The former harvests locations from OSM? Is there any problem adding their data to OSM? ...
Nice demo of the visualization library. What would you want from such a bot?
Got another #noStrudel update v0.36.0: Torrents, Nostr Signing Device, and Bookmarks
Main changes:
- Torrents view in tools and under users
- Add support for Nostr Signing Device ( desktop & chrome only )
- Support default user bookmark list
- Rebuild notifications view
- Change "Copy Share Link" to use njump.me
- Add Readonly channels view
Smaller changes:
- Blur videos from strangers
- Add colors to notifications view
- Better DM layout
- Add decrypt all button to DMs
- Use nevent instead of note1 in urls
- Add local relay cache option
- Rebuild thread loading
- Add option to hide usernames
As always you can test it out at https://nostrudel.ninja or run it locally with "docker run --rm -p 8080:80 ghcr.io/hzrd149/nostrudel:0.36"

nice docker deploy! So decentralized!
Since when does Nostrudel have a "health" view? That's pretty amazing!
So the red and green columns are my 11 relays and if your post appears to not be on many relays - like that last one for example - I can hit the broadcast button to re-submit the event to all those missing red relays.
I wish somebody would dedicate time to analyze things like this systematically. Which events tend to disappear or get rejected by which relays. Who's events are stored on unreliable relays etc. I think this could be a paid service to detect who is affected by event loss and keep a backup for them and for a small fee ... "Hey, John, all your notes older than 90 days disappeared from the nostr network. If you don't have any backup, we can help you out for 100sat per kB. If you are not interested, we might also delete them by next week."

There is only one ex fiat Billionaire that's not short Bitcoin.
I had used the term "open source" quite liberally in WalletScrutiny reviews but now corrected all occurrences of "open source" to "public source" as that's what matters for my project. Apparently many international organizations agreed on using the term "open source" only if the license is approved by the "Open Source Initiative".
RMS was always preferring the term FOSS to make the distinction but I think it's fair to keep it slightly briefer and go with the OSI definition. As a fan of FOSS, I'm not willing to surrender the term "open source" to projects that are not willing to grant the liberties FOSS is granting.
My point was that with that "license", publishing the code wouldn't change much.
But then again, the coldcard apologists would probably argue it's "Open Source" if the license was "Here's the code. If you read it, we will have to shoot you on sight."
Without the right to edit code, it's by definition not open source as per OSI standards which are widely adopted.
That's what I thought when he first claimed to be Satoshi. I think he's state sponsored and will keep the lawfare up against Bitcoin devs.
What did I miss? Is Faketoshi finally going to jail?
And ... sorry for being so negative but I had hoped for some signature verification improvement or so. Some actual bottleneck fix.
So event emission is 13 times faster. That is a tiny cog in the machinery. It is a nice and simple improvement but the very basic test in the linked PR shows a 5% improvement, not a 1200% improvement.
Many on nostr support the claim that Open Source is communism. And call you a commie if you try to argue in favor of FOSS.
Surprisingly many FOSS haters around here. :(
Not sure who that is but for what it's worth, I was the dev of a wallet that went through controversies. And of the whole team, I was the most visible and thus got heat during such controversied but had the wallet gotten hacked, I would definitely not have been in charge or an entity to get any funds back from even if I wanted to.
Can you elaborate what is 13 times faster? Did you minify so it loads faster? Is the signature check faster? ...
My condolences. So young :(
TIL: BlueWallet has LDK as a hidden feature, too.
How does BlueWallet stack up in your chart with that feature?
Can you share more details about the trackers and what you test there. Some frameworks allow a lot of tracking but are used for crash reporting, only for example. I highly dislike frameworks that track user interaction or "what happened before the crash" but understand that some teams use them to provide fixes for issues they wouldn't know about without.



