this post was submitted on 21 Jun 2023
302 points (100.0% liked)
Technology
37604 readers
245 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think it also important to note that it wasn't just the pricing itself, which was indeed already heinous, but that the rate calculation changed. It used to be a rate per user per app (apikey+oauth) but they changed that to just the per app ... that then has a multiplicative effect on the costs and makes the "free tier" they were talking about especially pointless....
It would be easy for an app to start at free tier ... not have much growth through word of mouth but enough given the per app rates to push it over boundary points ... and then be due a significant and unavoidable invoice in a couple of months...
The rate is $0.24 per 1000 API calls. You are thinking about the "free tier". Before, all calls were free, and even if there were per-app/per-user limits buried in the docs they were not enforced. After the announcement there was some confusion about whether the new "free tier" limits are per-user or per-app, and turns out they are indeed 10 calls/minute per app! The free tier is for developer testing basically, it cannot be used for a mass market app. So the rate calculation hasn't changed, it was introduced to kill off free apps.