Interesting approach. I built something similar https://github.com/nilbuild/diffity to understand unknown codebases. The difference is it gives you the interactive walk-through with mermaid diagrams, guiding you through the feature or part of the codebase that you're looking at.

I built this for a product planning tool (https://plan.fyi) I have been working on where I wanted users to define timelines using fuzzy language. My initial instinct was to integrate an LLM and call it a day, but I ended up building a library instead.

Existing date parsers are great at finding dates in text, but I needed something built for extracting context, understanding business time (EOD, COB, business days), parsing durations, and handling fuzzy periods like Q1 or "early january" or "Jan to Mar" etc.

It returns typed results (date, duration, span, or fuzzy period) and has an extract() function for pulling multiple time expressions from a single string - useful for parsing meeting notes or project plans.

https://timelang.dev (interactive playground)

We are trying to solve this at https://roadmap.sh/ai

It's still a work in progress but we are trying to make it better everyday

Happened the same to me and I thought of some updater glitch until I visited their website.

The schedule links I created with cron seem to be not working as well.

I have been using sendy for an year now. While it does have most of the features one would need, it starts to choke. I have a mailing list with 700k subscribers and it's been a pain to use sendy.

Same here. Can't manage to increase send speed in a significant way. Do you mind sharing what you optimized on your server to be able to send a mailing list to such a big number of subscribers?

I am thinking of using sendy, why is speed an issue? Aren't the emails delivered by SES? Can't you just send to SES a template and a list of emails and let them handle it?

Hey! There was no intention of "stealing." I did not know who else was involved in the development of timezones.digital, and I did send a message to the designer "Mykhailov" about using it as inspiration. The only reasons for redevelopment were:

- The timezone search in the original app was laggy.

- It did not allow searching timezones by offset, e.g., 'GMT+5,' 'gmt-5,' etc.

- It did not allow timezone search by name, e.g., PST, EST, GST, etc.

- It requested location permission that seemed unnecessary.

- It was closed source.

I had been using your product for quite some time and only developed time.fyi to scratch my own itch. I will be open-sourcing it soon and planning on extending it beyond what it is today.

Having said that, thank you for your work on timezones.digital!

Thanks, this has been fixed.

I just deployed the fix for this.

I just deployed the fix for this. It should be fine now.

Yes, you can.

I’m unable to drag the cards on iPhone.

Ah that was intentional, it disables the sorting on smaller screens. I am working on some UI refinement for smaller screens and will re-enable sorting after that.