this post was submitted on 01 Jul 2023
587 points (99.8% liked)

196

16745 readers
2199 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 2 years ago
MODERATORS
moss@lemmy.blahaj.zone
greembow@lemmy.blahaj.zone
moss@lemmy.world
queue@beehaw.org
funky_rodent@lemmy.blahaj.zone
PeachyMcPeachface@lemmy.blahaj.zone
threegnomes@lemmy.blahaj.zone
greembow@lemmy.world
remotelove@lemmy.ca
Roflmasterbigpimp@feddit.de
qaz@lemmy.world
A_Very_Big_Fan@lemm.ee
qaz@lemmy.blahaj.zone
qaz@lemmy.ca
A_Very_Big_Fan@lemmy.world
qaz@lemmy.dbzer0.com
Qaz@lemmy.ml
qaz@sh.itjust.works
qaz@lemmy.sdf.org
587
Rule, nail in coffin (lemmy.blahaj.zone)
submitted 2 years ago by Linuxduck@lemmy.blahaj.zone to c/196@lemmy.blahaj.zone
95 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] thurstylark@lemm.ee 6 points 2 years ago (1 children)

Less servers able to serve requests means either get overloaded and have downtime, or rate limit and stay up.

Both are bad, but rate limiting is less bad.

[–] catastrophicblues@lemmy.ca 1 points 2 years ago (1 children)

I see, I guess at that scale API requests add up. I suppose it is a solution, and if replies don’t count, the limits are rather reasonable.

[–] thurstylark@lemm.ee 3 points 2 years ago* (last edited 2 years ago)

Yeah, exactly.

Also worth mentioning, the scale of Twitter also means that they have contractual obligations when it comes to uptime (for advertisers etc), so downtime could be very costly indeed.