RSSNext / RSSNext/Folo

Folo Subscription Feed Recommending NSFW Content and Privacy Violations

Open
#4,571 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
39k
Forks
2.1k
Avg merge
1d 4h
Merged PRs (30d)
10

Description

Clear and concise description of the problem

Problem Description:

The Folo platform's subscription feed mechanism has been observed recommending unsolicited NSFW (Not Safe For Work) content to users, along with materials that potentially violate privacy rights. This behavior contradicts standard content moderation practices and raises concerns about:

Inadequate Content Filtering: Lack of robust mechanisms to prevent inappropriate content from appearing in subscription recommendations.
Privacy Risks: Potential exposure of sensitive user data or unauthorized sharing of personal information through recommended sources.
Non-compliance with Platform Policies: Absence of clear user controls to flag/block such content, despite industry standards requiring these features.

Expected Resolution:

Implement stricter content moderation algorithms to filter NSFW and privacy-violating materials.
Introduce mandatory user consent (EULA) explicitly prohibiting objectionable content.

Provide real-time reporting tools for users to flag violations, with a commitment to resolve reports within 24 hours.
Conduct a transparency audit on data collection practices related to subscription sources.

Severity: High (Impacts user safety and legal compliance)

Image
Suggested solution

Implement stricter content moderation algorithms to filter NSFW and privacy-violating materials.
Introduce mandatory user consent (EULA) explicitly prohibiting objectionable content.

Provide real-time reporting tools for users to flag violations, with a commitment to resolve reports within 24 hours.
Conduct a transparency audit on data collection practices related to subscription sources.

Severity: High (Impacts user safety and legal compliance)

Alternative

No response

Additional context

No response

Validations
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
  • This issue is valid

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reproducing the subscription feed recommendations and tracing the existing moderation, privacy, consent, and reporting paths. Done would require agreed scope for filtering NSFW and privacy-violating content, user controls, reporting, and the requested transparency audit.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
content, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.