A standardized, open-source data format for representing events evnt.directoryhttps://bsky.app/profile/evnt.directoryhttps://bsky.app/profile/evnt.directory/post/3mjjufndeyc23How 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 #atproto https://evnt.leaflet.pub/3mjjufibxx22a15 Apr 2026 12:09 +0000at://did:plc:hxbg7yhlsaamqu27tp5ptmi7/app.bsky.feed.post/3mjjufndeyc23https://bsky.app/profile/evnt.directory/post/3mjeydko7sc2zMost 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! https://evnt.leaflet.pub/3mjeydgshtk2z13 Apr 2026 13:36 +0000at://did:plc:hxbg7yhlsaamqu27tp5ptmi7/app.bsky.feed.post/3mjeydko7sc2zhttps://bsky.app/profile/evnt.directory/post/3mjbyud6gvs2m📗 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.12 Apr 2026 09:07 +0000at://did:plc:hxbg7yhlsaamqu27tp5ptmi7/app.bsky.feed.post/3mjbyud6gvs2mhttps://bsky.app/profile/evnt.directory/post/3mgorpntvwk2nwe are building a new data format for events 🌐 evnt.directory 📘 https://github.com/deniz-blue/evnt does it look good enough for majority of use cases? we definitely need more feedback on this 👀 oh and also it supports atproto https://evnt.directory10 Mar 2026 06:49 +0000at://did:plc:hxbg7yhlsaamqu27tp5ptmi7/app.bsky.feed.post/3mgorpntvwk2nhttps://bsky.app/profile/evnt.directory/post/3mgkqcm5dqs2katproto08 Mar 2026 16:13 +0000at://did:plc:hxbg7yhlsaamqu27tp5ptmi7/app.bsky.feed.post/3mgkqcm5dqs2k