How are private front-ends built without APIs?
How are private front-ends built without APIs?
I'm referring to projects like redlib or invidious.
I was thinking about doing something similar for a local second-hand marketplace and got curious. Redlib seems to use token spoofing to get past rate limits and Invidious doesn't even use the official YouTube API.
The only way I thought of, which would be slow, is to scrape the site (like you would with Beautiful Soup).
Also the legal benefit of scraping the site without the YouTube API is that you haven't had to accept their terms of service.
There's an Android app called GrayJay that got a C&D from Google, and they told Google to kindly fuck off, because they hadn't used any of Google's APIs. Google had no leg to stand on.
Interesting, I didn't know that. Thanks for the info!
It's not very slow to scrape a website. Works quite well. Your app would appear like any other browser to the site. The trouble with that is that it breaks easily when they change something on their site. Doesn't even have to be a malicious change.
It's not very slow to scrape a website. Works quite well.
That's good to know, I'll look into that some more. I was thinking that it might be slow if I'm having to scrape each page, every time a user changes categories (or something similar).
The trouble with that is that it breaks easily when they change something on their site.
I completely forgot about that :(
That's good to know, I'll look into that some more. I was thinking that it might be slow if I'm having to scrape each page, every time a user changes categories (or something similar).
Well, it's as slow as the website you're scraping. Could actually be faster if you don't have to execute a lot of bullshit JavaScript. And for the rest clever caching should help.
In terms of technology you're looking for XSLT, Xpath, CSS selectors and whatever parsers are available for your language of choice. Don't ever attempt to use regex for scraping.
You should look into how the webpage is built. If it's a static HTML webpage pre-rendered on the server, then you would have to scrape the HTML to extract the info.
However, many more "modern" webpages use client-side JavaScript to separately request the actual data from the web server through a REST/HTTP API. This kind of API is not possible to fully restrict, unless they want to require all users to log in for viewing the webpage.
And yeah, if it's built like that, then you'd want to make use of that REST API. You do not need to use JavaScript to call it. Using any HTTP client library in any programming language, or even justcurl, should work just as much.To see, if it's built like that, open the "Network" tab in the Developer Tools of your browser and refresh the webpage.
If it just loads a bunch of HTML, CSS and image files, then it's the static webpage kind. If it sends/receives messages with JSON in the body to URLs without a file-type, then it's likely the REST-API-kind.
RedLib and Invidious hoster here;
I can confirm they do not use any backend API, however this means eventually they (YouTube and Reddit) kick on automatic rate limiting after a while and I have to switch up my vpn connection on my server. it's annoying, but it works if you know a thing or two about proxies and web scraping (the knowledge from scraping can be cross applied to implementing a suitable proxy config)
that said, RedLib's backend token spoofing works a lot better than the Invidious method (Invidious emulates web traffic via Android mobile devices and gets the videos from Google Videos directly, bypassing YouTube for the heavy lifting).
Invidious does have APIs. People host invidious servers and the clients connect to them, similar to piped. I don't know anything about Redlib but it might work the same!
I'm referring to the fact that they don't use or have major rate limits on the APIs that they use for either Reddit or YouTube, respectively.