How a Diablo expansion led to behind-the-scenes trouble
1–10 of 80 posts
Re: How a Diablo expansion led to behind-the-scenes trouble
#2Re: How a Diablo expansion led to behind-the-scenes trouble
#3Re: How a Diablo expansion led to behind-the-scenes trouble
#4Re: How a Diablo expansion led to behind-the-scenes trouble
#5Re: How a Diablo expansion led to behind-the-scenes trouble
#6Off topic: the cookie acceptance dialog that polygon uses is broken. It shows a spinner and doesn't disappear. Why does this even need a spinner? I'm seeing similar behaviour on multiple websites now, it's infuriating.
But you cannot see my comment because I was hellbanned, so enjoy wondering.
Re: How a Diablo expansion led to behind-the-scenes trouble
#7It's a mystery how Blizzard then went on to release the failure Diablo 3 is.
Re: How a Diablo expansion led to behind-the-scenes trouble
#8It's a mystery how Blizzard then went on to release the failure Diablo 3 is.
In a way the Diablo 3 RMAH helped validate the modern freemium/gacha business model for mobile platforms.
Re: How a Diablo expansion led to behind-the-scenes trouble
#9It's a mystery how Blizzard then went on to release the failure Diablo 3 is.
Re: How a Diablo expansion led to behind-the-scenes trouble
#10Off topic: the cookie acceptance dialog that polygon uses is broken. It shows a spinner and doesn't disappear. Why does this even need a spinner? I'm seeing similar behaviour on multiple websites now, it's infuriating.
GDPR requires you to “prove” you gained consent by creating a server-side timestamped log of the option each user chooses. But you cannot see my comment because I was hellbanned, so enjoy wondering.