Exciting news for who? Only the site owner is excited that a free resource now requires a subscription
“Yay! Now I have to pay another subscription! I’m so excited! Let’s celebrate with them!” - nobody
Exciting news for who? Only the site owner is excited that a free resource now requires a subscription
“Yay! Now I have to pay another subscription! I’m so excited! Let’s celebrate with them!” - nobody
REST API docs
I think it’s reasonable move. They have Legacy API that cost them a lot of manhours to maitain and they decided to cut on costs and replace it with a new thing. Sadly they decresed amount of api calls from 20 to 5 [needs citation]
I think they don’t have good PR guy to better communicate the change
Subtitles are like 5kb text files, why even limit their downloads in any way?
The overhead isn’t the storage but the request. Processing a request takes CPU time, which can get expensive when people setup a media server and request subtitles for dozens of movies and shows. Every episode of a TV show is a separate request and that can add up fast when you scale it to thousands of users.
If they’re storing them in something like Amazon s3, there is a cost (extremely low, but not free) associated with retrieving data regardless of size.
Even if they were an entirely free service, it’d make sense to put hard rate limits on unauthenticated users and more generous rate limits on authenticated ones.
Leaving out rate limits is a good way to discover that you have users who will use your API real dumb.
Their pricing model seems fucked, but that’s aside from the rate limits.
Money money money moooonnneey
(Mah-nee!)
Electricity aint exactly free. Even if the data they store is minuscule. Servers will pull >300w if you store 10gb or 2000gb.