3 ms·
If we never fell for this awful "API" concept in the first place, we would've never gotten into this situation where discrimination based on user agents and com
by userbinator 3y ago
If we never fell for this awful "API" concept in the first place, we would've never gotten into this situation where discrimination based on user agents and companies effectively mandating what user agent (and by extension, the rest of your hardware and software stack) you can use to access their sites is normalised and even widely accepted.
I wasn't convinced and said this when sites first started promoting and offering "APIs" like it was a new feature, and it's worth repeating again: Every site already has an API and it's 100% free (unless you already needed to pay to get access): HTTP and HTML. Why would I need to register again an "app" (or even register at all if the site is already publicly viewable), and perhaps even pay --- just for the privilege of getting tracked and restricted even more, and to be able to get JSON instead? Fuck that shit.
More frustratingly, people calling things "private API" as if the client for it wasn't something that every visitor to the site would've automatically downloaded and executed. Anything that gets sent to and runs on my machine is fair game for me to read.
https://www.gnu.org/philosophy/right-to-read.html https://www.gnu.org/philosophy/right-to-read.html
- skeltoac 3y agoReminds me of the API that WordPress used for the Blogger-to-WordPress importer way back in the day: replace your Blogger template with a given format that the import script could parse. One of my earliest contributions to open source was an improvement to the format and importer that extended the functionality to bring Blogger comments into WP. Fond memory of the friends I made in the comments of my Blogger site, and the software career that followed.
- dontlaugh 3y agoScraping doesn’t come with any backwards compatibility. Most APIs do.