I am damn serious about making it to the next event. Might need a few months notice for a Visa application.
send sats ⚡️
Now is all there is of time!
Its official. I am NIP-05 verified 😁
…pretty little checkmark to go along with
Optimizing availability across multiple timezones is not as easy as it could be.
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft and myself are all in different timezones and trying to find the optimal time when we are all available for a discussion.
We need some kind of micro-app where we fill our available times and then it does some magic calculation and comes up with the best time.
What’s stopping us from building it?
morning glory without the muffins 🙋♂️
“Think of yourself as dead, you have lived your life. Now take what’s left and live it properly.”
- Marcus Aurelius (younger one or older one…no clue 🤷🏿♂️)
Any practical implementation of NIP-03 in the wild? (particularly for Consensus-based record keeping) 🤔
Running an experiment on a tool that might necessitate a robust consensus mechanism among multiple parties.
Think Docusign - Party A initiates a record, and Party B (along with potentially others) is invited to verify and consent to this record. Any update to the initial record does not mutate the original but instead is tracked as part of its historical evolution, requiring renewed consensus from all parties involved.
This mechanism ensures transparency and trust, as each iteration of the record is only valid with the unanimous agreement of all stakeholders, similar to a contract’s terms that evolves over time with each party’s endorsement.
So far, I think NIP-03 could be a strong candidate for such a system, given the immutable timestamping and the decentralized verification process it offers via OpenTimestamps attestations. My query:
- Are there any live, practical applications of NIP-03 that have been implemented in scenarios requiring such consensus and non-mutability? (or any other scenario)
- How might NIP-03 (alongside other NIPs i.e NIP-01/04) be leveraged in a system where every alteration to a record is treated as an append-only transaction, with all previous versions remaining intact and verifiable?
cc: nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p
My apologies in advance if my questions seem obvious - still learning.
Any practical implementation of NIP-03 in the wild? (particularly for Consensus-based record keeping) 🤔
Running an experiment on a tool that might necessitate a robust consensus mechanism among multiple parties.
Think Docusign - Party A initiates a record, and Party B (along with potentially others) is invited to verify and consent to this record. Any update to the initial record does not mutate the original but instead is tracked as part of its historical evolution, requiring renewed consensus from all parties involved.
This mechanism ensures transparency and trust, as each iteration of the record is only valid with the unanimous agreement of all stakeholders, similar to a contract’s terms that evolves over time with each party’s endorsement.
So far, I think NIP-03 could be a strong candidate for such a system, given the immutable timestamping and the decentralized verification process it offers via OpenTimestamps attestations. My query:
- Are there any live, practical applications of NIP-03 that have been implemented in scenarios requiring such consensus and non-mutability? (or any other scenario)
- How might NIP-03 (alongside other NIPs i.e NIP-01/04) be leveraged in a system where every alteration to a record is treated as an append-only transaction, with all previous versions remaining intact and verifiable?
cc: nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p
nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr feature request: Drafts.
Mobile app crushed on me as I was concluding a post (very long and informative post, lol) - major buzz kill.
Stack Exchange on Nostr for Nostr 🤔
Needed:
More HowTos! More Tutorials! More Examples! More Documentation!
Haha. The Real Top G. Love IT! cc: nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p
nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p tag me along on the next one 😁
Live on Nos Social
hmm. has there been any concrete indication or evidence that this will happen in the foreseeable future? I personally see a Nostr failure in its hurdles to mass adoption, rather than content moderation. Even people within the community itself still see Nostr (in reference to this note https://primal.net/e/note1yqwt9dc0yc8r426j5kl6ch0mmf7fwgcj7uu72v2z9a4t3thh29asjwu2em by nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft) as esoteric and complex, lol - we might first need to foster internal understanding and widespread acceptance of the protocol. Might also be crucial to prioritise "smooth ingress points" that make it easy for those unfamiliar with Nostr to get started i.e more real world applications catered to the non-enthusiast.
some of you is asking hk's stream, sorry I only record it.
But let me have some #foodstr first and thank you nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m
Got to tag along on the next one. cc: nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p
I think someone was trying to scam me (pictured) - asking me to pay for a relay that's freely accessible
Bruh...Chill! Serve me some tea first at least