Laeserin on Nostr: Well, we'll have two of the biggest calendar clients. If we agreed on a new event ...
Well, we'll have two of the biggest calendar clients. If we agreed on a new event type or some changes to one, with a NEP (Nostr Extension Proposal, i.e. a spec that's a spin-off to NIP-52), then it becomes part of the protocol. Especially as we have a relay dev on the team, and we could then prove two clients and a relay are compatible with it.
We are also missing some capabilities, in the current NIP, like we'd need more focus on time-zones (as we're planning meetups on different continents and the display is really confusing, otherwise), and we need the ability to link a set of events together into a series (like different appointments during a 3-day conference or meetup: demo session, hackathon, dinner out, etc.), with the series belonging to the calendar. Integrating polling is important, too.
We also need co-hosting. We were talking about maybe having a multi-sig event format, or something containing a sort of id-array, also for issuing confirmation-of-attendance certificates while there, by performing some task that can only be done while standing near each other. Until now, we've been using badges, but not everyone wants them and many clients don't display them. We need some normalization on the "location" tag, so that the places named in different clients sorta match-up, and we can refer to regions and not just specific towns. I'm also missing the ability to generate an ical file, for people who want to save the meeting to their "normie" calendar; that might require additional tags/fields.
But, whatever, I'm probably boring you. None of this is something that's a problem with "Nostr", it's a problem with the NIP being too limited because there haven't been enough people using it to build real products and hold real events. So, let's just change that and get the spec straightened out. The calendar stuff has been half-asleep for too long, even though it's an obvious Core NIP. It's the only NIP that involves humans interacting in real time and meatspace. Different ballgame.
We'll have our people call your people. 😉
We are also missing some capabilities, in the current NIP, like we'd need more focus on time-zones (as we're planning meetups on different continents and the display is really confusing, otherwise), and we need the ability to link a set of events together into a series (like different appointments during a 3-day conference or meetup: demo session, hackathon, dinner out, etc.), with the series belonging to the calendar. Integrating polling is important, too.
We also need co-hosting. We were talking about maybe having a multi-sig event format, or something containing a sort of id-array, also for issuing confirmation-of-attendance certificates while there, by performing some task that can only be done while standing near each other. Until now, we've been using badges, but not everyone wants them and many clients don't display them. We need some normalization on the "location" tag, so that the places named in different clients sorta match-up, and we can refer to regions and not just specific towns. I'm also missing the ability to generate an ical file, for people who want to save the meeting to their "normie" calendar; that might require additional tags/fields.
But, whatever, I'm probably boring you. None of this is something that's a problem with "Nostr", it's a problem with the NIP being too limited because there haven't been enough people using it to build real products and hold real events. So, let's just change that and get the spec straightened out. The calendar stuff has been half-asleep for too long, even though it's an obvious Core NIP. It's the only NIP that involves humans interacting in real time and meatspace. Different ballgame.
We'll have our people call your people. 😉