I've came up with an interesting way for storing irregular time patterns in my time library, which is also easily DB serializable.

May add django orm support for the library, so storing date ranges will be a breeze!

Over the past 4 month I wrote a backend API for a calendar app. Here I found out the problem - do you store all of the events in a calendar per-day with links between periodic events, or store only the periodic info and generate events from it?

I settled on the latter, qurious abt other solutions

I've been working on a little python library for datetime manipulation lately, called "jikan". It's the first for me, since before I've only wrote application code (so I was the only end user for it), and writing a sane API is an interesting challenge.

I will write abt my findings when it's ready!

So I'm gonna run a little experiment here to compare bluesky and the xitter experience, maybe setup some dualposting, hope this goes well!