this post was submitted on 16 Nov 2023
973 points (93.2% liked)

Mildly Infuriating

35521 readers
652 users here now

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.

I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!

It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means: -No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...


7. Content should match the theme of this community.


-Content should be Mildly infuriating.

-At this time we permit content that is infuriating until an infuriating community is made available.

...


8. Reposting of Reddit content is permitted, try to credit the OC.


-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.

...

...


Also check out:

Partnered Communities:

1.Lemmy Review

2.Lemmy Be Wholesome

3.Lemmy Shitpost

4.No Stupid Questions

5.You Should Know

6.Credible Defense


Reach out to LillianVS for inclusion on the sidebar.

All communities included on the sidebar are to be made in compliance with the instance rules.

founded 1 year ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 119 points 1 year ago (2 children)

REST API docs

Your consumer can query the API on its own, and download 5 subtitles per IP's per 24 hours, but a user must be authenticated to download more. Users will then be able to download as many subtitles as their ranks allows, from 10 as simple signed up user, to 1000 for VIP user.

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

[–] [email protected] 45 points 1 year ago (6 children)

Subtitles are like 5kb text files, why even limit their downloads in any way?

[–] [email protected] 25 points 1 year ago

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.

[–] [email protected] 14 points 1 year ago

Money money money moooonnneey

(Mah-nee!)

[–] [email protected] 12 points 1 year ago (2 children)

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.

[–] [email protected] 2 points 1 year ago (1 children)

Yeah this is absolutely not an insignificant fee. Especially if they have millions of requests... There be plenty of caching solutions to save on this though, especially since they wouldn't change often.

[–] [email protected] 6 points 1 year ago

Oh, I'm pretty sure it's close to trivial. $0.0004 per thousand requests is $400 per billion, or $0.40 per million.
That's as close to insignificant as you can get and still pay attention to. Caching solutions are probably going to end up costing you more in the long run. An HA setup that can handle a billion requests a year is going to cost you at least $100 a month, and still provide less availability than s3.

You don't want unmetered access, but their pricing is unlikely to be based on access rates, and more likely on salary costs and other infrastructure costs, like indexing and search.

[–] [email protected] 2 points 1 year ago

Agreed, they could have done this much more gracefully. Same as the reddit API. Average user? Who cares. Sending millions of requests? Okay we're going to clamp down pretty hard on you

[–] thisNotMyName 12 points 1 year ago (1 children)

a typical (full subtitle) .srt file for a movie is like 100-200 kb - still not much, but 5 is a little off

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

If it's all text, it'd compress quite well, especially since there's likely lots of repeated words. Not to 5kb of course, but I wouldn't be surprised if it had at least a 3x compression ratio with zstd.

[–] [email protected] 7 points 1 year ago (1 children)

Subtitle are like 1h worth of content, why even download more than 10 a day?

They could make it 20 and it wouldn't change much I guess, 10 does seem a bit low, but if they make it 1000/day (which you could argue is "no heavier than one JPEG") they'll have Kodi addons or whatever attempting to auto-download an entire library's worth of subtitles. It's not about the throughput, it's about the processing time of establishing connections, negotiating cyphers, processing a request, hitting a search indexer, etc. All those small costs add up if every day you have thousands of users downloading hundreds of file without giving anything back.

[–] SendMePhotos 2 points 1 year ago

Just start downloading them and using them to create a new platform. Bam!

(I am saying this with 100% ignorance)