Open Evnt @evnt.directory · 29/06/2026We updated the documentation! → evnt.directoryevnt.directoryOpen Evnt: a data format for eventsAn event data format with native multilingual support, partial real-world dates, and a component system that never needs a fork. 010
Open Evnt @evnt.directory · 18/04/2026Our main goal is to just define the data layer first - fix how we store the events. The format we are defining is meant to be protocol-agnostic: it should work over normal web, AT Protocol, ActivityPub, etc. What you are talking about is relevant to what we are doing and we are interested! 000
Open Evnt @evnt.directory · 15/04/2026How do you represent a 3-day hackathon where Day 1 is in an auditorium, Day 2 is on Discord, and Day 3 is both? Legacy formats break here. Open Evnt doesn't. Here is how we’re handling multi-instance, multi-venue scheduling: #opensource #atprotoevnt.leaflet.pubInstances & VenuesSecond in a series about fixing the structural flaws in how we represent events 050
Open Evnt @evnt.directory · 13/04/2026Most event formats require a precision that doesn't exist in the real world. We're starting a series on Open Evnt and how we're rethinking event schemas - starting with Partial Dates!evnt.leaflet.pubScheduling is complex: Why we need Partial DatesFirst in a series about fixing the structural flaws in how we represent events 291
Open Evnt @evnt.directory · 12/04/2026📗 Just published the lexicons for the "0.1" version of Open Evnt. It's now more AT Protocol compatible! PartialDate was also changed to fix a big flaw. Read more about the specification here. 020
Open Evnt @evnt.directory · 10/03/2026we are building a new data format for events 🌐 evnt.directory 📘 github.com/deniz-blue/e... does it look good enough for majority of use cases? we definitely need more feedback on this 👀 oh and also it supports atprotoevnt.directoryOpen Evnt 022
