This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.
Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.
We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:
-
Shaming.
-
Attempting to 'build consensus' or enforce ideological conformity.
-
Making sweeping generalizations to vilify a group you dislike.
-
Recruiting for a cause.
-
Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.
In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:
-
Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.
-
Be as precise and charitable as you can. Don't paraphrase unflatteringly.
-
Don't imply that someone said something they did not say, even if you think it follows from what they said.
-
Write like everyone is reading and you want them to be included in the discussion.
On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.
Jump in the discussion.
No email address required.
Notes -
These measures would be extremely, two orders of magnitude, too harsh for a well-run social media site responding to scraping. Twitter doesn't have it any worse than every other site, and they accept some scraping and can identify bots and ratelimit excessive load. Limiting most of twitter's real users to just half an hour of use per day is absurd, I can't think of any situation that would call for it.
(roughly) For scraping to really harm twitter this much, it'd have to be significantly higher-load than twitter's real users as a whole. And requests = (requests/users) * users, so if all requests are from authenticated users (after login wall but before this) and scrape_requests >> real_requests, either the scrapers are making many more requests than real users per user (in which case a much less strict limit works), or there are many more scraping users than real users - very unlikely because creating accounts is hard (maybe requiring unique phone numbers), because it wasn't 'no ratelimit for accounts created before 2020', and because that many bot accounts would be noticed and could be distinguished from real users.
If it's just covering for an outage ... that'd be a 12-hour long outage at this point. When Facebook has an outage, let alone a 12-hour long one, they don't lie about the cause and only communicate it via the totally-not-CEO's personal account on the site with the outage. Twitter's status page is still green.
What must Tucker on Twitter be thinking now, or anyone else in or contemplating a professional relationship with twitter? The advertisers they're trying to court? The $1000/mo gold checkmark holders?
I have no good explanation for this decision. (edit: to be clear - if the real reason is scraping, the poor technical decisionmaking - otherwise, the decision to cover for an internal issue by pretending the issue is scraping). Maybe Elon's really on drugs? He put someone incompetent in charge who's feeding him bad information? The deadline for the Google Cloud bill they weren't paying was June 30, i.e. yesterday - supposedly they restarted payments, but maybe they didn't really? Maybe firing so much of Twitter plus all the changes he's made led to a buildup of problems, and this is what he had to do to keep twitter up for now? Idk. Either way, this is a much more significant failure than any of Twitter 2's previous missteps, which still could be explained as part of a high-variance strategy. Burning the credibility of verified, boosting shitty paid replies ... eh, it's bringing in money. Not paying bills ... aggressive approach dealmaking. This is just gross incompetence no matter the explanation.
And, "put any Fortune 500 CEO in charge of America and it'll immediately improve" ... feeling even worse than it did a year ago
Have you read any interviews or heard anyone talk about the twitter code base? It's supposed to be a mess... In the process of trying to fix things, would stuff like this happen, a lot?
It's funny that just about the worst possible assumptions are made because vice said musk bad.
More options
Context Copy link
so I've seen rumors around, and keep in mind these are just rumors, from HN and others that Twitter has been accidentally DDoSing themselves.
in the Twitter UI as of a few days ago (and earlier while looking for more information on a related thing I accidentally confirmed this), it'd start making hundreds of requests per minute to Twitter's servers. now looking through it, I found this
https://sfba.social/@sysop408/110639435788921057
obviously my source is pretty biased, but the self-request spam seems to at least be happening to some extent.
I strongly suspect that, while this happened, it isn't a significant cause of the ratelimits. I also do not have good information though.
The login wall was implemented within a day or so of the ratelimit suggests they have shared causes. I don't think the login wall caused the request spam, just the ratelimit - implying that the login wall couldn't have been caused by the ratelimit. And I think the ratelimit was intentionally imposed.
Also, if that was a primary cause - they've now fixed the request spam, why haven't they removed the ratelimit?
I also think (could be wrong vague memory) the request spam was a bug that existed on twitter months back when one was ratelimited (by the old anti spambot ratelimits that were 100x higher)
More options
Context Copy link
More options
Context Copy link
it's time for a new subscription service -- Twitter Brown, where you get to see all of the tweets. only $12/month
this is getting ridiculous. there has to be a better way than this
More options
Context Copy link
I'll be concerned if these limits last longer than a couple of days. I doubt the GCP stuff is related (even the article you link connects it to Twitter Trust & Safety while this outage is affecting Twitter's core infra). FWIW Twitter seems fine for me now. It was severely degraded for a few hours on both app and web earlier but looks to have improved. I suspect someone fucked up deploying the new login-wall and they're running damage control, and possibly using the situation to run some experiments (or as leverage for their negotiations with API customers). This is the first major service interruption since Musk's takeover and (unless it persists!) I really think you're catastrophizing too much. I mean, Reddit was completely unusable for several days just a couple of weeks ago (though that was due to managerial incompetence rather than technical); 12 hours of degraded service is a bad look for a major tech company but hardly apocalyptic like you seem to imply.
If the rate limit is covering for the outage / GCP / etc, 'the rate limit still existing' means the issue is still ongoing because Twitter's still losing money
I agree, should've made that clearer - a 12 or 24-hour outage is bad, but not unprecedented, tech is incredibly complicated and it can happen without any mistakes on Elon's part. Facebook was down for 24 hours in 2019, Roblox was down for three days at some point, etc. The very-bad part is that it's either totally unnecessary (combatting scraping) or they're lying about it (internal outage, GCP issue, etc). When Facebook has a long outage, they have clear updates on the status page every hour. Again, imagine you financially depend on Twitter, just got ratelimited, and now have to look at screenshots of Elon's tweets and guess if he's being honest or not, guess when the ratelimits are disappearing, etc.
And the weirdness of the cause, unfortunately, significantly increases the likelihood of the rate limit persisting.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link