News for hackers. Stuff that matters.
Re:Addressing the community about changes to our API by MrThoughtful on Friday June 09, 2023 @02:05PM (#36261632)
I don't understand why the apps in question (Apollo etc) care about the Reddit API and its terms at all.

Those apps are basically browsers. Applications to browse Reddit, right?

Why not use the "html over http" API which every other browser also uses?

Yes, you would have to harden the code a bit so it gracefully deals with the structure of the html changing sometimes. And you would have to update the parser from time to time. But is that such a big problem?

Also: When using the API, how is the free API limit not enough? In TFA it says "100 queries per minute per OAuth client id". That is per user, right? Why does it take more than 100 API requests per minute to use reddit?

Re:Addressing the community about changes to our API by jchw on Friday June 09, 2023 @02:18PM (#36261839)
Something changes one day, and then your app is broken until you update it, causing you to need to rush to fix it, especially if your app has paying customers. This could be a massive, sudden change of any kind since you are effectively an adversary. Bad.

You are behind a firewall designed to cut out bots, and now need to bypass or handle anti-bot CAPTCHA. Again, bad.

You want to provide push notifications, but that requires background polling on a server. Yep, that's pretty bad, since it multiplies the effort AND erases the "basically just a browser" part in one swoop. Now you need to probably pass user credentials to your backend (bad) and scrape on the server, bypassing Cloudflare/etc in a headless manner (bad.)

Reddit shuts down old.reddit.com and cuts off access to NSFW and "edgy" or perhaps just small subreddits except when logged in on official apps. Now you need to scrape from either official iOS/Android APIs where the keys could go invalid at any time, or the JS desktop site which is all JS and XHRs everywhere. The only way to make your app truly behave like the real thing is to carefully set up an actual browser engine and hide evidence that you're using automation, which is a lot harder than you might imagine. Yep, you guessed it. Very, very bad.

For that last thing, Twitch's "integrity check" mechanism is a great illustration of just how user hostile things will quickly become. Twitch integrity check won't even pass for real browsers half the time. It hates Linux users. This is the future you get.

Re:Addressing the community about changes to our API by patwolfe on Friday June 09, 2023 @02:06PM (#36261657)
I think you are vastly underestimating the complexity and inefficiency of doing this for one of the most visited websites in the world.
Re:Addressing the community about changes to our API by MrThoughtful on Friday June 09, 2023 @02:11PM (#36261735)
How is the complexity of parsing html related to how much visits the website has?
Re:Addressing the community about changes to our API by Timon3 on Friday June 09, 2023 @02:15PM (#36261799)
If Reddit doesn't want third party apps, just how long do you think the HTML will stay consistent?
Re:Addressing the community about changes to our API by detaro on Friday June 09, 2023 @02:31PM (#36262052)
> In TFA it says "100 queries per minute per OAuth client id". That is per user, right?

No, it's per app.

Re:Addressing the community about changes to our API by simlevesque on Friday June 09, 2023 @02:10PM (#36261709)
The html can change at any time, breaking things. An API must manage breaking changes.
Re:Addressing the community about changes to our API by jaywalk on Friday June 09, 2023 @02:11PM (#36261732)
> Those apps are basically browsers.

Nope, not even close.

Re:Addressing the community about changes to our API by MrThoughtful on Friday June 09, 2023 @02:21PM (#36261876)
I don't mean web browsers. I mean Reddit browsers. Applications users use to browse Reddit.