- Local-first, so it is possible to add, edit and remove events while off-line
- API that offers all functionality that is offered by the user-interface
- Listens on an Iroh endpoint
- Can store public keys of (partially) trusted endpoints
- Allow (partially) trusted endpoints to interact with the calendar data within the specified limits
Events can be many things :
- Appointments
- Tasks
- Birthdays
- Holidays
- I met a person (with contact details and the coördinates where we met)
- I took a picture (with metadata)
- I recorded an audio entry for my diary
- I need the car that day
- I can't use the car that day, because my wife uses it
- The PV-installation generated 30kWh and stored it in the battery
Figure out a way to store different types of events in a way that is machine-readable, extensible, can be consolidated over multiple instances that store similarly typed events.
Of course, events can be repeated. Events can link to other content.
Less obvious: can events be nested? E.g., a to-do list for a particular day that offers the possibility to move a few of the items on the list to another list, or move the whole list to the next day.
Events can be many things :
Figure out a way to store different types of events in a way that is machine-readable, extensible, can be consolidated over multiple instances that store similarly typed events.
Of course, events can be repeated. Events can link to other content.
Less obvious: can events be nested? E.g., a to-do list for a particular day that offers the possibility to move a few of the items on the list to another list, or move the whole list to the next day.