TeamNewPipe / TeamNewPipe/website

Change comment system?

Open
#292 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
158
Forks
43
PR merge metrics
No merged PRs in 30d

Description

Looking at the comment system, I had 3 specific questions:

  • Why does it look like being stuck in the late 90s?
  • Who actually offers this comment system?
  • Where is the info (Comments, username, etc) stored?
  • Can I access the data if needed?
  • Why can I not properly count?

I am well aware that the provider of this comment system is mentioned in the Privacy Policy of the NewPipes website, but it doesn't eliminate the other questions... Primarely one those focused around privacy and transparency.

Because of this would I like to propose a possible change to giscus.

Benefits (Taken from the site itself):

  • Open-source
  • No tracking or ads and always free
  • No database required. Info is stored within discussions.
  • Custom theme support
  • Multiple languages available
  • Highly configurable
  • Automatically fetches new comments and edits from GitHub

Downsites:

  • Requires a GitHub Account to comment. You also need to authorize the github app to write in your name.
  • Requires the addition of the github app to the repository used for the comments.
  • Requires Discussions to be enabled in a public repository (I don't see it as downside... but you never know)

This is obviously all up to you guys, but I hope you consider it (if you haven't already).

Contributor guide

No contributing guide indexed for this repository

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

Review the current comment provider and the site's Privacy Policy, then compare their data storage and access details with giscus's GitHub Discussions requirements. Done means the privacy and transparency questions have clear answers and the project has a documented decision about whether a comment-system change is warranted.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.