this post was submitted on 14 Nov 2023
199 points (100.0% liked)
Technology
37711 readers
157 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
view the rest of the comments
Apparently it was a bug:
https://reddit.com/r/help/comments/17vbxz8/whoa_there_pardner_error_message/
It's not a bug. It's them running A/B tests to completely block mobile users that aren't on the app. They've been implementing different versions of this for over a year now. They always lie about what it was. Actually they pretty much habitually lie about all of their tests and changes.
https://en.wikipedia.org/wiki/Hanlon%27s_razor
I got this bug on desktop, running chrome, with no VPN.
This was, as most things like this are, just a pure dumb fuck-up by some guy putting things on prod without properly testing and staging. No need to put on any more tin foil hats than we already have, the incompetence is plenty reason enough to point and laugh.
Both can be true. The incompetence could have happened while trying to block mobile use.
The amount of dark patterns pushing users onto the app has already established the malice.
If an internet corporation has a history of enshittification, it gets increasingly hard to clock up these kind of things to incompetence. While stupidity can certainly explain some things, it's usually safe to assume it's a bit of both