Moderation on Vahuk exists to help keep Stories useful, community activity genuine, and the platform safe to use.

Vahuk may review Stories, accounts, votes, reactions, comments, source URLs, domains, Karma activity, and other platform behavior when there is a reasonable concern about spam, abuse, manipulation, safety, technical integrity, or policy compliance.

Moderation is not intended to punish ordinary mistakes, unpopular opinions, or normal disagreement. The goal is to protect useful discovery and address activity that creates a real problem for readers, contributors, or the platform itself.

This policy works alongside the Community Guidelines, Submission Guidelines, and Spam & Abuse Policy.

Why Vahuk Moderates Content and Activity

Vahuk is a community-powered social bookmarking and link-discovery platform. Members submit Stories, classify them, vote, react, comment, and help other people discover useful content from across the web.

Moderation helps keep those systems useful by reducing problems such as:

• spam and repetitive promotion;
• duplicate Stories;
• broken or unsafe source URLs;
• misleading titles and descriptions;
• incorrect or abusive Genre classification;
• fake votes, reactions, or comments;
• Karma manipulation;
• malicious links;
• harassment and other community abuse;
• technical abuse of Vahuk’s infrastructure.

For a broader explanation of how Stories move through Vahuk, see How Vahuk Works.

What Can Be Moderated?

Moderation is broader than deleting Stories.

Vahuk may review or correct:

• new Story submissions;
• published Stories;
• Story titles and summaries;
• Genres and Tags;
• source URLs and source domains;
• votes and reactions;
• comments and discussion activity;
• User Karma and Story Karma where correction is needed;
• contributor trust signals;
• user reports;
• account activity;
• suspicious or abusive automated traffic.

What Can Trigger a Review?

A moderation review can begin for many reasons.

Possible triggers include:

• a member report;
• duplicate-source detection;
• a broken or unreachable source;
• Genre relevance concerns;
• domain restrictions or reputation concerns;
• unusual submission patterns;
• suspicious voting or reaction activity;
• spam or abuse signals;
• a malicious or deceptive destination;
• unusual account behavior;
• automated integrity checks;
• manual administrator review.

A review does not automatically mean that a rule was broken. It means there is something worth checking.

Automated Checks and Human Review

Vahuk can use automated systems to identify obvious problems and patterns that may deserve attention.

Automated checks can help identify issues such as:

• duplicate or equivalent URLs;
• invalid or unreachable sources;
• restricted domains;
• unusual submission behavior;
• possible Genre mismatches;
• voting or reaction anomalies;
• repeated abuse patterns.

Automated signals are useful, but not every signal is a final judgment. Some situations need context, and that context may require human review.

At the same time, not every routine validation needs manual moderation. A known duplicate, invalid URL, blocked domain, or clear technical failure may be handled automatically.

Moderation Before a Story Is Published

Moderation can begin during submission.

Depending on the source, account, and current platform rules, a submitted Story may be:

• published normally;
• processed more quickly under trusted source rules;
• held for review;
• rejected as a duplicate;
• rejected because the URL cannot be validated;
• rejected because of a domain restriction;
• rejected because of an integrity or policy concern.

For practical pre-submission rules, see the Submission Guidelines.

Moderation Does Not End After Publication

A Story can be valid when it is published and become a problem later.

For example:

• the source may stop working;
• the URL may begin redirecting somewhere else;
• the domain may change ownership;
• the website may become compromised;
• new spam signals may appear;
• a user may report a serious problem;
• a duplicate may be discovered later;
• classification problems may become clear;
• artificial engagement may be detected.

Publication therefore does not provide permanent immunity from later review.

Vahuk May Recheck Older Story URLs

Vahuk may periodically check older Story URLs to see whether the original source is still available and useful.

A source check may identify problems such as:

• connection failures;
• HTTP errors;
• missing content;
• unrelated redirects;
• unavailable pages;
• changed or unsafe destinations.

If a source no longer works or no longer provides meaningful content, Vahuk may review or remove the Story.

This helps prevent old Story archives from slowly filling with dead or misleading links.

See What Is a Story? for more about the relationship between a Vahuk Story and its external source.

Duplicate Story Moderation

Vahuk tries to keep one useful Story record around a source rather than several copies of the same destination.

Equivalent URLs may sometimes look different while still representing the same underlying source.

When a duplicate is found, Vahuk may:

• block the new submission;
• preserve the existing Story;
• remove a redundant Story;
• keep votes, reactions, comments, and Story activity centered around the existing record where appropriate.

