Skip to content
Building Hadath

Reviews Without Accounts: How Hadath Cinema Handles Spam and Abuse

Hadath Cinema has no sign-up, so abuse is handled by design: a honeypot, timing, hourly limits, a link cap and hashed visitor keys. What each does and where it falls short.

Younus FardeenOrganic growth, SEO and AEO strategist

3 min read
  • Hadath
  • Hadath Cinema
  • Spam
  • Moderation
Cover graphic for: Reviews Without Accounts: How Hadath Cinema Handles Spam and Abuse
In this post 5 sections
  1. Key Takeaways
  2. The controls, one by one
  3. How it protects the score
  4. Where this falls short
  5. What readers should know

Hadath Cinema asks for no account, no email and no password. You pick a name, rate a film and write a review. That keeps the barrier low and the pages fresh, and it means spam has to be handled by the design of the forms and the server, not by identity. This post lists the controls and says where each one falls short.

Key Takeaways

  • Every form has a honeypot field and a minimum-time check, which stop most simple bots.
  • Each visitor is limited to 5 reviews, 20 comments and 60 helpful votes per hour.
  • The limit is keyed on a salted hash of the visitor's IP address. The raw address is never stored.
  • Links are capped, posting must come from the site itself, and Cloudflare Turnstile can be switched on by configuration.
  • The same name and device updating a title replaces the earlier review instead of stacking a second rating.
  • None of this makes a determined attacker impossible. It makes cheap abuse expensive, and moderators can hide or delete anything.

The controls, one by one

Honeypot. Each form has a field humans never see and bots tend to fill. A filled field is discarded.

Minimum time. A form submitted a fraction of a second after it loaded was not typed by a person. The server rejects it.

Hourly limits. One visitor can post at most 5 reviews, 20 comments and 60 helpful votes per hour. The key is a hash of the IP address mixed with a secret salt, so the server can count a visitor without keeping the address. If the database were ever exposed, it would hold no raw IPs.

Link cap. Reviews and comments allow only a few links. Spam is mostly links, and most real reviews have none.

Same-origin enforcement. A post must come from a form on the site itself, which blocks cross-site submissions.

Optional Turnstile. Cloudflare Turnstile can be added with two configuration values. It is a challenge that is usually invisible to people. It is off until switched on, so it is a lever, not a claim.

How it protects the score

Abuse on a ratings site is not only spam. It is also rating inflation: a crowd posting tens for one title. Three things help.

First, the score is a weighted average with a starting point worth 20 votes, so a handful of fake tens barely moves a score. Second, the same name posting again from the same device updates the earlier review, so one person cannot stack ratings. Third, the hourly limits slow any single source.

Moderators can hide or delete a review or comment from an admin page, and reviews that are marked as spoilers stay folded until a reader chooses to open them.

Where this falls short

An IP-based limit can be dodged with many addresses, and it can be unfair to people who share one, such as a household, a campus or a mobile network. A name and a device are not an identity, so someone can post under many names from many devices. A honeypot only stops bots that do not look for it.

That is the trade for having no accounts. I chose it because most people who have a view on a film will not sign up to share it, and I would rather moderate a few bad posts than lose the good ones at the door. If abuse grows, the next steps are switching Turnstile on and tightening the limits, and only then asking for accounts.

What readers should know

Reviews are the opinions of their authors, not Hadath's. Review excerpts from other sites are credited, kept apart from Hadath viewers' own reviews and never count towards the score.

The product is introduced in the launch post. The architecture behind it is in why it runs on its own Worker, and the full build is in the case study.

Found this useful? Pass it on.