NewPipeExtractor VS WebKit

There's this thing called NewPipeExtractor, which scrapes a lot of details from YouTube like videos, comments, and channels. But using it is a bit of a hassle since it requires implementing some abstract class, and its documentation is hard to understand.

For example there is https://github.com/TeamNewPipe/NewPipeExtractor which allows downloading videos. there is https://github.com/massgravel/Microsoft-Activation-Scripts which activates Windows, I have tried and it works.

As for native support, it seems the issue for it exists but is pretty quiet so you may want to subscribe to it or lobby for some progress: https://github.com/TeamNewPipe/NewPipeExtractor/issues/690

See https://github.com/TeamNewPipe/NewPipe/pull/8837 and https://github.com/TeamNewPipe/NewPipeExtractor/pull/904 for pull requests with this feature. The extractor PR is also needed for LibreTube (as LibreTube depends on Piped which depends on our extractor).

For an example the youtube/streaming front-end android client NewPipe and its associated "backend" NewPipeExtractor has a lot of machinary to emulate what javascript does in your browser when you ask it to play a video/stream from various websites (most notably youtube). It does take a lot of effort, which is why it often goes into periods of quiet development as the previous maintainers burn-out and new ones take over. But it isnt impossible, but modern websites do not let go of thier content easily. Also note that even this is only read-only, there isnt a mechanism to allow you to post.

NewPipe Team's commits were crucially helpful in resolving the issue. TeamNewPipe/NewPipeExtractor#960 (https://github.com/TeamNewPipe/NewPipeExtractor/pull/960) THANKS SO MUCH, NEWPIPE TEAM!

You should indeed see them, that's a bug. I opened a new issue for this with some technical details: https://github.com/TeamNewPipe/NewPipeExtractor/issues/1017.

Multiple engineers are working on adding it back: https://github.com/WebKit/WebKit/pulls?q=is%3Apr+is%3Aclosed...

Since 2023 Chrome announced the View Transition API, and it looks like Safari is also going to support it soon.

One heap per type.

Here’s an allocator optimized for that use case.

https://github.com/WebKit/WebKit/blob/main/Source/bmalloc/li...

To use this in Bun, you’d have to start Bun with the environment variable “BUN_JSC_useDollarVM=1” and then $vm.createBuiltin(mySourceCodeString)

When using this intrinsic, if any of the arguments are incorrect or it cannot otherwise enable it, the entire process will probably crash. In debug builds of JSC it will have a nicer assertion failure but that is not enabled in release builds

Example code: https://github.com/WebKit/WebKit/blob/17351231b4dedb62d81721...

also happy to answer any questions about Bun

Ah, good, let me introduce you to the wonderful world of the Chrome Devtools Protocol! (fka Chrome Remote Debugging Protocol)

I love this API for almost everything browser related. I built my RBI product atop this (BrowserBox: https://dosyago.com), and I think it's a drastically underrated API.

Also, it works out of the box in Edge, Brave, Chromium, and many parts of CRDP are supported by Firefox and Safari^1

1: See for example: https://github.com/WebKit/webkit/tree/main/Source/JavaScript...

No, it's unrelated.

https://github.com/WebKit/WebKit/commit/064df1a9f395f8c6e32c...

It's being worked on now: https://github.com/WebKit/WebKit/pull/17320

It is different. The cross-site navigation flag is a couple of years old. It was enabled by default for iOS in November 2018 for example https://github.com/WebKit/WebKit/commit/e191fc8c412850cb9fd0...