nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl I found a note by nostr:npub1f6ugxyxkknket3kkdgu4k0fu74vmshawermkj8d06sz6jts9t4kslazcka on theforest relay and could not publish my reply to theforest. Did I do anything wrong?
Meeting old friends is priceless.
New https://github.com/fiatjaf/nak release (v0.17.0) has:
- `nak git` commands that allow cloning, setting up a new nip34/grasp repository, pushing, fetching and pulling (just call "nak git push", for example, instead of "git push")
- `nak req --only-missing` flag that takes a jsonl file with events and does negentropy with a target relay to only download the events that are not in that file (finally nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 -- this was ready 2 weeks ago, but I had to make a ton of git stuff before I was able to publish it)
- `nak serve --negentropy --blossom --grasp` new flags that make hosting these things of servers locally much easier for debugging
- you can finally use npubs/nprofiles/nevents/naddrs directly as arguments to `nak event`, `nak req` and others (they will be parsed and included in the event or filter as proper hex)
Thank you.
It looks like you didn’t mess up nostr:npub1wmuj3vcrkz26duthss234nv62ynarq7tt7vf59emqz7scyks06psrmhpm0 yourself until now. Nor did you change keys. We’re on the same page with this.
Lost keys can be found by trusted third parties and the like. A dedicated revocation secret can disarm an uncontrolled identity takeover.
nostr:npub1wgux7feuww4xpjny0fe46p3mly5exlxh4avscsaxglmg4e83xwtsj6e5qm Time has changed Nostr for the better.
My auxiliary boat was a trusted third party for sure, and its uptime ended forever.
Thanks to this, I now find myself where I belong: Singing notes, self-sovereign and duplicated on relays.
As always, the circumstances enable us humans to prosper with love and freedom.
Thank you for welcoming me back. I feel warm, and you help me keep on learning until I get a grip on today's nostr. I will not FOLD.
As a child I used to call our cat in the long gone days when a magpie landed on the fence pole. Today I see cats everywhere on the web, without ever having called them.
I think cats are inflationary where I live, love, and let go. At least they still hunt magpies of flesh and blood.
I love the liveness of nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424.
My nostr journey began on May 19 2022, when the block height was 737,029. I set sail through the storied Bitcoin Triangle, decentralization, security, and scalability. Hoping the historic currents first noted by Satoshi Nakamoto would mask my passage into good times created by strong men.
For 187,715 blocks I navigated the same reefs that once caused my fellow plebs to lose their freedom: Ross Ulbricht back in the bitcoin OG days, and in the meantime freedom tech devs such as Keonne Rodriguez and William Lonergan Hill, along with several nameless plebs never spoken about publicly. During this period I had no access to any nostr relay and kept a low profile amid the bitcoiners as well.
Fast forward to today, with the block height now at 924,744, the memory of that expedition still lingers. Just a handful of difficulty adjustments ago, a sudden squall capsized my auxiliary boat and the hardware signing device that held my hard earned bitcoin stack. Though I was rescued by a digital immigrant, the loss of bitcoin in my boating accident was irreversible. Just as the old castaways before Laszlo's pizza day lost their supplies to the sea by failing to back up their seed.
I welcome all the well known nostr OGs ( nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 , nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s , nostr:npub1ktt8phjnkfmfrsxrgqpztdjuxk3x6psf80xyray0l3c7pyrln49qhkyhz0 , nostr:npub1nmr6w7qk0ta36vxysv77jv3d5rqghfc6d8sez8240rf3gja4vsmsd2yha8 , nostr:npub19mun7qwdyjf7qs3456u8kyxncjn5u2n7klpu4utgy68k4aenzj6synjnft and nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx ) with whom I interacted back in the days when our nostr hex private keys changed more frequently than our underpants. A warm and stylish PV 🫂 to the whole crew of new nostr npubs who believe in the right to take an identity from the universe by generating enough entropy.
Being able to read your notes again after all those blocks since 737,029 underscores how the rising star of nostr is beginning to shine in the shadow of AI slop. Gradually, then suddenly. Let's do it for the Vine this time. #introductions
#[0] , do you have a recommendation for using nostr over tor?
Has anyone managed to use nostr over tor yet? It looks like the relays don't work in the web clients when using them over tor. What's going on behind the scene?
In addition, the Umbrel security concept when I last checked the project was flawed. They were trusting the local network fully.