Google barge erection hypegasm latest - What's in the box?

Shiny showroom and party boat, according to fresh rumors


The two mysterious barges Google has parked on either side of the United States will be used as flashy product showrooms, a new report has claimed.

Speculation about the function of the two barges has raged ever since they were stationed near San Francisco's Treasure Island and off the coast of Portland, Maine. Both barges feature a large - and very ugly - makeshift four-story structure on their decks.

After frenzied reporting traced the barges back to Google, a report from a local CBS news outlet claimed the barge would not only serve as a showroom, but as a party venue.

The website alleged the barges were dreamed up at the shadowy Google[x] skunkworks facility, which is based around the corner from the advertising giant's Mountain View headquarters.

The first three floors, we're told, are intended to serve as "dazzling showrooms", complete with chrome fixtures and snazzy lighting. There is also an upper deck party floor, where rich customers can carouse with Google staff.

Being built on a moveable barge, Google's new party venues could be moored off the coast of the US one day and perhaps moved to the Thames a few weeks later.

Where it can't be moored, however, is the top of Fifth Avenue or on London's Regent Street, the locations of Apple's most famous retail stores, which are thought to have inspired Google's barge scheme.

Conspiracy theories about the barges have run all week, with some forum whackos claiming the Chocolate Factory was going to use the barges as arks, load in the animals in two by two and await the apocalypse.

Other nutjobs suggested the Bilderberg Group had persuaded Google to stash a few nuclear bombs in there, so it could blow up the US whenever it fancied getting cracking on the much-delayed New World Order project.

Given the level of secrecy surrounding the barges, it's no wonder the rumours started. Even San Francisco Mayor Ed Lee didn't know what was aboard. “They’ve kept a secret from me as well,” he said.

In a statement, the Californian Coastguard said it had carried out safety inspections of the barge, but would not tell the world what was inside it.

"The Coast Guard conducts hundreds of inspections across the region on a wide variety of commercial vessels. During the course of these activities, Coast Guard personnel are often exposed to sensitive proprietary information, new technologies, and other trade secrets. Regardless of the company or entity involved, the Coast Guard has an obligation to protect sensitive proprietary information, as a company’s competitive posture and business interests depend on it." ®

Similar topics


Other stories you might like

  • Everything you wanted to know about modern network congestion control but were perhaps too afraid to ask

    In which a little unfairness can be quite beneficial

    Systems Approach It’s hard not to be amazed by the amount of active research on congestion control over the past 30-plus years. From theory to practice, and with more than its fair share of flame wars, the question of how to manage congestion in the network is a technical challenge that resists an optimal solution while offering countless options for incremental improvement.

    This seems like a good time to take stock of where we are, and ask ourselves what might happen next.

    Congestion control is fundamentally an issue of resource allocation — trying to meet the competing demands that applications have for resources (in a network, these are primarily link bandwidth and router buffers), which ultimately reduces to deciding when to say no and to whom. The best framing of the problem I know traces back to a paper [PDF] by Frank Kelly in 1997, when he characterized congestion control as “a distributed algorithm to share network resources among competing sources, where the goal is to choose source rate so as to maximize aggregate source utility subject to capacity constraints.”

    Continue reading
  • How business makes streaming faster and cheaper with CDN and HESP support

    Ensure a high video streaming transmission rate

    Paid Post Here is everything about how the HESP integration helps CDN and the streaming platform by G-Core Labs ensure a high video streaming transmission rate for e-sports and gaming, efficient scalability for e-learning and telemedicine and high quality and minimum latencies for online streams, media and TV broadcasters.

    HESP (High Efficiency Stream Protocol) is a brand new adaptive video streaming protocol. It allows delivery of content with latencies of up to 2 seconds without compromising video quality and broadcasting stability. Unlike comparable solutions, this protocol requires less bandwidth for streaming, which allows businesses to save a lot of money on delivery of content to a large audience.

    Since HESP is based on HTTP, it is suitable for video transmission over CDNs. G-Core Labs was among the world’s first companies to have embedded this protocol in its CDN. With 120 points of presence across 5 continents and over 6,000 peer-to-peer partners, this allows a service provider to deliver videos to millions of viewers, to any devices, anywhere in the world without compromising even 8K video quality. And all this comes at a minimum streaming cost.

    Continue reading
  • Cisco deprecates Microsoft management integrations for UCS servers

    Working on Azure integration – but not there yet

    Cisco has deprecated support for some third-party management integrations for its UCS servers, and emerged unable to play nice with Microsoft's most recent offerings.

    Late last week the server contender slipped out an end-of-life notice [PDF] for integrations with Microsoft System Center's Configuration Manager, Operations Manager, and Virtual Machine Manager. Support for plugins to VMware vCenter Orchestrator and vRealize Orchestrator have also been taken out behind an empty rack with a shotgun.

    The Register inquired about the deprecations, and has good news and bad news.

    Continue reading

Biting the hand that feeds IT © 1998–2021