Twitter is refusing to pay Google for cloud services. Here’s why it matters, and what the fallout could be for usersBriongloid@aussie.zone to Technology@lemmy.world – 15 points – 1 years agotheconversation.comWith the Twitter limits today, I think we are already seeing the fallout begin. It took me 3 minutes of slow loading to get this and this. It's been over half an hour now and I still have a blank twitter page, what if today is the day twitter actually goes down.12Post a CommentPreviewYou are viewing a single commentView all commentsShow the parent commentThat could explain the limits today and changing APIs, blocking Nitter and users not logged in...The login-block appears to be exasperating the issue, by creating a pull loop, they are DDOS-ing themselves. ~source They turned off non logged in people, to save resources and it caused the opposite effect, too bad they fired all those developers.Oh good grief. I thought you were exaggerating.
That could explain the limits today and changing APIs, blocking Nitter and users not logged in...The login-block appears to be exasperating the issue, by creating a pull loop, they are DDOS-ing themselves. ~source They turned off non logged in people, to save resources and it caused the opposite effect, too bad they fired all those developers.Oh good grief. I thought you were exaggerating.
The login-block appears to be exasperating the issue, by creating a pull loop, they are DDOS-ing themselves. ~source They turned off non logged in people, to save resources and it caused the opposite effect, too bad they fired all those developers.Oh good grief. I thought you were exaggerating.
That could explain the limits today and changing APIs, blocking Nitter and users not logged in...
The login-block appears to be exasperating the issue, by creating a pull loop, they are DDOS-ing themselves. ~source
They turned off non logged in people, to save resources and it caused the opposite effect, too bad they fired all those developers.
Oh good grief. I thought you were exaggerating.