2015 diversity report card

It's no question that the tech industry is made up overwhelmingly of men. And as far as ethnicities go, whites and Asians tend to dominate the field. Given the enormous impact of tech on our daily lives, this lack of diversity is troubling. Diversity…

http://ift.tt/1RbBMO8 (Source)


Alleged OnePlus 2 Mini gets approved by TENAA

The upcoming OnePlus 2 Mini just got a bit more real. The phone was just approved by TENAA, which is the telecommunications equipment certification center in China.

According to the certification page, the phone, model number One E1000, has 4.99-inch 1920×1080 AMOLED display, 2.0GHz octa-core Snapdragon 810 processor, 3GB of RAM, 16GB storage with microSD support, 13 megapixel rear camera, 8 megapixel front camera, and Android 5.1.1 Lollipop.

The phone measures in at 140 x 69 x 6.9mm and weighs in at 138g. The images suggest it will have glass panels on the front and back with a metal frame around the sides, similar to the OnePlus X.

Some of the specs contradict the previous ones we have seen on GFX Bench results, although TENAA is infinitely more reliable than any benchmark info, as the latter can easily be forged.

We will have to wait and see when OnePlus decides to take the wraps off the new model.

Source •…

http://ift.tt/1mrVvgR (Source)

Valve comes clean, admits Christmas day Steam glitch was due to DoS attack

We reported earlier that a weird glitch took over Steam on Christmas morning, as several users reported seeing other users’ account information instead of their own. The issue was sorted out in a few hours, and later Valve confirmed that it was due to a caching issue.

While that may have been the direct cause of the glitch, it was caused due to another problem altogether. Turns out, Steam was the target of a DoS (denial of service) attack, which prevented serving of store pages to users. It caused the traffic to the store to soar by 2000% over average traffic.

In response to the attack, one of Steam’s web caching partners deployed caching configuration to minimize the impact on Steam Store servers and continue to route legitimate traffic. A second caching configuration was deployed during the second wave of the attack, which incorrectly cached web traffic for authenticated users. This is what caused some users to see other users’ pages.

According to Valve, this would have allowed users to see the billing address, last four digits of their Steam Guard phone number, their purchase history, last two digits of their credit card number, and their email address. That’s still a fair bit of information, especially since Valve initially said that no real information was seen by other users.

The issue has since then been resolved but it shows rather poor communication from the company, especially since it concerned user…

http://ift.tt/22AwYYb (Source)