Running nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl (for the first time since my entity exists).
Hope is in sight, the bird X next to the nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl inside of the circles[!] is dead*.
h/t nostr:npub1tv8gmfhalwnxxquxjzeh6gtdsdz6vg7vx0s3rt7s7uuw6aujh32qn77wn2 nostr:npub1rfd0hxdzcze6pzj29thuz34vur57wm9quje7w3edxjgusq6m47csnl7wrt
* No animals (including humans) were threatened bad for taking this shot.
#coffeechain #plebchain #birdstr #naturestr #healstr #growstr
This has to be the strangest SeedSigner photo that I've ever seen...
🍾🎆 tl;dr As nostr:npub1h8nk2346qezka5cpm8jjh3yl5j88pf4ly2ptu7s6uu55wcfqy0wq36rpev's video "a true match in cyberspace" meme's, nostr and bitcoin are tied together until the timechain discontinues humans need for logistically moving physical masses with their limited own energy or tapping proxy energy sources. When this phase-out of obsolete and inadequate knowledge happens, we'll have the chance to advance our psych-biological human entities into an era of energy singularity. h/t nostr:npub1hrctsg2qwu5gsp65gvj29968z460g0th755jq92c8uaz620lewmq6qk525
👢🥫 nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl is having a key role in kicking this can down the road in the current iteration. Keep on reading to get a picture of my vision of this iteration:
🧌😂 First, thank you nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl for noting your resonance of my photo on nostr. I thought it might be obvious why this arrangement has been used by me. But I learned that this is not te case. Whereas I just had to rearrange the items I've been unsing while soldering the pins, bringing 0.7.0 to the SD card and booting nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl for the first time, without artificial adding or rearrangement of physical items a lot.
😵🐦 The dead bird represents the downfall of nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m's twitter empire (as placeholder for all social media platforms) which is not using priv/pubkeys at all. This fall was catalysed by switching the all seeing hand from twitter inc. to X. In my reception this was initiated by nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m's realignement of his public entity to dying on the 21m'ism bitcoin hill. h/t nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc for explaining 21m'ism to me.
🔐🔏 On the other hand, a new nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl was born by me and can circulate in my network to bring joy and ease to my bitcoiners with incredible features like easy multisig and true disconnected 12th/24th checksum word calculation after generating the seed words from true entropy without using an electronic device at all. h/t to BitBix (Shiftcrypto) roll your own seed guide and printable wordlist. All those bitcoiners might eventually get nostr exposure due to nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl, see next paragraph for the how and why:
💜🪶 Furthermore I expect the nostr key generation and delegation features to hit the main branch of nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl anytime before the masses migrate from closed protocols aka. "social media platforms" to nostr and I assume that nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl will play a key role for the first wave of offline generated and delegated npubs taking their npub entity and the protection of thelike serious.
🌌🏔️ Now all those entites will have a nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl at hand to sanely onboard themselves into bitcoin with the direct support of humans which control npubs. The willing joiners can get a deep connection to bitcoin knowledge *without moving oneself or another human in space*, but by interacting with humans over nostr.
❓🔮 Can you see this vision as well, nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl, nostr:npub1tv8gmfhalwnxxquxjzeh6gtdsdz6vg7vx0s3rt7s7uuw6aujh32qn77wn2 and nostr:npub1rfd0hxdzcze6pzj29thuz34vur57wm9quje7w3edxjgusq6m47csnl7wrt?
Resources mentioned in my root note:
I love the idea of a delegated signing function for Nostr, but my understanding is that the larger delegated signing model would put too much strain on individual relays over time. Happy to be proven wrong but that was my impression.
I didn't dive deep enough into delegation myself to have a say about delegation in a technical protocol/ implementation manner.
However nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c has implemented delegation into gossip for a long time and I am assuming that users will have the say about using or not using delegation, if clients support it ( nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s ).
Relays will either get paid more by delegated notes, even if the cost is produced at the get/fetch side of other following npubs. Or some relays will just not accept delegated notes and we will see delegation friendly and unfriendly relays. (Is this the way how relays can avoid costs of delegated notes in the first place or are relays helpless currently? )
I assume that individual relays must feel the constrains first, before a protocol or relay implementation adoption will happen. Always has been, hasn't it?
Therfore I propose that *tool creators don't censorship possibilities for users* just because the costs for the network are considered too high at the moment for using a tool.
PV nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl and thank you for bringing awareness of delegation costs into my field. 🫂
Going to try to implement delegation in nostrdb to test the theory that it complicates things. I don’t think it’s as bad as everyone is claiming, but i could be wrong.
It has the same complexity issues that the 'k' tag does, where you need an event.effective_kind() and do all your indexes against the effective kind. With delegation, you need an effective_author() and do all your indexes thusly. I'm simplifying.
Wait, what’s a k tag.
Kind. It is the kind of another event also referenced, usually. In a PR (that I can't find at the moment) it is the effective kind of an event whose kind field is used to indicate it is a community-only event.
Bird X killer nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 spotted. He appears as white cat next to the nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl. See the images as proof.
Just look at nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6's cute paw. This is where the interface between his vision and the physical realignment of open communication thanks to nostr is/was.
Under this new circumstances, nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w can wrap himself up in a doggy bag and should reincarnate from his own ashes like a Phoenix. But probably this happend in the past already.
❓ Do we have a Catdog aka nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w? #asknostr
#artchain #plebchain #cat #animal #grownostr
Do not take the gossip implementation of delegation to mean that I support that alternative. I suspect there is a better way. I haven't looked into it much. It was someone else's PR that I just merged. Delegation is kind-of a pain, but I added an index to make it less costly.
What a funny looking mouse trap, too bad for the hamster next to it :/
It's a 🐦 sparrow and it's to bad for the bird X to be dead I suppose. nostr:npub1hea99yd4xt5tjx8jmjvpfz2g5v7nurdqw7ydwst0ww6vw520prnq6fg9v2
And the wooden thing is a kitchen cutting board. And on the kitchen board is a nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl, running in old school screensaver mode. 😂
