BP Plans Alaska Layoffs

first_imgBP plans to cut its Alaska workforce by 17 percent by early next year.The oil company announced on Monday that it will reduce its staff by 275 employees and full-time contractors to match a “reduced operational footprint” in the state. BP will offer early retirement and severance packages to employees who choose to take a buyout option.Spokesperson Dawn Patience attributes the layoffs to the sale of four North Slope assets to Hilcorp, a smaller oil company with a growing presence in Alaska. The deal, which was announced in April, includes the Endicott and Northstar fields, along with 50 percent interest in the Milne Point and Liberty fields. BP is transferring 200 field workers to Hilcorp as a result of the agreement, in addition to the 275 support staff they plan to lay off.Patience describes the 275 positions as “overhead” that is no longer needed with a smaller presence on the North Slope. She says the company intends to focus more on oil production in Prudhoe Bay and development of a natural gas megaproject. “BP’s operations may be shrinking in Alaska, but we announced $1 billion of additional investment in Prudhoe Bay, and the addition of two rigs –- one this year and one the year after — and those commitments stand,” says Patience.BP informed Hilcorp of their additional staff cuts on Monday, after they told employees. Hilcorp spokesperson Lori Nelson says the BP announcement was unexpected because only 250 employees were directly associated with the purchased assets and Hilcorp agreed to absorb most of them.“The number today was a bit of a surprise, but that’s BP’s decision,” says Nelson.The layoff announcement arrives less than a month after Alaskans narrowly voted to maintain a capped tax rate on oil production. As one of the three major players on the North Slope, BP contributed nearly $4 million to fight the ballot referendum on Senate Bill 21.Sen. Bill Wielechowski, an Anchorage Democrat who advocated for repeal of Senate Bill 21, calls the BP’s announcement “disturbing.” He notes it comes just as fellow North Slope producer Exxon is projecting a continued decline in oil production in Alaska.“We were promised a lot of things during the [Senate Bill 21] debate, and one of the most powerful things was jobs,” says Wielechowski. “And here we are, a couple weeks after the people of Alaska voted on this, thinking they were going to get a lot more jobs [and] thinking they were going to get a lot more production. And we’ve already had sworn testimony by Exxon that we’re getting less production and then we’ve got BP saying they’re laying off hundreds of Alaskans and contractors.”Wielechowski also finds the timing of BP’s announcement “suspect.”“Had the referendum passed, they probably would have blamed these layoffs on the referendum passing,” says Wielechowski.In a press release, Gov. Sean Parnell also stated he “extremely disappointed” by the announcement, and noted that oil and gas employment in the state was otherwise strong with 15,000 working for the industry.last_img read more

HTTPS and HTTP2 arent competing protocols We n

first_img“HTTPS and HTTP/2 aren’t competing protocols. We need them both,” said Patrick McManus, platform engineer at Mozilla, which is an implementer of HTTP/2.While HTTPS is meant to replace HTTP, it is technically not a protocol and is meant to add more security to HTTP. “Any version of HTTP secured with the Transport Layer Security (TLS) encryption protocol can be called HTTPS,” said McManus. “You can have HTTP/1 or HTTP/2 over TLS, and in both cases you can call the result HTTPS. This being the case, HTTP/2 doesn’t really compare to HTTPS; it’s simply able to run over HTTPS.”According to Aas, the HTTP/2 specification doesn’t require encryption, but major implementations will. Firefox will require HTTP/2 to run over TLS, thus resulting in HTTPS.“New technology should be built on engineering best practices, and using secure communications channels is definitely a best practice that serves our users well,” McManus said. Now that the HTTP/2 specification has been formally approved, it seems that the Web has two choices when it comes to replacing HTTP: HTTP/2 or HTTP Secure (HTTPS).HTTPS is a protocol designed to improve encryption and communications across the Web. The Electronic Frontier Foundation (EFF), along with a group of technology organizations and researchers, are working to easily transition the Web from HTTP to HTTPS through its Let’s Encrypt initiative.“We would like to see the vast majority of Web traffic use HTTPS instead of unencrypted HTTP. It’s why we exist,” said Josh Aas, executive director of the Internet Security Research Group (ISRG), a nonprofit organization managing the Let’s Encrypt initiative.Both protocols have one thing in common: replacing HTTP. Although the HTTP protocol has been widely used, it is insecure and leaves the Web vulnerable, according to the EFF. So the question now is, which protocol—HTTPS or HTTP/2—will better serve the Web?last_img read more