It's apparent SE doesn't care that non-JP servers are encountering 2002 issues

[Krotoan]

people have talked and warned about the issue since 2.0, throughout stormblood, yet obviously nothing happened till now
if they weren't aware of the issue then it clearly means they do not value any english speaking communities unless they make enough noise

This doesn't necessarily follow but I can see how some people would get the idea. If you're running a service and a small amount of people on the forums complain about something that only happens in a rare condition (server queues being full for days on end) and your techs say that it's because their net connections are bad (this isn't the sole reason but it DOES contribute and is likely what the team was told) you probably aren't going to react that strongly to it. I don't believe anyone has ever looked as deep as they have in this case, they just went "we hate 2002 errors" to which SE replied "your connection might be/is the problem" and the subject wasn't pursued further because soon after queues would lessen and nobody would care again.

, which isn't a good thing, not to mention that their first response to the 2002 error was that it's most likely an issue on the users end instead of theirs, which makes me think that they didn't really look into the problem in the first place until it became too big, or, if they were, still shifted the blame onto the user instead of being transparent about it, which is what they should've done in the first place

Technically if everyone's connection was perfect there would be no 2002 problem. As far as I can tell from everything everyone has revealed, SE and the users combined, is that every 15 minutes there is a very sensitive reconnect that happens. If your connection drops any part of that connection, the game considers you disconnected. The REACTION to that and followup protocol sucks and is poor coding it seems. However what I can assume happened, was the techs on SE's side all saw the server shooting back "this guys connection is dead, drop him" and assumed the cause was the users (something that's pretty common everywhere: nobody wants it to be their thing breaking). THIS finding was relayed to the "mouthpieces" of the FFXIV team and is what was announced. They were as transparent as they could have been, though maybe not as diligent. It's fair to say it was something that could have been fixed a long time ago, but it also has to be understood that until the perfect storm of problem happens, it wouldn't have been a priority in any company.

I apologize if you think a joke at the expense of people who go to some lengths to defend a corporation with excuses that have nothing to do with the issue at hand as 'ranting'

I think any further umbrage thrown their way is just salting wounds and sowing discord.

in addition to that, you can see at the bottom of my quoted post that I'm glad they're working on fixing this issue now, so what do you want me to say? I'm happy that they acknowledged it was on their and not the user's end, as they should've done (and known tbh) in the first place

I think acknowledging that the company is doing the "right" thing with the information it has now and how they made a choice to act on user given information instead of ignoring it and continuing to blame throw is far more important than further shade.