By timothy from Slashdot's but-I-already-have-a-computer department
MojoKid writes: AMD apparently wasn't done making announcements back at CES 2016. Today the company has shared news of new APUs, processors, fansink coolers, and motherboard updates. The company has been working with motherboard makers to enable a new wave of socket AM3+ and FM2+ motherboards with support for technologies like USB 3.1 (some with type-C and M.2 solid state drives (SSDs). Many of the updated motherboards are already available. AMD also has a trio of new APUs / processors coming down the pipe --the A10-7860K, the A6-7470K, and the Athlon X4 845. The Athlon X4 845 is a quad-core part, featuring four Excavator-class cores clocked at up to 3.8GHz. The processor has 2MB of L2 cache, 8 PCIe 3.0 lanes, and a TDP of 65W, but no built-in graphics. The A6-7470K is a dual Steamroller-core APU (clocked at up to 4GHz), with 8 GPU cores (at up to 800MHz), 1MB of L2 cache, 16 PCIe lanes, and a 65W TDP. The A10-7860K is a little beefier with four Steamroller cores (clocked up to 4GHz), with 8 GPU cores (clocked up to 757MHz), 1MB of L2 cache, 16 PCIe lanes, and a 65W TDP. Both the 7860K and 7470K are unlocked for more flexible overclocking. Finally, the FX-8370 bundled with AMD's new Wraith cooler will be arriving today at the same price point as the previous edition. According to AMD, the Wraith cooler offers 24% more surface area than the previous PIB cooler and the fan pushes 34% more air.Read Replies (0)
By timothy from Slashdot's and-that's-saying-something department
Soulskill writes: According to a (paywalled) report in The Information, Google CEO Sundar Pichai wants the company to take greater control over development of their Nexus smartphones. When producing Nexus phones, Google has always partnered with manufacturers, like Samsung, LG, and HTC, who actually built the devices. Rather than creating a true revenue stream, Google's main goal has been to provide a reference for what Android can be like without interference from carriers and manufacturers. (For example, many users are frustrated by Samsung's TouchWiz skin, as well as the bloatware resulting from deals with carriers. But now, Google appears to want more control. The report indicates Google wants to do a better job of competing throughout the market. They want to compete with Apple on the high end, but also seem concerned that manufacturers haven't put enough effort into quality budget phones. The article at Droid-Life argues, "We all know that Nexus phones will never be household items until Google puts some marketing dollars behind them. Will a top-to-bottom approach finally push them to do that?"Read Replies (0)
By timothy from Slashdot's pay-per-view department
McGruber writes: Citylab has the news that the U.S. Federal Highway Administration is revoking its 2004 approval of the "Clearview" font for road signs. Clearview was made to improve upon its predecessor, a 1940s font called Highway Gothic. Certain letters appeared to pose visibility problems, especially those with tight interstices (or internal spacing)—namely lowercase e, a, and s. At night, any of these reflective letters might appear to be a lowercase o in the glare of headlights. By opening up these letterforms, and mixing lowercase and uppercase styles, Clearview aimed to improve how these reflective highway signs read. Now, just 12 years later, the FHWA is reversing itself: "After more than a decade of analysis, we learned—among other things—that Clearview actually compromises the legibility of signs in negative-contrast color orientations, such as those with black letters on white or yellow backgrounds like Speed Limit and Warning signs," said Doug Hecox, a FHWA spokesperson, in an email. The FHWA has not yet provided any research on Clearview that disproves the early claims about the font's benefits. But there is at least one factor that clearly distinguishes it from Highway Gothic: cost. Jurisdictions that adopt Clearview must purchase a standard license for type, a one-time charge of between $175 (for one font) and $795 (for the full 13-font typeface family) and up, depending on the number of workstations. That doesn't seems like a very good use of tax money, for something that can be nondestructively reused once created.Read Replies (0)
By timothy from Slashdot's documentation-is-nice department
An anonymous reader writes: After MSN Chat closed in 2003, and then again in 2006, some guy has finally documented the authentication system used — over a decade later! Developer Joshua Davison writes by way of explanation:
I think itâ(TM)s important to document the challenge we (users, scripters, hackers) faced connecting to MSN Chat, which is the only known 'proper' implementation of IRCX v8.1 at this time.
MSN Chat introduced a GateKeeper SASL authentication protocol, which implemented 'GateKeeper' and 'GateKeeperPassport' (not dissimilar to the widely documented NTLM authentication protocol, which was also implemented as NTLM, and NTMLPassport)
The GateKeeper Security Support Provider (GKSSP) functioned in two ways; allowing a user to login with a Microsoft Account (Previously known as Microsoft Passport, .NET Passport, Microsoft Passport Network, and Windows Live ID), and also allowed guest authentication for users without, or not willing to use a Microsoft Account.
While most users didn't need or want to understand how the protocol worked, there were many of us who did, and many that just preferred to use MSN Chat outside of the browser.Read Replies (0)