An accidental duplicate attempt is different from deliberately modifying URLs to bypass duplicate detection.

For more detail, read the Submission Guidelines and Spam & Abuse Policy.

Genre and Classification Moderation

Vahuk may correct the classification of a Story when its Genre or Tags do not reasonably match the source.

Possible actions can include:

• changing a Genre;
• removing an irrelevant Genre;
• reviewing excessive Genre assignment;
• correcting Tags where appropriate;
• reviewing repeated off-topic classification.

A Genre correction does not automatically mean the Story or contributor is being punished. Sometimes the Story simply belongs somewhere else.

For classification guidance, read Genres on Vahuk.

How Genre Integrity May Be Reviewed

Vahuk may use several signals to understand whether a Story fits the Genre selected for it.

Those signals can include:

• the Story title;
• the summary;
• Tags;
• the selected Genres;
• the source domain;
• previous classification patterns;
• account history;
• reports or moderation history where relevant.

Vahuk does not publish every Genre relevance score or threshold because exact internal rules could be used to game classification checks.

Domain-Level Moderation

Vahuk may apply rules at the source-domain level when a broader pattern matters more than one individual Story.

A domain may be:

• handled normally;
• treated as an established or trusted source;
• reviewed more carefully;
• restricted;
• blocked.

Domain treatment can change over time if the website’s ownership, content, behavior, or safety changes.

Trusted Domains Are Still Subject to Review

Some established domains may be processed more quickly when the URL is valid and no other problem is found.

That does not mean every Story from the domain is permanently approved.

Trusted source handling does not override:

• duplicate checks;
• source availability checks;
• malware or phishing concerns;
• other platform policies.

A previously trusted domain can also become restricted if serious problems develop later.

Restricted or Blocked Domains

Vahuk may reject sources from domains associated with serious or repeated problems.

Possible reasons include:

• persistent spam;
• malware;
• phishing;
• fraud;
• deceptive redirects;
• repeated abuse;
• other serious integrity concerns.

The complete internal domain lists and decision rules do not need to be public.

See the Spam & Abuse Policy for more about domain-related abuse.

Voting and Reaction Moderation

Votes and reactions are useful only when they reflect genuine community activity.

Vahuk may review activity that appears to involve:

• vote exchanges;
• coordinated voting;
• alternate-account voting;
• automated votes;
• reaction farming;
• scripted reactions;
• targeted downvote campaigns;
• other artificial engagement.

For the expected use of these features, read Voting & Reactions.

Artificial Activity May Be Reversed

Moderation is sometimes about correcting the record rather than removing content.

If activity is found to be artificial or technically invalid, Vahuk may:

• remove invalid votes;
• reverse artificial reactions;
• recalculate Story activity signals;
• correct related Karma;
• adjust ranking effects where necessary.

The purpose is to restore a more accurate picture of genuine community activity.

Karma May Sometimes Need Correction

User Karma and Story Karma can sometimes require administrative correction.

Reasons can include:

• a technical error;
• an invalid reward event;
• reversed artificial activity;
• abuse-related corrections;
• restoring Karma after an incorrect deduction;
• another legitimate administrative correction.

Legitimately spending User Karma through normal Story submissions is not a moderation violation.

A lower Karma balance caused by normal participation does not by itself make a contributor less trusted.

For more about User Karma, Story Karma, and contributor trust, read How Karma Works.

Contributor Trust and Moderation

Contributor trust can be one part of Vahuk’s broader integrity system, but it is not based on one number or one event.

Depending on the situation, trust-related signals may include:

• account history;
• published Story history;
• spam or removal history;
• reports and moderation history;
• duplicate submission patterns;
• submission velocity;
• source-domain diversity;
• other integrity signals.

Vahuk does not publish the complete trust formula because doing so would make deliberate manipulation easier.

High Karma or Trust Does Not Provide Immunity

A long history on Vahuk does not put anyone above the rules.

High User Karma does not prevent account review. High Story Karma does not prevent a Story from being moderated. A trusted contributor can still make mistakes or become involved in abusive activity.

The opposite is also important.

Low Karma does not automatically mean someone is abusive, and a new account is not automatically suspicious simply because it is new.

Comments and Community Conduct Can Be Moderated

Vahuk members are free to disagree, criticize, question, and discuss the Stories they find.

Comments or other community behavior may require moderation when they involve problems such as:

