RSSNext / RSSNext/Folo

Desktop Windows: Embedded YouTube player shows anti-bot sign-in message, and the in-app "Sign in" link does nothing

Open
#4,967 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Title: Desktop Windows: Embedded YouTube player shows anti-bot sign-in message, and the in-app "Sign in" link does nothing

Description

On Windows desktop, YouTube videos embedded inside Folo cannot be played in-app.

Instead of playing, the embedded player shows a YouTube anti-bot message asking the user to sign in to confirm they are not a bot.

The in-app Sign in link inside the embedded player is not functional. Clicking it does not open a usable login flow inside Folo.

Platform

  • Desktop - Windows

Version

  • Folo 1.5.0
Image

Environment

  • Windows desktop
  • Folo main account is logged in normally
  • Default browser can play the same YouTube videos normally

Reproduction Steps

  1. Open Folo on Windows desktop.
  2. Open an entry containing an embedded YouTube video.
  3. Try to play the video inside Folo.
  4. The embedded player shows the anti-bot sign-in message.
  5. Click the in-player Sign in link.

Actual Result

  • The embedded player remains blocked by YouTube's anti-bot/sign-in screen.
  • Clicking the in-player Sign in link does not provide a usable in-app login flow.
  • The video cannot be watched inside Folo.

Expected Result

  • Embedded YouTube videos should play inside Folo, or
  • the in-player sign-in action should open a working authentication flow that resolves the block.

What I already checked

  • Updated to Folo 1.5.0.
  • Folo main account login is normal.
  • Browser can watch the same YouTube videos normally on the same machine/network.
  • Switched system DNS from router DNS to public DNS (8.8.8.8 and 1.1.1.1).
  • Flushed DNS cache and restarted Folo.
  • Verified www.youtube.com resolves to normal public Google IPs after the DNS change.
  • Relaunched Folo with --disable-gpu.
  • The issue still reproduces inside Folo only.

Extra Notes

  • This looks specific to the embedded YouTube/WebView flow rather than the main Folo account login.
  • Earlier, system DNS behavior looked abnormal and once returned a 198.18.x.x fake-IP style result for YouTube, but even after fixing DNS resolution the embedded player still shows the same anti-bot/sign-in screen.
  • The browser is unaffected, which suggests the desktop embedded player / WebView behavior differs from the browser path.

Screenshot

Attached screenshot shows the YouTube embedded player anti-bot sign-in message.

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

Start by locating the Windows desktop embedded YouTube/WebView integration and reproduce the issue using the listed steps. Compare the in-app player and sign-in behavior with the normal browser flow; done means the video plays in Folo or the in-player sign-in action opens a usable authentication flow.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.