I'm offering a consulting service for integrating with Stripe Revenue Recognition.

I'll help set it up correctly including improving your billing integration that will work well for both revenue recognition and tax integration.

Email: tanin (at) nanakorn.com

With DST, there are actually 2 new concepts: ambiguous time (if the clock rolls back) and invalid time (if the clock jumps forward).

Java and Ruby work differently. Java would simply round the invalid time to the closest valid time IIRC. Ruby would accurately raise the InvalidTime exception. Same behaviors for an ambiguous time.

Chile is actually the country that will cause tricky issue in a system because they adjust DST at midnight... so there is one day a year where its midnight is considered invalid time. If we are building a system that depends on a day's boundary, then we will encounter this nightmarish issue where one of the days must start at 1am instead of midnight.

I really hope DST is going away soon.

Thank you!

Please let me know if you have questions or suggestions.

I had to check whether this was some kind of an april fool joke.

It looks like a legit attempt. Wow. This is insanely innovative.

Thank you!

My thesis is that an intermediate layer would eventually end up being equivalent to the docx format, so I've decided not to have any intermediate representation.

We convert docx to html and send it AI. When AI rewrites the HTML and it back, we diff the rewritten HTML against the docx's document.xml and make the modification. This is a simplistic explanation of it. There are a bunch of validations and processing going on.

Regarding the tracked changes/comments, we simply invent new HTML tags for those things e.g. <ins>, <del>, <commentRangeStart> and etc.

I'm working on a Cowork/Codex plugin for reading and manipulating docx files. It uses 2-5x fewer tokens compared to the Anthropic's docx skill and is much faster.

The main target users are lawyers who redlines and drafts legal documents, and they almost always use docx.

It can be used together with Claude For Legal; The combination is pretty magical.

Here's the plugin: https://github.com/LegalRabbit-AI/legalrabbit-docx-claude-pl...

If you build connectors for yourself or your team, you probably can skip MCP because you can tell your friends to install CLI or whatever and provide extra prompts for your CLI.

If you have external users, then you have to use MCP, which comes with how to use each endpoint and etc. MCP is what their current apps e.g. Cowork, Cursor support out-of-the-box.

In that sense, MCP is very much not dead

If you need a network boundary, what MCP provides that REST API + llms.txt can't do?

OIDC? Ease of deployment in a company?

You can have your IT department configure an MCP for the org, and your regular non-technical users click a button and login with their account the service. Then they get all the tool calls authenticated as themselves.

The AI probably can figure out. However, Claude Code and other tools are built to support MCP. This means MCP is probably more reliable than using REST API + llms.txt.

Standardization. Who writes llms.txt? Everyone writes their own? Will agents still behave the same?

DOCX or OOXML takes it to another level.

Instead of making something an attribute, they make it a child element...

Yeah, I try to avoid 3rd party libraries unless it comes from credible sources/companies or vetted by famous frameworks e.g. Rails uses it.

Not just for NPM but for Intellij plugin, VSCode extension, and etc.

If Node has officially pre-vetted libraries, that would be really awesome.