• harassment;
• credible threats;
• targeted abuse;
• spam;
• repeated disruption;
• impersonation;
• malicious links;
• publishing private information to harm someone.

See the Community Guidelines for the broader standards of participation.

Disagreement Is Not Automatically a Moderation Issue

Vahuk should not remove or restrict a Story simply because people disagree with it.

A Story can be controversial, unpopular, critical, political, or opinionated without violating Vahuk’s rules.

Negative votes also do not automatically prove that something should be removed.

Moderation should focus on behavior, integrity, safety, technical validity, and compliance with platform rules rather than whether a viewpoint is popular.

Reporting Content or Activity

User reports can help draw attention to problems that automated systems may not fully understand.

Reports may be appropriate for issues such as:

• spam;
• malicious links;
• harassment;
• impersonation;
• fake engagement;
• serious or deliberate misclassification;
• other policy concerns.

If no suitable reporting option is available for the issue, visit Vahuk Help.

A Report Does Not Guarantee Removal

A report is a signal that something may need review. It is not automatic proof that a rule was broken.

After review, Vahuk may:

• take no action;
• correct part of the Story;
• apply another appropriate moderation action;
• remove the Story in more serious cases.

Several reports do not automatically prove wrongdoing either. Context still matters.

False and Abusive Reports

The reporting system should not be used as a weapon against another member.

Examples of report abuse include:

• retaliatory reporting after a disagreement;
• mass-reporting a competitor;
• coordinated false reports;
• repeated reports with no genuine basis.

Report abuse may itself be reviewed under the Spam & Abuse Policy.

Possible Moderation Actions

Vahuk does not need to apply the same response to every problem.

Depending on the situation, possible actions may include:

• taking no action;
• correcting Story metadata;
• changing or removing Genres;
• correcting Tags;
• rejecting a submission;
• holding a Story for review;
• removing a duplicate Story;
• removing a Story whose source no longer works;
• unpublishing or removing a Story;
• restricting search indexability;
• removing artificial votes or reactions;
• correcting User Karma or Story Karma;
• adjusting contributor trust;
• restricting a source domain;
• rate-limiting activity;
• restricting an account;
• suspending an account in serious or repeated cases.

The response should depend on what actually happened rather than forcing every case into the same penalty.

A Story Can Be Noindex Without Being Removed

Search-engine indexability and publication are separate decisions.

A Story may remain available to Vahuk users while Vahuk asks search engines not to index it.

This can happen when a Story does not meet Vahuk’s current search-quality or indexability standards.

Possible considerations may include duplication, content quality, integrity concerns, insufficient value for search users, or temporary review status.

Noindex is therefore not always a punishment. It can simply be an SEO and quality-control decision.

When a Story May Be Removed

Story removal may be appropriate when keeping the Story would create more harm or clutter than value.

Examples can include:

• a malicious source;
• a permanently broken source;
• a duplicate Story;
• serious spam;
• a deceptive destination;
• a source that no longer contains meaningful content;
• a serious policy violation;
• activity forming part of a larger abuse campaign.

Account Restrictions

When a problem extends beyond one Story, Vahuk may need to review the account itself.

Account restrictions may be considered for patterns involving:

• repeated spam;
• fake engagement;
• moderation evasion;
• malicious submissions;
• coordinated account networks;
• harassment;
• technical abuse.

The type and duration of a restriction can depend on the seriousness and history of the behavior.

Rate Limiting and Technical Protection

Not every moderation action concerns published content.

Vahuk may rate-limit or restrict activity that threatens the reliability of the service.

This can include:

• excessive automated requests;
• suspicious submission bursts;
• brute-force behavior;
• abusive scraping;
• repeated expensive requests without a legitimate reason;
• attempts to degrade Vahuk’s availability.

Technical protection may occur independently of a Story moderation decision.

Serious or Urgent Cases May Be Handled Quickly

Some situations create enough risk that waiting for a longer review would not be appropriate.

Vahuk may take faster protective action when there is a credible concern involving:

• malware;
• phishing;
• fraud;
• account compromise;
• credible threats;
• severe harassment;
• automated attacks against Vahuk;
• other urgent safety or infrastructure risks.

A Story, source, account, or activity may be restricted first and reviewed further afterward when immediate protection is reasonably necessary.

Moderation Should Be Proportionate

Not every problem deserves the same response.

When appropriate, Vahuk can consider factors such as:

• how serious the issue is;
• whether it happened once or repeatedly;
• the account’s broader history;
• whether the behavior appears accidental or deliberate;
• the harm caused;
• whether the problem was corrected;
• whether the same behavior continued after correction.

