You actually do not need to ask how AI could read how an code works.

Because basically you are asking the AI to read an computer languange, that the AI already understand

It's almost the same as asking your friend that knows physics about how Newton's 1st Law works

The impatient - 3.0.4
Release: 3.0.4
- Backend: Fix backend Range bug
- search.ejs: Do not show channel metadata if there's no data about it.
- Backend: Use my fork of ytsr - watch.ejs: Hide author avatar in related videos section if unavailable
- Backend: NO_CACHE support
- Backend: Proxying M3U8 and HLS chunks support introduced

Signed-off-by: Yonle <yonle@lecturify.net>

Did you know that somebody did commanding crawler bot to crawl ytmous.yonle.repl.co ?

Even i added tag to not crawl or even robots.txt, The bot did not listen anyways.

It's crawled so bad that even the old ytmous mirror is getting crawled

(Don't tell me that this is the reason why Heroku shut down it's free plan?)

Pros:
- The crawler could help me find bugs

Cons:
- My instance resource or even bandwidth could cost a lot than what i expect

There seems to be a memory leak in package side, Could be in ytdl, ytsr, ytpl, or even miniget

I am suspecting miniget for some reasons

miniget is not the one that has problem.

Tested with 200 requests to 15 MB of files already (15 * 200 = 3000 MB traffic).

Now i am suspecting ytdl-core

As i expected. ytdl-core

But as far as i could get, this seems to be node issue itself. As i saw multiple issues that pointing to node v16

If you want to run ytmous, Use the stable release ones.

But if you want to try something unstable, You could clone master or nightly

You said you want to get rid of softwares that tracks your activities.

But you are still using Discord that tracks your activities for your status.

How Lame!

Here's a tip if you want to hide something like "People also watched", or "Shorts"

100+ JavaScript function calls per seconds of doing this kind of tasks.