As an owner of multiple servers running in Alpha and Classic, I've been hoping for a long time that this issue would get resolved and make security much better. After a certain point, you can't really do anything else to make a server secure, and it's infuriating how incredibly simple the fixes are. Mojang, please take 15 minutes out of your day to resolve this issue.
I'm glad to see that there is hope we may finally get name verification back in OG versions! As a servee owner I was definitely excited to see that update. Good to know that we've got a definite timescale now.
At the moment it really does just feel like they aren't really planning on doing it and are simply going to continue pushing it back each time a deadline passes. I welcome the idea that they're just busy and haven't gotten around to it, but it really seems like there should be some degree of this rising to the top of the queue for things to fix after being ignored for so long.
Perhaps we'll be lucky enough to get resolved before we hit 3 years of this issue being open. A time-span of 2 months is at least reasonably specific I guess.
Considering this is simultaneously the most watched and most voted up issue by far, would it be possible for any prominent content creators to cover this issue and draw Mojang's attention as well as the community at large to this? Many of us have watched this issue be pushed back multiple times, but the fact this hasn't received an update to even acknowledge a new date to look into it in around half a year is concerning for the prospects of this simple fix ever being implemented.
This has just been closed as a duplicate after nearly 4 years and having another issue closed as a duplicate of this one. What does this duplicate and is the issue going to be resolved? We haven't previously been given any status updates on the state of this in close to a year as well. Could we be given some transparency on what's going on?
Will this issue be moving to the new system when the migration takes place? Considering that the original reporter was removed from the post, there isn't anyone to provide consent to have the bug report automatically transferred. We've been following this and waiting for well over five years now, and I don't want to see it just disappear off the system.
As an owner of multiple servers running in Alpha and Classic, I've been hoping for a long time that this issue would get resolved and make security much better. After a certain point, you can't really do anything else to make a server secure, and it's infuriating how incredibly simple the fixes are. Mojang, please take 15 minutes out of your day to resolve this issue.
I'm glad to see that there is hope we may finally get name verification back in OG versions! As a servee owner I was definitely excited to see that update. Good to know that we've got a definite timescale now.
At the very least I'm glad to hear that this hasn't been scrapped and might happen at some point.
At the moment it really does just feel like they aren't really planning on doing it and are simply going to continue pushing it back each time a deadline passes. I welcome the idea that they're just busy and haven't gotten around to it, but it really seems like there should be some degree of this rising to the top of the queue for things to fix after being ignored for so long.
Perhaps we'll be lucky enough to get resolved before we hit 3 years of this issue being open. A time-span of 2 months is at least reasonably specific I guess.
Considering this is simultaneously the most watched and most voted up issue by far, would it be possible for any prominent content creators to cover this issue and draw Mojang's attention as well as the community at large to this? Many of us have watched this issue be pushed back multiple times, but the fact this hasn't received an update to even acknowledge a new date to look into it in around half a year is concerning for the prospects of this simple fix ever being implemented.
This has just been closed as a duplicate after nearly 4 years and having another issue closed as a duplicate of this one. What does this duplicate and is the issue going to be resolved? We haven't previously been given any status updates on the state of this in close to a year as well. Could we be given some transparency on what's going on?
Will this issue be moving to the new system when the migration takes place? Considering that the original reporter was removed from the post, there isn't anyone to provide consent to have the bug report automatically transferred. We've been following this and waiting for well over five years now, and I don't want to see it just disappear off the system.