A typo, an accidental duplicate, and a coordinated spam campaign are not the same problem.

Honest Mistakes and Deliberate Abuse Are Different

Ordinary mistakes can happen.

Examples include:

• choosing the wrong Genre;
• accidentally submitting a duplicate;
• writing an incorrect title;
• submitting a URL that happens to be temporarily unavailable;
• misunderstanding how a Vahuk feature works.

More serious abuse can include:

• repeated attempts to bypass duplicate detection;
• fake accounts;
• coordinated voting;
• domain flooding;
• malicious links;
• repeated attempts to bypass restrictions or moderation.

See the Spam & Abuse Policy for more detail.

Repeated Behavior Matters

A pattern can provide more useful context than one isolated action.

This can matter when reviewing repeated:

• duplicate submissions;
• domain flooding;
• off-topic Genre selection;
• voting manipulation;
• automated activity;
• moderation evasion.

Continuing the same behavior after a rejection, correction, or restriction may be treated more seriously than the first occurrence.

Do Not Evade Moderation

Trying to work around a moderation action can create a separate integrity problem.

Moderation evasion can include:

• creating another account after a restriction;
• resubmitting a removed Story through an alternate URL;
• switching domains to continue the same abusive campaign;
• using redirects to hide a blocked source;
• moving artificial engagement between accounts;
• exploiting technical weaknesses to avoid platform controls.

If you believe an action was incorrect, use an available review or help channel instead of trying to bypass it.

Moderation Decisions Can Be Reviewed or Corrected

Neither automated systems nor human moderation are perfect.

Where an appropriate review or contact option is available, members may provide missing context or report a possible error.

Reasons for reconsideration may include:

• a factual misunderstanding;
• a technical error;
• incorrect duplicate classification;
• incorrect domain restriction;
• incorrect Karma adjustment;
• important context that was not previously available.

Use Vahuk Help for the currently available support or review options.

False Positives Can Be Corrected

A legitimate Story can occasionally be caught by an automated rule or misunderstood during review.

Where appropriate, Vahuk may correct:

• a wrongly rejected Story;
• an incorrect Genre change;
• a false spam classification;
• an incorrect Karma adjustment;
• a mistaken domain restriction;
• another technical or moderation error.

Correcting an error is part of maintaining a fair moderation system.

Vahuk May Keep Moderation and Integrity Records

Vahuk may retain relevant technical and moderation records when needed to understand platform activity and investigate problems.

These records may relate to areas such as:

• moderation actions;
• Story submission failures;
• abuse signals;
• domain decisions;
• technical errors;
• other integrity events.

These records can help Vahuk diagnose mistakes, understand repeated behavior, maintain consistency, and protect the service.

Internal logs, detection details, and security-sensitive information do not need to be publicly exposed.

Why Vahuk Does Not Publish Every Moderation Rule

Vahuk should be transparent about what members are expected to do and the kinds of actions the platform may take.

That does not require publishing every internal anti-abuse formula.

Information that may remain private includes:

• exact spam thresholds;
• contributor trust formulas;
• domain reputation rules;
• automated detection logic;
• submission velocity limits;
• Karma anti-abuse weights;
• ranking and integrity multipliers.

Publishing exact anti-abuse thresholds could turn moderation documentation into instructions for avoiding detection.

Moderation and Search Engines Are Separate

Vahuk controls how a Story is handled on Vahuk. Search engines make their own decisions.

Vahuk may decide whether a Story:

• remains published;
• is available but noindex;
• appears in internal discovery;
• is removed.

Search engines independently decide whether to crawl, index, or rank a URL.

A moderation action therefore does not guarantee a particular result in Google, Bing, or another search engine.

Moderation and Popularity Are Also Separate

A popular Story is not above moderation.

A Story with high Karma, many votes, many reactions, or Trending placement can still be reviewed if a real problem is discovered.

Likewise, an unpopular Story does not automatically violate policy.

Community popularity is one kind of signal. Policy compliance and platform integrity are different questions.

For more about community signals, see Voting & Reactions and How Karma Works.

What to Do If Your Story Is Rejected or Removed

If a Story is rejected, restricted, or removed, start with the information already available to you.

Check the following:

