Profile: 738ea36e...

I've been considering enhancing the credibility of the nostr:nprofile1qqsfg4hh4jmk864t9cptmrnqeuta7a8n2tp2u4uaec03m5jujhwkz8qa6077t and nostr:nprofile1qqs2y0dld3kvs0s5es7lfetvcuvytas3jzqgfnlxyr5rusxqdnxa85q85utq7 by developing an open-source verifier. This verifier would fetch & compare messages from the mailing lists to their respective Nostr accounts. Every X hours it would ensure all messages have been published and remain unaltered, then sign a "sync validation signature" with the validator nsec and publish. This approach could provide stronger assurance that no additional layer of moderation exists in the cloned mailing lists. What are your thoughts on this? Any ideas on how we can feasibly implement it? Perhaps only reasonable with nsecbunker? nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzfmhxue69uhhyetvv9ujue3h0ghxjmcpp3mhxue69uhkyunz9e5k7qgjwaehxw309ahx7um5wgh8vvrv9e5k7qg4waehxw309ahx7um5wghxxmmfdehhxtnfduq3vamnwvaz7tmjwdekccte9ehx7um5wghxuet5ugk8hv

That's odd. I've just discovered that the long-form event tagged summary on Coracle displays some random note instead of the correct one. In contrast, Amethyst shows it correctly. Does anyone know why this could be happening?

@nevent1qqsxpy2ugd377k3a760lpthkzlppmeltxqezgff4qy5ngermaz6ay3cpxfmhxue69uhhyetvv9ujumn0wd68ytnzvuk8wumn8ghj7mn0wvhxcmmv93mhxue69uhkumewwd68ytnrwg4cp9t7

nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qyxhwumn8ghj7mn0wvhxcmmvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsz8rhwden5te0dehhxarj9e3xjarrda5kuetj9eek7cmfv9kqzrmhwden5te0dehhxarj9ekk7mgpz3mhxue69uhhyetvv9ujumn0wd68ytnzvuq3wamnwvaz7tmxd9k8getj9ehx7um5wgh8w6twv5qs7amnwvaz7tmwduh8xarj9e3hyqg4waehxw309aex2mrp0yhx6mmnw3ezuur4vgq35amnwvaz7tmjv4kxz7fwdehhxarjd93ksetn9ehhyecpz4mhxue69uhkummnw3ezu6twdaehgcfwvd3szxrhwden5te0wfjkccte9eekummjwsh8xmmrd9skcqgkwaehxw309ashgmrpwvhxummnw3ezumrpdejqzxrhwden5te0wfjkccte9ehx7um5wfshg6fwvdhk6qg6waehxw309aex2mrp0yhx7unpdenk2urfd3kzuer9wcq3gamnwvaz7tmwdaehgu3wdau8gu3wv3jhvc3942n

@npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn

It might be interesting if we could interface nsecBunker with an affordable, simple signing device capable of validating the policies on its own. This seems more straightforward than VLC for Lightning. Anyone doing this?

I understand nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz point. High-cost services will only be available to a select few users who pass the stringent reputation test, which is acceptable. But why not implement both options? Why not allow users to pay upfront (a concept I'll call "zapfront" πŸ˜„) to specific service providers (based on reputation), and also signal a permission for a delivery of results via an encrypted DM?

Congrats nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft! 795441 is a great birthdate! πŸŽ‰

That's very cool!

Still cool to see an email about Bitcoin & Nostr sent to the Bitcoin-dev mailing list and being cloned to Nostr :)

Is the real Antoine Riard on Nostr?

Hi nostr:npub1tsgw6pncspg4d5u778hk63s3pls70evs4czfsmx0fzap9xwt203qtkhtk4, could you suggest an alternative mitigation approach for that specific attack?

Want one of these as well? you can generate your own at https://bolt12.tattoo or https://qr.autobtc.ai

Please be patient, it's being processed on a self-hosted GPU πŸ˜„