Show HN: Reallyfrom.me – vouch that your message is from you

ReallyFrom.me launched this week as a message-verification tool that lets senders prove a specific piece of text originated from them, per a Show HN post by the creator going by the handle kiddz.

The tool works by having the sender write a message, generate a hash code tied to that text, and share it with the recipient alongside a short verification link — formatted as reallyfrom.me/[username]/[code]. The recipient can then paste the message into that link to confirm the text is identical to what was originally submitted. According to the HN post, senders can also choose to make their message publicly visible on the verification page, which kiddz describes as "prolly good for public figures."

The stated motivation is the growing difficulty of knowing whether any human effort went into writing a message. The HN post frames the problem directly: "with agentic and autonomous methods of sending messages, it's harder to trust that any effort has gone into writing a message." The tool positions itself as a lightweight way to vouch for authorship without requiring recipients to trust the delivery channel — email, messaging app, or otherwise.

No company details, funding, team size, or founding date are mentioned in the source. The product appears to be an early-stage, solo or small-team project shared directly to Hacker News. The post had 1 point and no comments at the time of publication.

The broader problem ReallyFrom.me is addressing — distinguishing human-written messages from AI-generated or autonomously sent ones — has drawn attention as large language model usage in communication tools has grown. The tool's hash-based approach is simple by design: it does not authenticate identity through a third-party credential or cryptographic key pair, but instead relies on the sender controlling their own username namespace on the platform and the hash matching the submitted text. That distinction matters for threat modeling, though no security analysis appears in the source material.

No roadmap, pricing, or expansion plans are mentioned in the HN post.