1. Read any message Vahuk provides about the decision.
2. Make sure the source URL still works.
3. Check whether the source already has a Story.
4. Review the selected Genre and Tags.
5. Review the Submission Guidelines.
6. Consider whether the source or domain could be restricted.
7. Do not repeatedly resubmit the same Story without fixing the problem.
8. Use Vahuk Help if you believe an available review or support process is appropriate.

What If My Karma Changes After Moderation?

Moderation can sometimes result in a Karma correction.

This may happen because:

• invalid activity was reversed;
• a technical mistake was corrected;
• an abuse-related adjustment was necessary;
• an earlier incorrect deduction or reward was restored or corrected.

If you believe a Karma change is wrong, use an available support or review process rather than trying to manufacture replacement Karma.

See How Karma Works.

What If a Domain Is Restricted?

If Vahuk rejects a source because of a domain restriction, repeatedly trying alternate versions of the same URL is not the solution.

Instead:

• stop retrying the same destination;
• read any submission message that was provided;
• review the Spam & Abuse Policy;
• use Vahuk Help if there is a legitimate reason to raise the issue.

Frequently Asked Questions About Moderation

What can trigger moderation on Vahuk?

Moderation can be triggered by reports, duplicate detection, broken URLs, Genre concerns, domain rules, suspicious submission behavior, artificial engagement, spam signals, malicious sources, automated integrity checks, or manual review.

Does every reported Story get removed?

No. A report is a signal for review, not automatic proof of a violation. Vahuk may take no action if no meaningful problem is found.

Can Vahuk moderate a Story after it has been published?

Yes. New information, source changes, reports, duplicate discoveries, broken URLs, spam signals, or artificial engagement can lead to later review.

Can Vahuk change a Story’s Genre?

Yes. A Genre may be corrected when the Story is misclassified or when taxonomy cleanup is needed. A Genre correction is not automatically a penalty.

Can a Story be removed because its source stopped working?

Yes. Vahuk may periodically recheck source URLs and may remove Stories whose sources become unavailable, invalid, unsafe, or no longer useful.

Can Vahuk remove duplicate Stories?

Yes. Vahuk may block or remove duplicate Story records so community activity remains centered around the appropriate existing Story.

Can votes or reactions be reversed?

Yes. Invalid, artificial, automated, duplicate, or technically incorrect activity may be removed or corrected.

Can Karma be corrected?

Yes. Vahuk may correct User Karma or Story Karma after technical errors, artificial activity, abuse, or another legitimate administrative correction.

Does low Karma mean I am being moderated?

No. A member may have low Karma simply because they spent it through normal participation or have not earned much yet.

Does spending Karma reduce my trust?

No, not by itself. Legitimately spending Karma through Story submissions is normal behavior. Contributor trust considers a broader pattern of activity.

Can high Karma prevent moderation?

No. High User Karma or Story Karma does not provide immunity from Vahuk’s rules.

Can a trusted contributor be restricted?

Yes. Trusted contributors are still expected to follow the same platform rules. Serious or repeated problems may lead to restrictions regardless of previous trust.

Can a trusted domain be blocked later?

Yes. A domain’s status may change if it becomes compromised, changes ownership, begins redirecting to unsafe content, or develops serious spam or abuse problems.

Can Vahuk noindex a Story without deleting it?

Yes. A Story can remain available to Vahuk users while being excluded from search-engine indexing when it does not meet current search-quality or indexability standards.

Does a negative vote mean a Story will be removed?

No. Negative votes are community feedback. They do not automatically prove that the Story violates a rule.

Can I question a moderation decision?

Where an appropriate support or review method is available, you may use it to provide missing context or report a possible error. Visit Vahuk Help for current options.

Can a moderation mistake be corrected?

Yes. Vahuk may correct false positives, technical mistakes, incorrect Karma adjustments, mistaken domain restrictions, or other moderation errors when appropriate.

Why doesn’t Vahuk publish every moderation threshold?

Some anti-abuse details remain private because exact thresholds could be used to design activity that stays just below enforcement limits. Vahuk explains expected behavior publicly while keeping sensitive detection details private.

Moderation Should Protect Discovery, Not Replace It

Most normal Vahuk activity should never need moderation.

Moderation exists for the cases where something stops being useful, safe, genuine, or consistent with the rules that keep the platform working.

When a problem does occur, Vahuk can consider the context, severity, history, repetition, and whether the behavior appears accidental or deliberate.

For related guidance, read the Community Guidelines, Submission Guidelines, Spam & Abuse Policy, Voting & Reactions, and How Karma Works. You can also visit Vahuk Help for the main documentation hub.