Yo, nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf is #Comingle down with a calendar shake-up?
Discussion
Let’s goooo. I agree the Nostr calendar stuff has been half-asleep and it’s partially my fault for taking on too many priorities. Your write up makes sense to me in general.
What about you, nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsz9nhwden5te0de5k2mpwdehhxarjxyhxxmmd9uq3samnwvaz7tm6v9cxcctz9ehx7um5wgcjucm0d5hszenhwden5te0ve5kcar9wghxummnw3ezuamfdejj7mnsw43rzdmtwe58smr58qc8qutwdecrvcmwddcxswr3we6hjan4dpmh2wtx096rq7t9d56x6umcxce8wae58quh5ctnxderjamwxslkyun0v9jxxctnws7hgun4v5q3qamnwvaz7tmp9ehx7uewd3hkctcprpmhxue69uhkxun9v968ytnwdaehgu3wwa5kuef0q9n8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99ah8qatzx9kx2mrtdqeks6rcwuukserhd33hq6ekwyuhgvrcwsukvdme0fjnq7fsdeuxz7nk0fck5mtjv5ehqwfc0qehxargddm8j73lvfex7ctyvdshxapaw3e82egpvemhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0dec82c330g6x6dm8ddmxzdne0pnhverevdkxxdm6wqc8v735w3snquejvsuk56pcvuurxaesxd68qdtkv3nrx6m6v3ehsctwvym8q0mzwfhkzerrv9ehg0t5wf6k2qpq49p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklqdgtmnt ? Does your library also handle calendars? Or will it do so? Seems essential for communities, right?
Alexandria will also have them.
Chachi does already render calendar events, planning for a deeper integration (RSVP, Events tab) since some irl communities are using them already.
Cool, I'll @ you on this stuff, then. nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn, too.
Yup, it will!
But the spec is indeed not there yet.
I don't see co-hosting as an calendar event issue. It's a co-managing a #communikey issue.
If you can:
- delegate the nostr:npub1purpleye8gzrzss99nzqqnemtf7g8xxj8p950nkyknnuqzycuh5qnazkzp key signing
- specify more than one "host" / "organizer" npub
- have external logic work out events "by geographical zone"
Then what's the issue? I need more precise criticism, I think.
Well, we'd want that tech for the affirmations, so that two people could somehow sign the same event, saying that they'd met in person at XYZ event. Otherwise, you'd need a proposal event and a confirmation event, which is inefficient, or a wrapper, which is messy.
And co-hosting events can be generated by our shared nostr:nprofile1qyt8wumn8ghj7emjv4jkuum0w4kzuumsv93k2tcpypmhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjj7qpqpurpleye8gzrzss99nzqqnemtf7g8xxj8p950nkyknnuqzycuh5qd8v2p2 npub, but you don't actually know which of us wrote that (which is sometimes a feature, since we don't want to personalize everything). Would be neat, if the community npub generated the event containing the list of hosts, and each host signed it.
Also, would just be nifty, to find out if it's possible to have a multisig Nostr event. 😅 Like, that would be cool, right?