Source: https://xcancel.com/dshiatt/status/1840822267737162237
Obviously just damage control but they do seem to be “fixing it”. They must’ve accidentally implemented a feature to get and show image from the newest news post (which is often an ad), accidentally tested and vetted that feature, and accidentally pushed it.
Ah yes it’s always a bug after massive community backlash. If there wasn’t much, it’d have been a test, and if there wasn’t any, it was always intended.
Telling gamers to watch out for Hanlon’s razor would open them to too much harsh reflection of their own mistakes.
yes sure it could’ve been a bug, but can we really believe them that it was?
companies are on a quest to pollute our lives with ads, it’s not a stretch to think it’s bullshit when another attempt to do that is being denied with “whoopsie the new guy wrote the code wrong nothing to worry about here!”
ahhh, companies copying homework from bigots’ dogwhistling tactics? what a brave new world we live in
says something bigoted
receives backlash
“haha guys can’t you take a joke? everyone’s so sensitive nowadays”
Don’t you hate it when there is a bug in your code that magically attracts ads? They just appear without warning or reason.
I’m skeptical whether it was really a bug or not, but I could definitely see how it could’ve been just a bug given the description in the OP. Could’ve also been a “happy accident” they were hoping nobody would complain about.
It’s just a bug.
you don’t get entire functional UI elements accurately populated with appropriate data out of a “bug”. at best its a feature that was being tested internally and never would have made it past that, at worst its something that went live early.
I can see how that’s a bug that it got released if the intended purpose was to do a POC and gauge the reaction from some internal testers.
But even then they were POC-ing that, which is terrible
