"API" bullshit.

To web service providers:

Don't make me register for an "API key" or whatever you call it just so you can get my personal info and log, throttle, or charge for my requests for a subset of the data that I can already get freely via your app or website. Don't spread the misconception that your "developer API" is the only way to get at your data.

To "developers":

Don't beg and whine for an API when you can just use your fucking browser or their app to see the data already. Learn what View Source can do for you. Don't be mislead by web service providers who peddle their stupid API bullshit just so they can exert more control over you.

>>32,39
Those changes are easy to handle. Once you've written a scraper that extracts what you want, updating it for a new site structure is just a matter of changing a few paths and expressions. Scraping becomes difficult when the site appers make things deliberately hard for your bot. Like randomizing the html structure of the page or captchas. The other time when its hard is when the appers can't produce valid html, or the data isn't organized in any reliable way.

I pictured >>39 as a child in a plastic high set at a table in a fast food restaurant throwing opened packets of mustard and ketchup at me as he said that.

Smoke weed everyday

>>30
The API is rarely documented and usually hidden in megabytes of Javashit cruft. I once tried to reverse https://volafile.io's API, it was awful.

>>43
Just stay determined. Reverse engineering is tedious but it has a reward to it. Like checking these sweet dubs.

>>43
Protip: look at the requests being made, it's usually obvious from that.

Protip: Cudder is all talk and no action

Posting in a shit thread! :^)

　　　　　　　　Shitty thread Wasshoi！！
　　　　　＼＼　Shitty thread Wasshoi！　／／
　+　　　+　＼＼Shitty thread Wasshoi！／+
　　　　　　　 ∬ ∬　　　 ∬ ∬　　　 ∬ ∬　　+
　　　+　　　　 人　　　　　 人　　　　　 人　　　　 +
　 　 　 　　　（＿_）　　　 （＿_）　　　 （＿_）
　　+　　　　（＿＿）　　 （＿＿）　　 （＿＿）　　　　　+
.　　　+　　 （ ＿＿ ）　 （ ＿＿ ）　 （ ＿＿ ）　　+
　　　　　　（　´∀｀∩　（´∀｀∩）　（　´∀｀）
　+　　（(　（つ　　　ノ　（つ　　丿　（つ　　つ　)）　　+
　　　　　　 ヽ　 （　ノ　　（　ヽノ　　　）　）　）
　　　　　　　（＿）し'　　し（＿）　　（＿）＿）

>>47
:^)

JACKSON 50 GET

Does this thread come with an API??

>>51
Look at the URLs, the HTML, and use your brain.

>>52
...while minimizing brain use.

If I wrote a web browser it would have built in and cached API for all websites it visits.

>>54
Cudder would write a web browser but Cudder is all talk and no action!

so you can get my personal info and log, throttle, or charge for my requests

and you think they aren't doing that when you GET their webpages? lol. if they give you an API, you can still hide behind a VPN and give them a fake name/pay with a prepaid debit card.

Learn what View Source can do for you.

most websites are migrating to being fully Javascript rendered e.g., React. to use that you'll need browser automation. so in addition to whatever parsing code you need, you'll have to pull down most of WebKit (or whatever) just to extract a little bit of data on a web page. G-d help you if they randomly change one of the CSS selectors.

it's just an extremely brittle design. most people need on-demand, reliable data and don't mind paying for access because they're not mentally ill trannies in some Eastern European hovel.