I've created a thread to collect data regarding to this issue:
Please use the template provided, this data will all go to the devs which hopefully will speed up the process.
The thread I linked has been closed, enough data has been collected.
Thanks to everyone that had chimed on and shared their data.
They'll be investigating this issue, though as far I'm aware, there's not much known on when there'll be some new development on the situation.
What? No, not at all. No one has responded to this aside from the initial page. I want this thread to stay open until it becomes an issue and draws actual attention not just a fast paced PR/HR response that nothing comes of.
The thread I linked in my post was intended for data collection.
They had received enough data so they had decided to close that thread.
That thread wasn't really intended for raising awareness or discussion, just information for the developers.
This thread however will probably stay open for discussion, support or however you seem fit.
I'm pretty sure there is no reason to close this exact thread we're currently posting it, as it's still relevant.
Technically this isn't really a PR/HR response from them, they've mentioned to me that there wasn't enough movement on the matter to really make a statement on it.
I myself had started a thread to help a dev that requested some data so he could look into it, this caused a bit of a hassle as it might've looked like an official statement.
I'm sorry if that caused some confusion, it was pretty much out of own initative to help with the process, though so far there hasn't been enough progress on the matter to really announce anything.
I can assure you they're looking into it, though I cannot provide an ETA.
Ah okay that makes sense, is there any way you could contact the previous team responsible for data collection and let them know about this thread? There's quite a sizable pool now of people having the same issue.
