A standardized, open-source data format for representing and sharing event data across different applications.
Links:
- About & Differences from other formats
- 📱 Applications
- 📅 ATProto
- 📅 Event Repositories
- 📜 Data Format Specification
- @evnt/schema package
- JSON Schema (generated)
- Markdown Documentation (generated)
- ATProto Lexicon (generated, also bad)
- 🔗 Event Source
- 🔗 Application Links Format eventsl.ink
- Application Selector (eventsl.ink)
| Name | Description | Plat. | Lang. | Source Code |
|---|---|---|---|---|
| Vantage | Example Web App | 🌐 | TS+React | ./apps/web |
| Event Viewer | Kuylar's WIP |  |
Kotlin | kuylar/EventViewer |
Applications are the different clients that can be used to view and interact with events.
Applications share links to the application selector (eventsl.ink)
Events can be served over HTTP or ATProto.
Event data can be served over ATProto using the at:// URI scheme. This allows events to be stored as ATProto records, which can be easily shared and discovered within the ATProto ecosystem. We use the directory.evnt.event collection for event records, but this is not strictly required. The content of the record should be the EventData schema.
An easy way to share and distribute event data is through event repositories which use GitHub pages. You can use this template repository to create your own event repository.
A list of event repositories:
- deniz-blue/events-data: FOSS, tech, other public events.
- deniz-blue/events-data-scraped: Scraped event data from various sources.
Open an issue or PR to add your event repository to this list
