I was planning to eventually add that into atmo.rsvp too as a tool, some thoughts:
- i wouldnt necessarily expect my availability to be public (in the sent-over-firehose sense), id probably prefer a dedicated space (that i can still set to public and share the link, but cant just be found by listening to the firehose), makes it potentially easier to also add blocked out times etc in there with less privacy concerns
- not a big fan of the sidecar thing in general and imo not really needed here, i think we should probably implement something like @gui.do proposal in a generic way (array of people with roles on event records and use role=“guest” here or similar). thats the only required record (apart from createdAt which is already in
event) onbookingand note can just be inevent.descriptionand availability record booked against can be inevent.uri(and yeah that means all apps that have access to your event spaces can see that, but that would probably be the case either way as the booking record would live in those spaces too [it has to afaik as cross-space linking is not supported?])
for q #5 that strongly suggests a new permission set to me
(not super strong) opinions regarding the other questions
- weekly
- not required
- knownValues
tbh still not 100% sure how that whole space stuff is gonna work for events and availability, gotta think about that a bit more