this post was submitted on 01 Jul 2023
40 points (100.0% liked)

Technology

37800 readers
478 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

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

I wonder what's actually going on; I doubt it's about "scraping" and "manipulation"

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

This is second-hand, so take it with a grain of salt, but I've seen mention of a bug that sometimes causes the same graphql query to be executed in an infinite loop (presumably they're async requests, so the browser wouldn't lock and the user wouldn't even notice).

So they may essentially be getting DDOS'd by their own users due to a bug on their end.

Edit: better info: https://sfba.social/@sysop408/110639435788921057

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

Ha, that's hilarious. Absolutely not a surprise, though

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

For my money I would bet the issue stems from abandoning Google server hosting, either from arrogance or being unable to afford it.

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

That's my bet too. They weren't hosting the site itself on GCP but they were using them for trust and safety services, and I bet that one of those services was anti scraping prevention with things like ip blocking and captchas, which would explain why scraping suddenly became a problem for them the day their contract ended. It can't be a coincidence.

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

Oh yeah I completely forgot about that particular idiocy, Elmo gets up to so much stupid shit that it's hard to keep track.

But I'd also be willing to bet money on this being somehow at least partially tied to ditching GC, likely due to not being able to pay (at that's what is implied by them refusing to pay the bill.) I guess Elmo thought "how hard can running some servers be? I'm a rokit skientist" and decided to just skip paying the bill as a power move instead of trying to make a deal with Google, and now the remaining developers, ops people etc. – those poor bastards – are paying the price.