No. Just no. </thread>

OTP isn't about keeping your session alive though, it is about adding extra security layers when there may be something suspicious going on. The whole idea of implementing these sort of security measures is to allow the server side to make a decision on what to do regardless of what the client side is providing/requesting. If I could just copy a cookie that says I've already entered a OTP and have an active session, it would completely defeat the purpose of it. Even if it required me to re-enter my credentials, if it got past the OTP that would be a big enough security hole. As such, no OTP related data belongs in a cookie, and all OTP logic/data should be server side. Something that would make more sense in this case would be to only prompt OTP once a week (or so) for IP changes that are within the same ISP's address space, and prompt every time only if the IP is outside that ISP or region.

Or better yet, give that one to the killed individual giving the speech.

Because there are people (like) who are inclined to unsub as soon as they get their alts geared. This way they made it impossible to gear up within a month, so subscribers will need to pay for two (or more) months to gear up instead of just one month.

The main reason it is tied to security is because most people typically have one IP for an extended period of time, and login from a new IP can be a red flag for a hack attempt. As far as other services that do it, I know Steam does. It drives me nuts though because I frequently login to my steam account at new places to use the forums, and I am always checking my email to get a new passcode.

I think I can answer most of your questions based on the patch notes and what was in PTS. Post 2.0, you can't earn a single com if you are over the 400 cap, regardless of the source. The overflow cap is only in place for converted coms. No, see #1. No, reason #1 again. And more irritatingly, the converted gear tokens not only have to be under the 400 total cap (even though they should be overflow), but also count towards your weekly 200 cap. IMHO, they should not count towards the weekly cap and BW should add an exception so that they don't count towards the cap before 2.0 goes live. See my post above for more details. Again, unfortunately no. No coms can be earned in anyway, shape or form over 400 once 2.0 hits.

My biggest concern is with the old gear tokens. While we can turn them over for Classic Coms easy enough, it causes us to hit the cap too quickly. IIRC, Campaign tokens gave 150 Classic Coms in PTS. When I turned in two of them in PTS, it caused me to hit my weekly cap of 200, and flushed the remaining 100 down the toilet. This concerns me because my main has over a dozen tokens waiting to be turned in (Most are Columi, but still). This means that I will be hitting the weekly cap for at least 2 months just trying to convert my pre-2.0 gear tokens, and will have no reason to do any of the 50~54 elder game content in that time period. This is true for my primary alts as well, but to a much lesser extent. IMHO, the gear tokens should go towards the one time 800 Com overflow cap, and not towards the weekly 200 Com cap. A dev response would be nice on this one.

I would presume he is doing it for the Steam overlays. You know the social stuff, such as the friends list, web browser, achievement tracker, etc. It would be pretty cool if does work for that, I'll have to try it.

I'd really like to buy a pair as well, but no way I would drop 3mil for them. I know the hands from these particular sets are rare, but if anyone has a sane price they are willing to sell for message me. Btw, anyone have any Bladestorm pieces besides the chest and legs? Bladestorm is the mara equivalent of the Saber Marshal, TD-17A Imperator and TD-07a Panther sets right?

Depends on your phone's screen and contrast. It comes up as black on very, very dark brown on my phone. I have to regenerate 4 or 5 times as if either of the last 2 digits are similar looking, I can not distinguidh them at all. For example, if either of the last 2 are 0,5,6 or 8 then they all look like 8, as I can only make out the bottom eigth of the character. The first 6 digits are on a lighter (Very slightly lighter) background than the last 2, so if I tilt my phone around I can usualy make them out. If this doesn't get fixed soon, I am going to need to drop the app and get a physical key.

Getting myself way off topic here, but all I know is, even with the latest version of VMWare ESXi and an insane amount of tunning, we(my company) can not get the IO throughput out of it that we need. It is typically 15~20% less performing on writes for us than bare metal is. As an benchmark once not that long ago, we setup a dedicated host with only one VM, fully tuned, and it still didn't perform well enough.

I really wish they wouldn't have catered to the whiners and just would have done a forced merge to begin with. The way that FFXIV merged is a perfect example. They merged two or three servers into one, and whoever rolled their toon first and had logged in within the past 60 days kept their name, others had to rename. And rather than letting people know origin and destination servers, the destination had a new server name. Also, to solve their current name "problems", they should just get stricter about retiring names and say if you have been unsubbed for 90 or more days you may lose your name if someone else tries to roll with that name. A name change service would be nice too. Also, I truely hope that they are not using VMWare servers or some cloud computing solution here. In my experience, the performance for high demand applications are terrible on those things to this very day.