NEAR Hunt

Policy

Comment policy

Every comment on NEAR Hunt is a public row on the NEAR blockchain, written and signed by the commenter's own account. NEAR Hunt reads those rows; it does not hold them. That shapes what this policy can and cannot do.

How a comment works

  • A comment is one row: key comment/{submission_id}/{ms} in the nearhunt.near namespace, value { "text": "…", "reply_to": "…"? }.
  • The author is the account that signed the write, not a name typed into the text.
  • Plain text, up to 2,000 characters. No images, no markup.
  • A deletion writes null to your own row. The site stops showing it; the earlier text stays in public chain history, as with any NEAR transaction.
  • Anyone can read every comment without this website: POST /v0/latest/nearhunt.near with { "key_prefix": "comment/" }.

What is welcome

  • Questions for the builders, and answers from them.
  • Feedback and criticism of a project, including blunt criticism of the idea.
  • Corrections, with the evidence you have.
  • Disagreement with other commenters, kept to the argument.

What gets hidden

NEAR Hunt hides a comment when it is:

  • spam: ads, referral links, token promotion, repeated posts;
  • harassment, threats, or abuse aimed at a person rather than a project;
  • someone else's personal data, or a private message published without consent;
  • impersonation of a builder, a team or NEAR Hunt;
  • illegal content, or content that is illegal to host in the operator's jurisdiction;
  • flooding: many near-identical comments that drown a thread.

Disagreement, scepticism, a bad review and an unpopular opinion are not reasons to hide a comment. Upvotes and comments are community signals, never official judging.

What hiding does — and does not do

  • The site keeps a hide list in the repository, data/hidden-comments.json. An entry names one project, one author and one comment id. Hiding is a reviewed code change, and removing the entry brings the comment back.
  • An entry cannot hide another author's comment, even one with the same id: project, author and id must all match.
  • NEAR Hunt cannot delete a comment, and does not try. Only the account that wrote a row can remove it; NEAR Hunt's accounts never write under comment/.
  • Replies to a hidden comment stay visible: they are different people's rows, and hiding one comment must not silence them.
  • Hidden comments are left out of counts and out of the discussion API, and no reason is published.

Report a comment

Open an issue at github.com/satojandro/near-hunt with the project page, the author's account id and the comment text. Reports are read by the operator; a hide is a commit, so it is visible in the repository history.

If a comment breaks the law or threatens someone, report it to the platform where you saw it as well: NEAR Hunt cannot remove a row from the chain.

Your account, your rows

Comments are signed with the login key you approve when you connect — the same key that signs upvotes. It can write only __fastdata_kv calls to nearhunt.near; it cannot move funds. Disconnecting does not remove the key from your account; remove it in a NEAR wallet if you want it gone.

Open data explains where every row lives and how to read it directly.