Contact

Epochly is a static site with no backend and no contact form, so email is the only channel — which also means nothing you send passes through this website at all.

Email: rlaejrtn16@gmail.com

What gets answered first

The site is maintained by one person alongside other work, so replies usually take a few business days. Two categories jump the queue, because they are defects rather than wishes: a conversion that produces the wrong instant, and a code snippet in the language cheat sheet that is not correct or not idiomatic. Both put a wrong fact in front of readers, which is the one failure mode this site is built to avoid.

Reporting a wrong conversion

Include the exact input and what you expected, and the problem is usually reproducible in one attempt:

• The literal value you pasted, character for character — including any sign, decimal point or separators, since those affect parsing.
• Whether you let it auto-detect or forced a unit with the s / ms / µs / ns buttons.
• The instant you expected, ideally as ISO 8601 in UTC so there is no zone ambiguity in the report itself.
• Your time zone — the IANA identifier the tool printed, such as Europe/Madrid — if the disagreement is in the local line rather than the UTC line.
• Your browser and its version, which matters for anything involving zone data.

Correcting a code snippet

The ten-language table on the home page is the part most likely to age or to be wrong in a way that only a daily user of that language would notice. If a form is deprecated, if a newer standard-library call has replaced it, or if the version note is off, please send the replacement in the shape you would actually write it, plus the version it applies from. Corrections from people who use the language every day are worth more than any amount of re-reading here.

Reporting a time-zone case

Zone handling is the part of a date tool most likely to be subtly wrong for someone else, because most of it is invisible unless you live in the affected zone. Three cases are worth reporting even if you are not certain they are bugs: a non-whole-hour offset rendering incorrectly (the +05:45, +12:45 and -02:30 zones are the usual canaries); a daylight-saving boundary where the encode direction picks an instant you consider wrong; and a historical date where the offset that applied then differs from the one that applies now. In each case the useful report is the wall clock you entered, the zone you selected, and the epoch value you expected.

Embedding, and asking for something new

The converter can be dropped into another page with the <iframe> snippet on the home page. If it renders badly inside your layout — clipped, mis-sized, or fighting a content security policy — send the page it is on and it can usually be fixed from this side. There is no tracking in the embed and no registration to use it; it is the same static page.

Requests for conversions the site does not cover are read but rarely acted on quickly. Epochly is deliberately narrow: epoch values in and out, in the four units, plus the Discord markup. Anything that would need a network request, an account, or a server has already been ruled out by the no-backend design described on the privacy page, so those suggestions are declined regardless of how good the idea is.

What cannot be answered here

Debugging a specific application's date handling is outside what an email exchange can do — the answer almost always lives in code and data that cannot travel in a message. The pages themselves are written to make that debugging self-service: the milliseconds to date page identifies unit bugs by their fingerprint dates, and the date to timestamp page shows what a missing time zone actually costs. Working through those two will resolve most of it faster than waiting for a reply.

Please also do not send production log excerpts. They are frequently more sensitive than they look, and nothing about a conversion bug requires them — the single value that misbehaved is enough.

Before writing

A lot is already covered: how unit detection works and what the tool deliberately does not do is on the about page; data handling and advertising cookies are on the privacy page; and the recurring questions — seconds versus milliseconds, the 2038 boundary, Discord's style letters — sit in the FAQ sections of the converter, the current timestamp page and the Discord generator.