GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

I don't know that I trust this. I was in a GM vehicle and on start the entertsinment unit showed a URL where you can access open source licensed code used in the car. Went to the URL and it was a dead link. I probably should've notified the EFF or something but I didn't. These companies don't understand or respect FOSS.

&gt; The purpose of this project shall be to provide a transport agnostic, layered communication protocol that builds on top of existing automotive and Internet standards, from the mechatronic layer (between ECUs, VMs, etc…) up to the Cloud, enabling a connected software defined vehicles.<p>&quot;Up to the cloud&quot;<p>There is no need for a car to &quot;up to the cloud&quot;. Just give me a local Bluetooth network that reports back to me engine ECU reports, statistical logistical reports and driver stats. Because as soon as you leave the ground to &quot;reach the cloud&quot; that&#x27;s where open-source stops.

There&#x27;s some previous submissions ~6 mo ago but not much traction.<p>Since it&#x27;s not named in the title it&#x27;s: Eclipse UProtocol. Protobuf &amp; CloudEvents. Url-based, with different devices (&quot;UDevice&quot;) each getting their own dns name (&quot;UDomain&quot;). Somewhat transport agnostic. Http2, amqp, mqtt, dds (used some in ROS robotics os).<p>This makes me rather miss Webinos, which was a connected is with pretty interesting end user privacy systems kind of built in that let the device kr car talk to a cloud, but a user defined cloud.

After the failure of pretty much all embedded automobile platforms like microsoft sync that people really don&#x27;t want yet another crappy middleware platform, the automotive industry is trying this shit again removing android auto and apple carplay after people actually got what they want.<p>Why? Auto vendors realized they lost control through their ineptitude of the user interface, and want it back. Problem is no one wants what they have to offer, that is a sub-par experience in every way to simply letting them use their phone as a screen in their car already there.<p>Automobile vendors realized they screwed up and lost real estate while they were still screwing with Microsoft, Clarion, all the other WinCE vendors and few others longer than they should, and are simply going to piss everyone off trying to take it back again.

There&#x27;s some previous submissions ~6 mo ago but not much traction. <a href="https:&#x2F;&#x2F;hn.algolia.com&#x2F;?q=%22uprotocol%22" rel="nofollow noreferrer">https:&#x2F;&#x2F;hn.algolia.com&#x2F;?q=%22uprotocol%22</a><p>Since it&#x27;s not named in the title it&#x27;s: Eclipse UProtocol. Protobuf &amp; CloudEvents. Url-based, with different devices (&quot;UDevice&quot;) each getting their own dns name (&quot;UDomain&quot;). Somewhat transport agnostic. Http2, amqp, mqtt, dds (used some in ROS robotics os).