News
Pablo Escobar’s brother wants $100 million in Tesla shares for Not-a-Flamethrower dispute
Elon Musk is no stranger to taking on powerful forces that stand in the way of his Earth-changing missions, but drug lord families still seem like an odd addition to the list. Despite the improbability, infamous cartel founder and cocaine kingpin Pablo Escobar has recently been linked to the serial entrepreneur over The Boring Company’s Not-a-Flamethrower, specifically through Escobar’s brother. Roberto Escobar claims Musk stole the Flamethrower design from him and plans to sue over it – unless Musk agrees to hand over $100 million dollars in either cash or Tesla shares, that is.
“Elon we both know you stole from me, I am OK to settle this right now for $100 million. Tesla shares is OK or cash. I will win in court, and you will lose more than $100 million,” Escobar said in a statement to The Next Web. “Maybe I will make myself new Tesla CEO with the courts?… Let’s settle this like gentleman. Send me the Tesla Shares to Escobar Inc.”
Someone associated with Musk’s business activities reportedly spent time with Escobar (the living brother, not the deceased drug lord) in the summer of 2017 wherein an Escobar Inc. toy flamethrower concept was discussed, according to a report originally published by TMZ. The Boring Company’s Flamethrower, announced in January 2018, apparently was a dead ringer for Escobar’s idea design-wise, leading cartel leader’s brother to angrily conclude that his idea had been stolen. Musk later responded to TMZ‘s report on Twitter, saying “It’s Not a Flamethrower, Mr Escobar.”
The dispute is interesting and unusual, to say the least, but we can be sure there’s one thing Boring clearly did not get from Escobar Inc. – the flamethrower’s purpose.
“I want the people to be able to burn money, like me and Pablo used to do. I burned probably a couple of billion dollars over the years. Literally burning the money. For many reasons,” Escobar was quoted as saying about the device.
Escobar is now weighing his legal options against Musk, although it’s not clear what options are exactly available.
Prior to 2013, if an inventor could demonstrate their invention predated someone else’s patented invention for the same thing, they could sue and work out a financially retroactive deal to be compensated for their work (more or less). However, with the enactment of the America Invents Act, the United States now has a “first to file” system that only gives inventors one year from public disclosure of their invention to file for patent protection. In Escobar’s case, he’s basically too late to file for a patent where it would matter most to Musk – in the United States. The only other legal workaround would seem to be a lawsuit over a non-disclosure agreement, which doesn’t appear to have happened here. It’s not enough that there were witnesses to the discussion, and it also doesn’t seem like there was even a handshake-type understanding over any claims to the design.
Another thing worth mentioning is that if The Boring Company has already filed for patent protection of its Not-a-Flamethrower design, it doesn’t appear to have published yet based on patent database searches. Since the idea was disclosed in January 2018 (or even 2017, based on Escobar’s claims), it’s now considered ‘prior art’ and renders any other highly similar patent filings ineligible for protection. It would appear that Escobar’s best bet for legal protection would have been to file for a patent right after Musk’s flamethrower was announced so both devices would have been in that muddy one-year window and open to a court fight. Alas, it’s all water under the bridge now.
The Boring Company had a few options to pursue here, actually. First, the tunneling venture could have filed for a design patent which only protects what their flamethrower looks like. These types of patent applications usually issue to full patents quickly unless the patent examiner objects to it based on similar designs. If Boring went this route, we should see a patent show up shortly if one was filed around the time of the product announcement in January 2018.
-
A second option The Boring Company could have taken was to file for a utility patent, meaning there was some sort of technical merit to the Not-a-Flamethrower’s design. These publish 18 months after filing unless non-publication is specifically requested. If Boring went this route, well, there are so many timelines that could have been taken, it’s hard to say whether we’ll see anything until a patent issues, assuming one issues at all. Regardless, the patent route was Escobar’s only real route for lawsuit-driven compensation, and he seems out of luck.
Perhaps in response to recent publicity, the Escobar Inc. Flamethrower just went on sale for $250, and according to its company website’s History page, 20,000 units will be produced. This, of course, is the exact amount the Boring Company sold at the original price of $500. Among other interesting news items, one of the gems from that same History page reads, “2004 – Roberto de Jesus Escobar Gaviria is freed from Itagui Prison based on excellent behavior.” This important moment in the Escobar Inc. chronicles is surely only matched by the successful launch of Escobar Inc.’s Flamethrower for burning cold hard cash in cocaine kingpin fashion.
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
-
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
-
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
-✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
-
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
-
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
-
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
-
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
-
Tesla claims supplier is holding Cybertruck production hostage
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
