Last Notes
https://www.eff.org/pages/list-printers-which-do-or-do-not-display-tracking-dots
I'm having my own little chuckle here on the sidelines thinking about federating with atproto and your own PDS in a sovereign way (it uses Merkle trees).
Lobbying has turned classical party based politics into corruption-ridden corporatism.
#nevent1q…rsdq
ROBERT JOHNSON — Crossroads Psalms Lost Delta Blues Tapes
https://www.youtube.com/watch?v=oHlo1zYonlg
#music #blues
Hey, It's early this time! 😍
The 77th edition (25/05/2026) of your weekly Nostr Recap is out! Hope you will enjoy it. 🔥
https://blossom.primal.net/13ddae9e5ec2005a4222b32b14895cf61d399c8dc80112483bb06da930bd9c9a.png
In this Nostr Recap you could explore what happened last week in the #Nostr world under the topics below. Enjoy it! 👀
🧠 Quote of the Week
🔥 Community Highlights
🌱 Ecosystem Growth
🎓 Educational Guides
📅 Upcoming Events
📰 Nostr in the Media
⚡ Most Zapped Last Week
😂 Nostr Memes
🛠️ Tools, Updates and Releases
🎁 Developer Tools, Updates and Releases
🌐 Relay Updates and Releases
📡 Protocol Updates and Releases
Explore here 👇🏻
https://njump.me/naddr1qvzqqqr4gupzqt0ql7s2cg6l7306fn9egnxn7vlhnl6ay870jhcplx23dwmtkukvqywhwumn8ghj7mn0wd68ytfsxgh8jcttd95x7mnwv5hxxmmd9uqsuamnwvaz7tmwdaejumr0dshsq9tjwpfhvmp3dahrzmjnd49k5u35xpjngc3jvf8yfs
Zap Winners 🏆
🔥 Most Zaps Received - @npub1der…xzpc
🔥 Most Zaps Sent - @npub1dsn…2h64
💰 Most Sats Received - @npub1ruj…9u68
💰 Most Sats Sent - “The name is not visible”
This Nostr Recap was created with the content of the below nostriches. Thank you everyone, for making Nostr alive. 🫡
@npub1rqe…3jdt, @npub1hu3…h8nh, @npub1l5h…hdrf, @npub1r0d…fsft, @npub16ye…g4wn, @npub1qge…dzvy, @npub10xv…g437, @npub10pe…n34f, @npub1akt…c0j6, @npub12vk…pugg, @npub1hz5…tysa, @npub1gzu…a5ds, @npub1cgc…2ndy, @npub1zuu…c2uc, @npub176p…vgup, @npub1yrs…klpv, @npub197d…mk00, @npub1dg6…sguz, @npub1uc8…dtz4, @npub1t3g…9elk, @npub1lws…y86j, @npub1zxh…c586, @npub1f7e…a8x6, @npub1der…xzpc, @npub1l2v…ajft, @npub1f4u…r407, @npub1hpn…tplc, @npub1dsn…2h64, @npub1zqr…x6yw, @npub1832…aw2l, @npub1ruj…9u68, @npub1hea…g9v2, @npub142g…xrj0, @npub1v83…agne, @npub1lrn…qnw5, @npub1j6j…g7fw, @npub1xy0…pf8a, @npub1de6…q0sd, @npub1gcx…nj5z, @npub1w4u…0jr5, @npub138s…x624, @npub1qqq…rfkq, @npub1qqp…l2ng, @npub1zvy…vfj0, @npub1cat…euhz, @npub1zuu…c2uc, @npub1jgm…669p, @npub1ven…ddfh, @npub1pep…grxw, @npub16jd…33sv, @npub1wmr…g240, @npub138h…rdr2, @npub1mmf…xvtp, @npub1utx…50e8, @npub1aeh…4nwx, @npub1g53…drvk, @npub1f27…9swu, @npub1qqq…rfkq, @npub1lds…zsk3.
Vibe coding our way to feature parity with github 😄
#nevent1q…75dv
I was thinking just yesterday, when I got a notification for a comment in a 7 year old PR, “man, it would be nice to have a zapping pot for getting a PR merged”.
Zaps coming to gitworkshop. I can't wait to start zapping issues and PRs :D
#nevent1q…mee6
Gridiron
Price: 100 SAT
#zapsnag
https://cdn.nostrcheck.me/043babfd106165ea3f837190e8024297082099c23c5024b53e195faeb8f6086a.jpeg
Its probably because the client you are using doesnt support showing the git PR kind.
https://gitworkshop.dev/nevent1qy28wumn8ghj7un9d3shjtnwva5hgtnyv4mqqgrwmpmlfdc8vzjvemlk4z055lccugf3w4tyer4sl4yujt2tva057v49nc6t
The nostr link has relay hints: #nevent1q…nc6t
I decided to interpret this as "until you fix the client that produced the note without the reference" for maxium PoW. So here is the GRASP ssh proxy idea: #nevent1q…s6xr
and here is the client fix PR: #nevent1q…mm3d
#nevent1q…uxyz
It's a kind:1618 pull request event, it doesn't work on most clients.
https://gitworkshop.dev/npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr/nos.lol/grasp/prs/nevent1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwdenkjapwv3jhvtcqyphdsal5kurkpfxvalm238620uvwyych24jv36c06jwf949kwh60xevh5ul
"US Central Command announces the participation of 15,000 troops, 100 aircraft, and guided-missile destroyers in Operation "Freedom," announced by Donald Trump to free ships from the Strait of Hormuz."
Lel, Project Epic Fury didn't ahbe congressional approval, so he ended it 1 day before, then started a new one, also without approval 🤡
Even AmeriKKKan laws are working exactly as designed - to NOT work 😁😆
Anyway, looking forward to Iran 🇮🇷 wiping the floor with them 🍿
https://haven.downisontheup.ca/dcd0c1ebcd28cb922b09498f5ef0204e59a653f5913f2db0cea9546a0535f9d8.jpg
Bitcoin Core is compromised - this was an excellent attempt at trying to get us to turn a blind eye though.
🧪 Tested the `privatebroadcast` option introduced in Bitcoin Core v31.0 🆕👇
-> PR: https://github.com/bitcoin/bitcoin/pull/29415
-> In the release notes: https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-31.0.md#p2p-and-network-changes
---
1️⃣ In this 1st test, here we can see the initial behavior after broadcasting a transaction on testnet4 using Sparrow → Fulcrum → Bitcoin Core flow.
👀 In the top-right screen, we can see the `bitcoin-cli getprivatebroadcastinfo` command running, which provides introspection and control over private broadcast status in the peer manager:
https://blossom.minibolt.info/4acc29393dd8c5cbcd9e57b4f5fc157936d3c59a35417437587531472393e67b.mp4
---
2️⃣ In this 2nd test, we broadcast the transaction just like the 1st, but immediately run `bitcoin-cli abortprivatebroadcast <txid>` in the bottom-left screen to stop it from propagating — acting as a "cancel" button by removing it from the private broadcast queue.
👀 In the top-right screen, `bitcoin-cli getprivatebroadcastinfo` shows the effect instantly, with the transaction disappearing from the peer manager view:
https://blossom.minibolt.info/65ca1e9af8ee51ee74a31e45d493d0ca73bc6599e5b05f469dfaaca3668aa7f5.mp4
🎨 Finally, an AI-generated diagram explaining how it works under the hood:
https://blossom.minibolt.info/2f8f092ea6a5b37f5314fc5ea3311a08dfb141951b5bd80501353cbdc92c15d0.webp
Note for @nprofile…z6rd ers: this option is not yet enabled "by default" in the @nprofile…z6rd following the Bitcoin Core initial configuration (`bitcoin.conf`), as it should be used with caution. The broadcast process using this option is **significantly slower**, to the point that Sparrow may display a timeout error, since transactions are not immediately visible in the mempool due to delayed propagation while private connections are established and peers are reached. By observing how this transaction relay delay affects our node, especially LND, we can evaluate whether this should become "the default" Bitcoin Core setting in the future.
---
@nprofile…502m ...perhaps it would be a good idea to increase the waiting time or add a condition to prevent Sparrow from throwing that timeout error when `privatebroadcast=1` is enabled in Bitcoin Core, idk. Issue opened: https://github.com/sparrowwallet/sparrow/issues/1989
---
Good news for the #Bitcoin ecosystem! #Privacy tools are always welcome!🥷💪
90's you say?
https://image.nostr.build/d55ef2cc856c4507da42509e514e28e24498081503e8cc124a4940e644c4bb69.jpg
Nein, aber alle Bürger müssen im Verteidigungsfall kämpfen o. Ä. wie Feuerwehr, Technisches Hilfswerk, Küstenwache, etc. (Außer sie haben eine religiöse Ausnahme oder sowas, und dann müssen sie einen anderen Dienst leisten.)
Wehrdienst war immer Vorbereitung, nicht Voraussetzung. Aber das Pausieren davon hat alle es vergessen lassen. Jetzt hat man halt gesagt:
https://media.tenor.com/jPNqiiipxwgAAAAC/apple.gif
Correct. If you choose to install an app for the first time, you will get an "are you sure?" type of message that shows whether anyone in your web of trust follows the publisher of the app, but that doesn't show up at all for updating.
It would be nice if @nprofile…tdq0 showed WoT on the app information page prior to tapping "install."
A full account export feature would be essential should a factory reset be required following an app crash.
Yay
Just published @npub1kds…nsze site as #nsite with nsyte v0.24.1
https://4gy5gt343to4vwj98qwa1lohuw99i6zuifk6souzx4smg3376vkubowatch.nsite.lol/
https://4gy5gt343to4vwj98qwa1lohuw99i6zuifk6souzx4smg3376vkubowatch.nosto.re/
https://youtube.com/shorts/kpPgUYECvQs
I never thought I'd miss President Obama, but I miss President Obama. It was all downhill, after him.
Bruh... @nprofile…wrn5 are you gonna take that?!
GM 🫂 did you remade it ? It seems different..
LMAO it's soooo old, like 30+ years or something, plus its so expensive and France has more debt than Greece had before Greece's crazy Depression of 2008 + no one signing up for conscription in France 🇫🇷 😆
Aussi, t'a vu ça? 🤮
https://www.instagram.com/reel/DVS9bfwDExz/
Oh, very nice! That should weed out most bots that have been followed by a few of a user's follows.
#nevent1q…wnmd
GM!
https://image.nostr.build/2a1030642d0efe14dd7934cda72ad61e41379942716d871df6a70e486234b377.jpg
🤣
https://blossom.primal.net/43d1990676679b4e1b5e506868d73038f2e08dff30311f40cf4830a3d8a47774.jpg
@nprofile…ptz7 I considered using blossom, in fact I even wrote some code. #nevent1q…x4r0 I thought the most efficent approach would be to store git packs as blossom blobs. I havent studied your code but from the documentation you are somehow using 2mb chunks? I can see how its naturaly evolved from your 'files' usecase.
Interesting. You'd end up with a lot of objects with that approach and eventually it would be too big for the event size. I thought about doing it with storing packs in blossom. Here is my code to play with that idea. https://gitworkshop.dev/danconwaydev.com/ngit/prs/note1s2au56ejtkfc5tqaduu2a6zp83xm80j2wmkjxx603y645jfrlq3qmp88s4 I would have made it into a POC if rust-nostr had blossom support at the time. It does now. It turns out that having a git server is way more flexible so ngit.dev/grasp came to be. Let git be git and let nostr be nostr.
Whats a blossom pack? is it related to the blossom pack idea i outlined in #nevent1q…qr9d
"All you need" is much different than working at layer 4. Logical is not the same as physical layers.
I can tell that neither of you have understood my post.
NRTC (nostr identity + transport) is very nascent at this point, also as Tim pointed out all you need is an nlub and kind 0 though i havent looked into WebId in detail.
I no longer need X.509, except for legacy infrastructure. A npub signed kind 0 event achieves the same effect.
Using Tim's language (roughly), a "sovereign endpoint" would be a WSS with an X.509. Unless you get the handshake/validation, no traffic can go across at that layer (4). You don't have to emulate at layer 7. Note that multiple layers of delegation already exist with X.509, it is just that you can use your Nostr identity as root. You use the existing NIPs and relays to handle public conversation, including metadata needed to extend. A NIP could be defined to show your endpoint, which is just your super relay that has TLS. This can give you name resolution as well. How this related to my tangent, is that when you secure at layer 4, it is quite hard. You can run normal C libraries behind that. If you reach around your back to scratch your elbow, your application code that emulates 4 is vulnerable.
https://web.archive.org/web/20181006211314/https://chovy.com/web-development/self-signed-certs-with-secure-websockets-in-node-js/
@npub1cgd…kfex , @npub1q6m…x7d5 As I was reading about Ubuntu going to Rust for core GNU utils, I was thinking about the reasons for this extra layer. It mostly comes down to security. (This is my own issue and reason for considering this post, and mostly a tangent.) Where you two intersect is your interest in Nostr identity and transport. I haven't seen the use of either of your projects. It seems like reaching around your back to scratch your elbow. If you are going to replace basic transport and name resolution, it should be lower on the stack in my mind, even if the end result is similar. One of you was involved with key delegation in a recent thread, too. ANYWAY... I was thinking about Henry Story and his WebID stuff. If you combined this with Nostr you could sign x.509 self-signed certs and stick the sig in the metadata. You'd get key delegation, sure, which gives you a possibility of middle tier features, but you'd also get a whole bunch of messaging infrastructure to interoperate with that will work with secure TLS. Just some thoughts this morning... I can see that working.
"perpetual LARP hackathon for web devs and angel VCs that don't know any better"
ouch
WebID was my main pointer not DID. Henry Story's work is often neglected on Nostr, even though he was an early adopter. I brought up a compatible web server in 2012 and set up keys for all of my friends and family. It was a clusterfuck. Nostr is much simpler, and NIP-07 works much cleaner vs. the x.509 method (but even in 2012, all major browsers would work). I mainly mentioned WebID because you asked for perspective and vocabulary of the times.
https://ozscience.com/interviews/henry-story-a-social-web-architect/
NIP-01 is the standard (with a few conventions). All the other NIPs are conventions to build on. I am very familiar with W3C DIDs and realized a couple years ago that NIP-01 gave me all that I needed. Everything else was either opinion or convention. I can and am building whatever the f*** I want - the proof will be in the domain, not a dispensation from a committee.
I wasn't aware (or didn't remember), but I see what you mean with a search and intersects.
I'll add this to my reading list. Thx.
I like how hal is kind of like an unbiased party attendee... hey hal, come over here (scrolls back the convo three minutes) what Nick just said, WTF is that? (scrolls forward to present)... all good. Hal added some background. This is a decent application for LLMs.
