Skip to content

Conversation

@conxtantyn
Copy link
Contributor

@conxtantyn conxtantyn commented Jan 12, 2026

Context

This change ensures that users clearly understand when a post has been flagged as illegal and why interaction with it is restricted. The goal is to remove illegal content from discovery surfaces while preserving transparency on the content owner’s profile. This approach balances compliance requirements with user clarity by explicitly labeling illegal posts and enforcing strict interaction limitations. It also prevents further amplification or monetization of illegal content.

Description

Posts flagged as illegal are now excluded from the feed, search results, and all filter-based discovery mechanisms. These posts remain visible only on the content owner’s profile, where the post title, content, and description are hidden and replaced with a visible label “Removed as illegal”.

Illegal posts cannot be interacted with in any way: they cannot be liked, disliked, commented on, viewed, shared, promoted, or reported again. Existing interaction metrics (likes, comments, views) are no longer displayed, and illegal posts do not reward gems. Access via consent-based mechanisms or web toggles is explicitly blocked.

Links

@github-actions github-actions bot added android assets documentation Improvements or additions to documentation tests labels Jan 12, 2026
@conxtantyn conxtantyn changed the base branch from development to constantine/feature/commentReporting January 12, 2026 08:22
Base automatically changed from constantine/feature/commentReporting to release-v1.11.0 January 15, 2026 10:23
@conxtantyn conxtantyn merged commit 307e139 into release-v1.11.0 Jan 15, 2026
11 checks passed
@conxtantyn conxtantyn deleted the constantine/feature/illegal-post branch January 15, 2026 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

android assets documentation Improvements or additions to documentation tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants