Freighter hits fishing boat in Gulf of Suez; thirteen dead

Tuesday, December 16, 2014

A freighter hit a fishing boat around midnight on Sunday morning in the Gulf of Suez in the Red Sea. Of the 40 Egyptian fisherman on board, thirteen are dead and thirteen more missing.

Survivor Al Sayyed Mohamed Arafat told local media he jumped from the fishing boat, named Badr al-Islam, as the container ship approached. He says he hung onto a wooden crate for four hours before rescue. Local authorities have promised compensation to each survivor.

A vessel, flagged in Panama, suspected to be involved in the collision has been detained by the military. The army said yesterday one victim raised the alarm by phone and the military sent four boats and a helicopter to commence search and rescue off the Gabal al-Zayt coastline.

A plane has since joined the search. The military say the fishing boat lacked safety equipment for emergency communications.

The detained ship was found south of the Gulf, near the port of Safaga. It was carrying 220 tonnes of cargo according to the General Authority for the Red Sea Ports.

Friday, May 19, 2006

This interview intends to provide some insight into OpenSync, an upcoming free unified data synchronization solution for free software desktops such as KDE, commonly used as part of the GNU/Linux operating system.

Hi Cornelius, Armin and Tobias. As you are now getting close to version 1.0 of OpenSync, which is expected to become the new synchronisation framework for KDE and other free desktops, we are quite interested in the merits it can provide for KDE users and for developers, as well as for the Open Source Community as a whole. So there’s one key-question before I move deeper into the details of OpenSync:

What does OpenSync accomplish, that no one did before?

Cornelius:

First of all it does its job of synchronizing data like addressbooks and calendars between desktop applications and mobile devices like PDAs and cell phones.

But the new thing about OpenSync is that it isn’t tied to a particular device or a specific platform. It provides an extensible and modular framework that is easy to adopt for application developers and people implementing support for syncing with mobile devices.

OpenSync is also independent of the desktop platform. It will be the common syncing backend for at least KDE and GNOME and other projects are likely to join. That means that the free desktop will have one common syncing solution. This is something really new.

How do the end-users profit from using synching solutions that interface with OpenSync as framework?

Cornelius:

First, the users will be able to actually synchronize all their data. By using one common framework there won’t be any “missing links”, where one application can sync one set of devices and another application a different one. With OpenSync all applications can sync all devices.

Second, the users will get a consistent and common user interface for syncing across all applications and devices. This will be much simpler to use than the current incoherent collection of syncing programs you need if you have more than the very basic needs.

How does OpenSync help developers with coding?

Cornelius:

It’s a very flexible and well-designed framework that makes it quite easy for developers to add support for new devices and new types of data. It’s also very easy to add support for OpenSync to applications.

The big achievement of OpenSync is that it hides all the gory details of syncing from the developers who work on applications and device support. That makes it possible for the developers to concentrate on their area of expertise without having to care what’s going on behind the scenes.

I have written quite a lot of synchronization code in the past. Trust me, it’s much better, if someone just takes care of it for you, and that’s what OpenSync does.

Tobias:

Another point to mention is the python wrapper for opensync, so you are not bound to C or C++, but can develop plugins in a high level scripting language.

Why should producers of portable devices get involved with your team?

Cornelius:

OpenSync will be the one common syncing solution for the free desktop. That means there is a single point of contact for device manufacturers who want to add support for their devices. That’s much more feasible than addressing all the different applications and solutions we had before. With OpenSync it hopefully will become interesting for manufacturers to officially support Linux for their devices.

Do you also plan to support applications of OpenSync in proprietary systems like OSX and Windows?

Cornelius:

OpenSync is designed to be cross-platform, so it is able to run on other systems like Windows. How well this works is always a question of people actually using and developing for this system. As far as I know there isn’t a real Windows community around OpenSync yet. But the technical foundation is there, so if there is somebody interested in working on a unified syncing solution on Windows, everybody is welcome to join the project.

What does your synchronisation framework do for KDE and for KitchenSync in particular?

Cornelius:

OpenSync replaces the KDE-specific synchronization frameworks we had before. Even in KDE we had several separate syncing implementations and with OpenSync we can get replace them with a common framework. We had a more generic syncing solution in KDE under development. This was quite similar from a design point of view to OpenSync, but it never got to the level of maturity we would have needed, because of lack of resources. As OpenSync fills this gap we are happy to be able to remove our old code and now concentrate on our core business.

What was your personal reason for getting involved with OpenSync?

Cornelius:

I wrote a lot of synchronization code in the past, which mainly came from the time where I was maintaining KOrganizer and working on KAddressBook. But this always was driven by necessity and not passion. I wanted to have all my calendar and contact data in one place, but my main objective was to work on the applications and user interfaces handling the data and not on the underlying code synchronizing the data.

So when the OpenSync project was created I was very interested. At GUADEC in Stuttgart I met with Armin, the maintainer of OpenSync, and we talked about integrating OpenSync with KDE. Everything seemed to fit together quite well, so at Linuxtag the same year we had another meeting with some more KDE people. In the end we agreed to go with OpenSync and a couple of weeks later we met again in Nuernberg for three days of hacking and created the KDE frontend for OpenSync. In retrospect it was a very pleasant and straightforward process to get where we are now.

Armin:

My reason to get involved (or better to start) OpenSync was my involvement with its predecessor Multisync. I am working as a system administrator for a small consulting company and so I saw some problems when trying to find a synchronization solution for Linux.

At that point I joined the Multisync project to implement some plugins that I thought would be nice to have. After some time I became the maintainer of the project. But I was unhappy with some technical aspects of the project, especially the tight coupling between the syncing logic and the GUI, its dependencies on GNOME libraries and its lack of flexibility.

Tobias:

Well, I have been a KDE PIM developer for several years now, so there was no way around getting in touch with synchronization and KitchenSync. Although I liked the idea of KitchenSync, I hated the code and the user interface […]. So when we discussed to switch to OpenSync and reimplementing the user interface, I volunteered immediately.

Can you tell us a bit about your further plans and ideas?

Cornelius:

The next thing will be the 1.0 release of OpenSync. We will release KitchenSync as frontend in parallel.

Armin:

There are of course a lot of things on my todo and my wishlist for opensync. For the near future the most important step is the 1.0 release, of course, where we still have some missing features in OpenSync as well as in the plugins.

One thing I would really like to see is a thunderbird plugin for OpenSync. I use thunderbird personally and would really like to keep my contacts up to date with my cellular, but I was not yet able to find the time to implement it.

Tobias:

One thing that would really rock in future versions of OpenSync is an automatic hardware detection mechanism, so when you plugin your Palm or switch on your bluetooth device, OpenSync will create a synchronization group automatically and ask the user to start syncing. To bring OpenSync to the level of _The Syncing Solution [tm]_ we must reduce the necessary configuration to a minimum.

What was the most dire problem you had to face when creating OpenSync and how did you face it?

Cornelius:

Fortunately the problems which I personally would consider to be dire are solved by the implementation of OpenSync which is well hidden from the outside world and [they are] an area I didn’t work on 😉

Armin:

I guess that I am the right person to answer this question then 🙂

The most complicated part of OpenSync is definitely the format conversion, which is responsible for converting the format of one device to the format that another device understands.

There are a lot of subsystems in this format conversion that make it so complex, like conversion path searching, comparing items, detection of mime types and last but not least the conversion itself. So this was a hard piece of work.

What was the greatest moment for you?

Cornelius:

I think the greatest moment was when, after three days of concentrated hacking, we had a first working version of the KDE frontend for OpenSync. This was at meeting at the SUSE offices in Nuernberg and we were able to successfully do a small presentation and demo to a group of interested SUSE people.

Armin:

I don’t remember a distinct “greatest moment”. But what is a really great feeling is to see that a project catches on, that other people get involved, use the code you have written and improve it in ways that you haven’t thought of initially.

Tobias:

Hmm, also hacking on OpenSync/KitcheSync is much fun in general, the greatest moment was when the new KitchenSync frontend synced two directories via OpenSync the first time. But it was also cool when we managed to get the IrMC plugin working again after porting it to OpenSync.

As we now know the worst problem you faced and your greatest moment, the only one missing is: What was your weirdest experience while working on OpenSync?

Cornelius:

Not directly related to OpenSync, but pretty weird was meeting a co-worker at the Amsterdam airport when returning from the last OpenSync meeting. I don’t know how high the chance is to meet somebody you know on a big random airport not related at all to the places where you or the other person live, but it was quite surprising.

Tobias:

Since my favorite language is C++, I was always confused how people can use plain C for such a project, half the time your are busy with writing code for allocating/freeing memory areas. Nevertheless Armin did a great job and he is always a help for solving strange C problems 🙂

Now I’d like to move on to some more specific questions about current and planned abilities of OpenSync. As first, I’ve got a personal one:

I have an old iPod sitting around here. Can I or will I be able to use a program utilizing OpenSync to synchronize my calendars, contacts and music to it?

Cornelius:

I’m not aware of any iPod support for OpenSync up to now, but if it doesn’t exist yet, why not write it? OpenSync makes this easy. This is a chance for everybody with the personal desire to sync one device or another to get involved.

Armin:

I dont think that there is iPod support yet for OpenSync. But it would definitely be possible to use OpenSync for this task. So if someone would like to implement an iPod plugin, I would be glad to help 🙂

Which other devices do you already support?

Cornelius:

At this time, OpenSync supports Palms, SyncML and IrMC capable devices.

Which programs already implement OpenSync and where can we check back to find new additions?

Cornelius:

On the application side there is support for Evolution [GNOME] and Kontact with KitchenSync [KDE] on the frontend side and the backend side and some more. I expect that further applications will adopt OpenSync once the 1.0 version is released.

Armin:

Besides kitchensync there already are a command line tool and a port of the multisync GUI. Aside from the GUIs, I would really like to see OpenSync being used in other applications as well. One possibility for example would to be integrate OpenSync into Evolution to give users the possibility to synchronize their devices directly from this application. News can generally be found on the OpenSync web site www.opensync.org.

It is time to give the developers something to devour, too. I’ll keep this as a short twice-fold technical dive before coming to the takeoff question, even though I’m sure there’s information for a double-volume book on technical subleties.

As first dive: How did you integrate OpenSync in KitchenSync, viewed from the coding side?

Cornelius:

OpenSync provides a C interface. We wrapped this with a small C++ library and put KitchenSync on top. Due to the object oriented nature of the OpenSync interfaces this was quite easy.

Recently I also started to write a D-Bus frontend for OpenSync. This also is a nice way to integrate OpenSync which provides a wide variety of options regarding programming languages and system configurations.

And for the second, deeper dive:

Can you give us a quick outline of those inner workings of OpenSync, from the developers view, which make OpenSync especially viable for application in several different desktop environments?

Cornelius:

That’s really a question for Armin. For those who are interested I would recommend to have a look at the OpenSync website. There is a nice white paper about the internal structure and functionality of OpenSync.

Armin:

OpenSync consists of several parts:

First there is the plugin API which defines what functions a plugin has to implement so that OpenSync can dlopen() it. There are 2 types of plugins:

A sync plugin which can synchronize a certain device or application and which provides functions for the initialization, handling the connection to a device and reading and writing items. Then there is a format plugin which defines a format and how to convert, compare and detect it.

The next part is a set of helper functions which are provided to ease to programming of synchronization plugins. These helper functions include things like handling plugin config files, HashTables which can be used to detect changes in sets of items, functions to detect when a resync of devices is necessary etc.

The syncing logic itself resides in the sync engine, which is a separate part. The sync engine is responsible for deciding when to call the connect function of a plugin, when to read or write from it. The engine also takes care of invoking the format conversion functions so that each plugin gets the items in its required format.

If you want more information and details about the inner workings of OpenSync, you should really visit the opensync.org website or ask its developers.

To add some more spice for those of our readers, whose interest you just managed to spawn (or to skyrocket), please tell us where they can get more information on the OpenSync Framework, how they can best meet and help you and how they can help improving sync-support for KDE by helping OpenSync.

Cornelius:

Again, the OpenSync web site is the right source for information. Regarding the KDE side, the kde-pim@kde.org mailing list is probably the right address. At the moment the most important help would be everything which gets the OpenSync 1.0 release done.

[And even though] I already said it, it can’t be repeated too often: OpenSync will be the one unified syncing solution for the free desktop. Cross-device, cross-platform, cross-desktop.

It’s the first time I feel well when thinking about syncing 😉.

Armin:

Regarding OpenSync, the best places to ask would be the opensync mailing lists at sourceforge or the #opensync irc channel on the freenode.net servers.

There are always a lot of things where we could need a helping hand and where we would be really glad to get some help. So everyone who is interested in OpenSync is welcome to join.

Many thanks for your time!

Cornelius:

Thanks for doing the interview. It’s always fun to talk about OpenSync, because it’s really the right thing.

Armin:

Thank you for taking your time and doing this interview. I really appreciate your help!

Tobias:

Thanks for your work. Publication and marketing is something that is really missing in the open source community. We have nice software but nobody knows 😉

Further Information on OpenSync can be found on the OpenSync Website: www.opensync.org

This Interview was done by Arne Babenhauserheide in April 2006 via e-mail and KOffice on behalf of himself, the OpenSource Community, SpreadKDE.org and the Dot (dot.kde.org).It was first published on the Dot and is licensed under the cc-attribution-sharealike-license.A pdf-version with pictures can be found at opensync-interview.pdf (OpenDocument version: opensync-interview.odt)

Thursday, May 31, 2007

A semi-tractor carrying 9,000 gallons (34,000 litres) of liquid butane overturned at the weekend on the United States highway 50 east of Salida, Colorado, rupturing the tank and spilling its contents.

The road was closed to traffic for 20 hours during one of the busiest times of the year, and traffic rerouted along a three-hour diversion route.

Colorado State Patrol reports state the driver, Roger Meely, 62, was hauling a pressurised tank full of butane when he lost control and crashed near Mile Marker 228. Colorado State Patrol Sgt. William Holt described the accident, “He lost control of the vehicle in the curves, veered across the lanes and rolled it.” Meely was treated and released from the Heart of the Rockies hospital in Salida after the crash, but escaped serious injury.

The truck rolled at about 6:50 p.m. six miles from Salida, prompting closure of the highway. Although the driver escaped unharmed, 10-15 homes and an unknown number of campsites along the Arkansas River were evacuated as fumes began to drift downstream towards the town of Swissvale. Rafters were ordered away from the area, but Hazmat crews were able to prevent butane from contaminating the river.

Emergency workers were forced to allow the butane to vent itself through the night. Capt. Jack Cowert of the Colorado State Patrol said, “I would say those of us on scene were surprised it didn’t explode.”

In total, the following organisations responded: the Colorado State Patrol Hazardous Materials Unit, South Arkansas Fire Protection District, Howard Volunteer Fire Department, Arkansas Valley Ambulance, Chaffee County Emergency Services, Alpine Towing and the Colorado Department of Transportation.

An attempt was made at 9:00 a.m. Monday to right the tanker and tow it away, but in the process of securing it to the tow truck it slipped and a dolly axle buckled, further lengthening the delay.

The road was not reopened until 3:10 p.m. Monday. Sheila Johnson, a flagger working for Alpine Towing, later said of the commuters affected that they were mostly understanding, saying of them, “For the most part people were pretty good about the road being closed,”.

Holt blamed the driver for the accident, saying he “will be cited for something,” and that “anytime a crash like this happens, the driver either wasn’t paying attention or he was driving too fast.” It was later determined that the driver’s excessive speed was to blame. He was ultimately charged over the incident.

The incident sparked a full review evaluating the emergency response, which included about ten agencies.

Friday, June 16, 2006

The Australian federal opposition has attacked the Howard government following four incidents in a week at the HIFAR nuclear research reactor in Lucas Heights, South of Sydney. The incidents come just a week after the Australian government announced an inquiry into the feasibility of nuclear power.

The first incident occurred on June 8, when a carbon canister containing radioactive material exploded, blowing out seals in a cell at the Lucas Heights site. The accident is believed to be an explosion in a carbon canister containing radioactive material, which blew the seals out on Hot Cell No 2 in Building 54 releasing small amounts of xenon and krypton into the atmosphere.

Jenny Macklin (Jagajaga, Labor), shadow science minister and deputy leader of the opposition accused science minister Julie Bishop (Curtin, Liberal) of misleading the parliament. Ms Bishop told parliament on Wednesday that “there was no measurable contamination found outside the immediate area where the incident occurred,”

Ms Bishop denied there being any radiation threat to the community. “According to ANSTO, there was absolutely no radiation threat to the health of the workers of ANSTO or the community.”

Jenny Macklin said in a statement on Wednesday that details of the incident were being hidden. “The local community deserves to be told what actually happened at the Lucas Heights reactor last Thursday, and why the release of radioactive gases into the atmosphere was not made public,” said Ms Macklin.

Following Ms Macklin’s statement ANSTO said it was “surprised and disappointed” at Ms Macklin’s comments. ANSTO refuted that it failed to adequately notify the community saying that they released a media statement the day after the incident. ANSTO said that radiation released during the incident was “so low as not to be directly measurable”. ANSTO said that it could however calculate the amount of radioactive material released and it was a “very small fraction of the radiation dose received by everyone each year from naturally occurringsources of radiation”.

ANSTO assured the public that the releases could not be detected off-site.

Following a statement by the science minister on Thursday that she was unaware of any incidents at ANSTO in the 12 months prior to the latest incidents, the opposition again questioned Ms Bishop’s competence. Ms Macklin asked how the minister could not be informed about compliance reports issued by Australia’s nuclear regulator ARPANSA that state there were 12 incidents at Lucas Heights in 2005.

Following Ms Macklin’s removal from the house, Anthony Albanese (Grayndler, Labor), shadow environment minister questioned Ms Bishop about incidents at ANSTO on Wednesday. According to ANSTO, a worker received a low dose of radiation from Iodine-123 while packaging radiopharmaceuticals. ANSTO claims that the technician received a dose around four per cent of the annual limit for radiation workers and much less than a thyroid cancer patient would receive during a nuclear medicine scan.

In a statement, Ms Macklin later accused the science minister of being ill-informed of the incident at Lucas Heights, saying it was concerning the government had an “incompetent” science minister at a time when they were “pushing the benefits of nuclear power”.

Responding to the opposition’s questions during question time in the House of Representatives, the science minister accused the opposition of engaging in a scare campaign to close down a facility that provides “a medical service for cancer suffers across Australia.

ANSTO has said that the radiation dose received by the technician was so low he did not require medical attention once he had undergone several tests.

ANSTO admitted another two incidents occurred at its Lucas Heights facility on Thursday. The first occurred when a worker who was cleaning a production area burst a package of radioactive material. The second occurred when a worker packing a radiopharmaceutical dropped a small vial. ANSTO said that the amount of radiation received by both workers was extremely low.

ANSTO said that while it is uncommon for two incidents to occur on a single day, it was not uncommon for minor incidents to occur once a month.

Tuesday, January 16, 2018

A car accident involving the car occupants and a dentist’s office happened on Sunday night in Santa Ana, California. A white Nissan sedan which was apparently driving too fast hit the raised concrete median on the road, after which it was launched into the air, slamming straight into the wall of the second floor of a two-story dental practice building, where the car got wedged.

According to the police, the car approached from a side street. The room of the dental office penetrated by the sedan was used as a storage space. A fire department crane was used to extract the vehicle from the building, which took several hours.

There were two people in the sedan. One of them managed to escape from the hanging vehicle on his own, while the other one remained trapped inside it for over an hour. They were both hospitalized with minor injuries, according to the Orange County Fire Authority (OCFA). According to the police, the driver of the car admitted narcotics use, and after toxicology tests the case is to be submitted to the Orange County District Attorney’s Office.

The moment of the accident was captured by surveillance video from a bus which the car narrowly missed when becoming airborne.

According to OCFA spokesperson Captain Stephen Horner, there was a small fire after the crash, which was extinguished quickly.

Monday, March 17, 2014

Nico Rosberg won the opening race of this year’s Formula 1 season in Australia yesterday. TV commentators spoke of “fascination throughout the field” as big names retired and new names proved themselves.

Former champion Lewis Hamilton qualified on pole but problems were evident by the second lap when he received a team radio message telling him “we need to retire… save the engine, save the engine!” Another followed rapidly, however, telling him to “just stay out, stay out, just keep on rolling”. Hamilton left the race on the fourth lap.

Reigning champion Sebastian Vettel did not fare much better, having only qualified twelfth, with engine woes of his own. He too quit the race in the early stages, staying behind to watch the race and, according to commentator and retired Scottish F1 racer David Coulthard, learn what he could from the sidelines.

Vettel and Hamilton were not the only stars retiring early. Veteran racer Felipe Massa was rammed from behind by Kobiashi’s Caterham, sending both cars out and prompting deployment of yellow flags for several laps while the debris was recovered. The crash was triggered by Kobiashi clipping Kimi Raikkonen, damaging the front of Kobiashi’s car. Raikkonen stayed in the race and managed to finish eighth. The first ten cars over the finish line score points towards both the driver’s and constructor’s championships.

Coulthard and fellow commentators believe Kobiashi, who took responsibility for the accident, may receive points on his racer’s licence in a new system to deal with transgressions introduced this year. Kobiashi called the crash “My mistake[… I] should have braked earlier, and I apologise to Felipe”. Massa said Kobiashi “cannot do a start like that, every time” he does so will lead to an accident.

More drama followed shortly after when Valteri Bottas clipped a wall on lap 10, breaking the rim of his back-right wheel. The rim was left on the track, followed shortly thereafter by the tyre off the wheel. The safety car was deployed for several laps until the debris was recovered. Despite the setback Bottas climbed back up the standings and finished in sixth place.

Many drivers, including cars at the front of the pack, took advantage of the safety car period to do pit stops. Some are now considering using less fuel than the maximum allowance in a move the FIA never expected technologically possible when drafting the rules several years ago.

It was a day for débutantes at Albert Park, a street circuit where racing took place in close proximity to busy public roads. Newcomer Kevin Magnussen scored third place on his first F1 race, while fellow rookie Daniil Kvyat came in tenth and became the youngest-ever F1 points scorer. Kvyat takes the record from Vettel by several months while Magnussen becomes the first Dane on an F1 podium.

Not every débutante was so lucky; Caterham driver Marcus Eriksson dropped out of his first race after being radioed “Stop the car, stop the car, engine oil pressure”. Established racers Pastor Maldonado and Romain Grosjean, both Lotus drivers, also stopped with technical trouble. All three cars pulled up at the side of the track on different laps, each triggering yellow flags. Despite the retirements, fourteen cars finished which was more than some commentators were expecting.

Hamilton was upbeat about his retirement, saying “It’s tough for everyone but that’s the way it is” and adding “We’re not the only ones [to have difficulties]”. Vettel was more pessimistic, claiming this is “going to be a long season”. Asked about the cause of his engine troubles, Hamilton said “One of the cylinders, I think, was not firing”.

The race was unusual from start to finish, having been shortened by one lap after the first start was aborted by amber lights instead of just green. The end is more controversial; home driver Daniel Ricciardo scored his first-ever Australian Grand Prix podium finish in second place but was later disqualified for an alleged breach of fuel regulations. Ricciardo had been the first Australian driver to stand on the podium in his home country since Formula 1 brought the event into the championship format used today.

His disqualification is not final, however. His team, Red Bull, have vowed to appeal. If the appeal fails all the drivers below him move up one position, meaning first-time entrant Magnussen will have come in second place and Kvyat will be ninth. That would see Sergio Perez score a point for Force India by moving into tenth. Perez’s race was hampered early by a puncture picked up in the opening lap.

Ricciardo was reported to the stewards by technical delegate Jo Bauer who claimed his car “exceeded consistently the maximum allowed fuel flow of 100kg/h”. 100kg is also the maximum fuel allowed on board cars, a new limit set for this season. The fuel flow rule is also new this year; F1 cars averaged about 170kg/h last year.

Ricciardo was disqualified after five hours of steward deliberations. Red Bull have hit back with a statement saying many teams have found the FIA’s fuel flow meter to be faulty. They say they are “confident the fuel supplied to the engine is in full compliance with the regulations.” Today Andrew Westacott, chief executive of the Australian Grand Prix, said the appeal outcome may not be known for weeks.

Prior to Ricciardo’s disqualification, the remaining point-scorers were Jensen Button in fourth, Fernando Alonso in fifth, Nico Hulkenberg in seventh, and Jean-Eric Vergne in ninth.

Racers and fuel rules were not the only things fresh for this race. Williams are on the back of their worst-ever season and have changed their livery to brighter, whiter cars. Another new innovation is the introduction of red lights on the rear of cars that blink when the vehicle is not using electricity, warning the car behind of possible deceleration. F1 cars also now sport hybrid turbo engines.

Rosberg, speaking after what is his first Australian victory, said it is “Such a pleasure to have such a fast car.” He came a full 24 seconds ahead of Ricciardo. It is also the hundredth victory by an F1 car powered by a Mercedes engine.

“Whatever the outcome I’m really proud of what I did today”, Ricciardo said as he awaited the stewards’ disqualification decision. “There are more positives than negatives”.