Yup.They're totally going to pretend that nothing ever happened and never make a statement on it, aren't they?
That's ridiculous.Great news, I honestly don't think this was intentional to begin with.
I don't even care about this. Change the shit. If they try something like this again, hopefully people are loud enough to get it changed again. Why do we want lip service from a corp?They're totally going to pretend that nothing ever happened and never make a statement on it, aren't they?
Caught with their hand in the cookie jar.They're totally going to pretend that nothing ever happened and never make a statement on it, aren't they?
On the flipside, how many people are going to act like they were ever affected by this and will devote considerable mindspace to still flipping their shit out about it going forward?They're totally going to pretend that nothing ever happened and never make a statement on it, aren't they?
How do you know this was an intentional decision and not an unintended bug?
Why in the world would they develop a purchasing app for this that evaluated what they paid for the old one if they didn't intend to collect the back discount?Great news, I honestly don't think this was intentional to begin with.
Always, always voice your frustrations and there's a good chance it'll get resolved.
This is a post from another user but it kinda makes sense to me...
I am shocked that something that could easily get them sued in court was an oversight and not just them being greedy /s
it was pretty obvious that the system was just getting the new subscription by refunding users of their old subscription and purchasing the new one with their wallet + additional needed funds. Hopefully they also offer some way to convert your current time to upper subscriptions by just having less subscribed time on higher tiers, that would solve the second issue with those who stacked.
Until they say otherwise always assume the worst when it comes to shit like this.How do you know this was an intentional decision and not an unintended bug?
Way too many.On the flipside, how many people are going to act like they were ever affected by this and will devote considerable mindspace to still flipping their shit out about it going forward?
On the flipside, how many people are going to act like they were ever affected by this and will devote considerable mindspace to still flipping their shit out about it going forward?
How do you know this was an intentional decision and not an unintended bug?
Great news, I honestly don't think this was intentional to begin with.
If it was a mistake, I don't think it's really far fetched to make an announcement and say they were working on it. In any case, their communication is really shitty.Are we sure that them fixing this isn't a coding error? Maybe we should wait for an official announcement that it's corrected.