Linuxduck@lemmy.blahaj.zone to 196@lemmy.blahaj.zoneEnglish · 1 year agoRule, nail in coffinlemmy.blahaj.zoneimagemessage-square93fedilinkarrow-up1581arrow-down11
arrow-up1580arrow-down1imageRule, nail in coffinlemmy.blahaj.zoneLinuxduck@lemmy.blahaj.zone to 196@lemmy.blahaj.zoneEnglish · 1 year agomessage-square93fedilink
minus-squarecatastrophicblueslinkfedilinkEnglisharrow-up3·1 year agoWhy would that affect these metrics?
minus-squareThurstylark@lemm.eelinkfedilinkEnglisharrow-up6·1 year agoLess 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.
minus-squarecatastrophicblueslinkfedilinkEnglisharrow-up2·1 year agoI 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.
minus-squareThurstylark@lemm.eelinkfedilinkEnglisharrow-up3·edit-21 year agoYeah, 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.
Why would that affect these metrics?
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.
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.
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.