Yes, that's very often the case with things that would very likely be shared if it looked good.
There are things that don't get shared out of principle. For example there are anonymous votes or behind the scenes negotiations without commitment or security critical data.
But given that Musk tends to parade around vague promises since a very long time, it seems sharing data that looks very good would certainly be something they would do.
If a company wants to sell you something, but wants to block access to information, the default position for everyone should be "it's probably because it's bad".
If I have an investment fund and I refuse to tell you about the current performance, I hope you would be sceptical.
If I try to sell you medicine and redact the information about whether it does what I claim, and block you from seeing how many people were poisoned from taking it, I hope that everyone would refuse to take it.
The insanity I'm seeing here from Tesla defenders is amazing. I can only assume they've fully bought in to the vision and tied assets to it and refuse to acknowledge that they might lose everything.
It's a public company making money off of some claims. Not being transparent about the data supporting those claims is already a huge red flag and failure on their part regardless of what the data says.
While I think Tesla should be transparent, this article doesn't really make sure it is comparing apples to apples either.
I think its weird to characterize it as legitimate and the say "Go Tesla convince me ohterwise" as if the same audience would ever be reached by Tesla or people would care to do their due diligence.
It’s not weird. They have a history of over promising to the point that one could say they just straight up lie on a regular basis. The bar is higher for them because they have abused the public’s trust and it has to be earned again.
The results have to speak for Tesla very loudly and very clearly. And so far they don’t.
But this is more your feelings than actually factual.
I mean sure you can say that the timelines did slip a lot but that doesn’t really have anything to with the rest that is insinuated here.
I would argue a timeline slipping doesn’t mean you go about killing people and lie about it next. I would even go so far as to say that the timelines did slip to exactly avoid that.
Tesla continues to overpromise, about safety, about timelines that slip due to safety.
We should be a bit more hard nosed and data based when dealing with these things rather than dismissing the core question due to "feelings" and due to Tesla not releasing the sort of data tha allows fair analysis b
> But this is more your feelings than actually factual
Seems to be the other way, though I find that kind of rude to assert as opposed to asking me what informs my opinion. Other comments have answered that very well
You're generous with your words to the point they sound like apologism. Musk has been promising fully autonomous driving "within 1-3 years" since 2013. And he's been charging customers money for that promise for just as long. Timelines keep slipping for more than half of the company's existence now, that's not a slipup anymore.
Tesla has never been transparent with the data on which they base their claims of safety and performance of the system. They tout some nice looking numbers but when anyone like the NHTSA requests the real data they refuse to provide it.
When NHTSA shows you numbers, they're lying. If I tell you I have evidence Tesla is lying you'll tell me to show it or STFU. When Tesla does the same after so many people died, you go all soft and claim everyone else is lying. That's very one sided behavior, more about feelings than facts.
> But this is more your feelings than actually factual.
The article is about "NHTSA crash data, combined with Tesla’s new disclosure of robotaxi mileage". Sounds factual enough. If Tesla is sitting on a trove of data that proves otherwise but refuse to publish it that's on them. If anyone is about the feels and not the facts here, it's you.
> I mean sure you can say that the timelines did slip a lot but that doesn’t really have anything to with the rest that is insinuated here.
No. Not at all. This isn't "timelines slip". This is Musk saying, and I quote, "Self driving is a solved problem. We are just tuning the details." in 2016, and in 2021, "Right now our highest priority is working on solving the problem."
Somewhere along the line, it apparently got "unsolved".
"Timelines slipped" is far too generous for someone who, whenever Tesla is facing bad press, will imply that a new FSD release coming in 6 months, 3 months, a month, will solve all the issues plaguing it so far. Repeatedly. Those aren't real timelines.
Hell, even Tesla has had to add comments to investor and securities documents saying that "Musk's statements are aspirational and do not always reflect engineering realities."
I don’t see how this is connected to the point at hand here.
I think taking time to make sure the system works is the right call. Delaying it is the right call.
Not publishing something because you had a different impression previously, just because, is the right call.
I think it integrity to delay a product even when your investors might get angry.
Is it a winning strategy at wallstreet? No, probably not.
But what is the argument here „Musk bad“ because he delays a product because it’s not ready?
I think doing the due diligence is required here. Musk argument „it’s solved“ could even be argued by „look at Waymo“ they are doing it, aren’t they?
Tesla is aiming for more than that though.
And as it is in product development sometimes, sometimes your don’t know what you don‘t know.
Because why do you want to focus on chains guarding parkingspots, your cameras aren’t able to see, when your car can’t even drive through the city.
This is such a big thing to solve and 100% is impossible given some definitions.
Back to the article, I think delaying for safety is the right call, and that is also what the article says. It’s just that the article is in bad faith, as most of the arguments here are.
You probably would turn around and slam Musk for a System that obviously problematic as the alternative and until then it’s saying that he delays.
And if it were obviously problematic I think it would be much louder than just an article from a website that is know for having a biased view at things.
Tesla (Elon Musk really) has a long history of distorting the stats or outright lying about their self driving capabilities and safety. The fact that folks would be skeptical of any evidence Tesla provided in this case is a self-inflicted problem and well-deserved.
He did promise his electric trucks to be more cost-effective than trains (still nothing in 2026...). And "world's fastest supercar". And full self-driving by "next year" in 2015. None of these are offered in 2026.
There have never been truthful statements from his companies, only hype & fluff for monetary gains.
There used to be [EDIT: still is] a website[1] that listed all of Musk's promises and predictions about his businesses and showed you how long it's been since he said the promise would materialize. It's full of mostly old statements, probably because it's impossible to keep up with the amount of content being generated monthly.
We do rendered manifest pattern. The chart gets rendered into a single yaml, that get checked into it's own branch and PR. That way, any changes can be easily inspected before merging and can work with confidence that e.g. changing a setting or updating isn't going to change ALL of the objects. It's also extremely easy to (trustingly) roll back to previous states.
The only downside is that you can't really prune excess objects with this method. We're pushed to use Argo for deployment which I don't really gel with, but I trust it to apply the yaml, and at the very least it highlights when objects need to be removed.
Honestly my take on Helm charts is to keep them as simple as possible. All the complicated stuff you see in public charts people publish? Yeah stay far, far away from that. Our Helm charts at my job are 95% plain YAML files with an occasional variable insertion to handle cases where you need different hostnames (etc) based on the environment being deployed to. They are a pleasure to work with because they are so simple.
Even some of the examples in TFA (like the optional persistent storage one) are IMO way more complex than what you should use Helm for. At that point you're better off using a programming language to generate the YAML based on some kind of state object you create. It's way too error prone to do that stuff with YAML templating imo.
I love it. Finally some innovation. Now make it incapable of instagram and TikTok and other invasive social media crap and we might have the winner for the next decade.
As if :(
Give it copy paste / translate tasks and it’s a no brainer (quite literally)
But same can be said of humans.
The question here is, did it implement it because it read the available online documentation about the NES architecture OR did it just see one too many of such implementations.
Indeed, the 'cleanroom' standard always was one team does the RE and writes a spec, another team that has never seen the original (and has written statements with penalty clauses to prove it) then does the re-implementation. If you were to read the implementation, write the spec and then write the re-implementation that would be definitely violating the standard for claiming an original work.
I think there is a point to this. I’m not saying I’m a fan. But the reality is that it is too simple to communicate secretly, and the government has an interest in protecting its citizens. This is true in many aspects. (Health, technology, electronics, traffic)
Btw. The https communication comparison does not hold, there is always a third party that can read what you say. E2E chats are effectively communication where evidence is instantly destroyed.
Want to have a private communication, I think offline is the right approach.
I agree that it sucks, but it’s probably not about you. It’s about nefarious people that use this as an uber advantage.
But the reality is that it is too simple to communicate secretly
This is a horrifying thought to be reading on this site of all places, and I can't help but feel that humanity is well and truly screwed if this mentality has seeped this far into the culture. *Communicating secretly is a human right*. A legal right under international law (ICCPR article 17, ECHR article 8), and a constitutional right in any country worth living in. There can not possibly be such a thing as "too simple to exercise your human right to privacy". It's like asserting that it is too simple to choose your line of work, or that it is too simple to live in the city of your choosing.
and the government has an interest in protecting its citizens
The government has more than an interest, it has a legal obligation to protecting the human rights of its citizens.
>Btw. The https communication comparison does not hold, there is always a third party that can read what you say. E2E chats are effectively communication where evidence is instantly destroyed.
If I use a third party CA this is correct. But what third party can read communications over HTTPS between a client and a server I control with a self signed SSL cert?
This isn't correct with 3rd party CA's with modern TLS either.
TLSv1.2 has Perfect Forward Secrecy with DHE and ECDHE key exchanges and in TLSv1.3 PFS is mandatory. A compromised root CA or even leaf certificate these days protects you from a man-in-the-middle and not a whole lot else - the certificate private key is never used for session key derivation and the keys themselves are ephemeral and never sent over the wire so even intercepting the key exchange doesn't allow decryption of the stream.
Even if you don't have Forward Secrecy, like you decided to use RSA KEX which is a terrible non-default idea even in 2015 let alone today (this feature isn't even present in TLS 1.3 deliberately, lobbying to keep doing this failed), your private key is still needed so a third party CA can't imitate you.
The CAs have never been supposed to know your private key. For a long time now it's straight up forbidden on pain of removal from trust stores for the CAs to learn somebody else's private keys.
For the example of Let's Encrypt your client probably picks a private key and stores it where your web server can use it, but it never sends this key to anybody else. In fact if you care you can even have the key chosen by the web server and literally never send that key to the Let's Encrypt client at all, the client picks up a "Certificate Signing Request" and it goes OK, I see you want a certificate for some key you know but I don't, that's cool I will go ask Let's Encrypt to issue a certificate for that and let you know.
the problem with current government protecting its citizens by collecting their private communications is the next government having access to this sensitive data.
Yep, the next government may be evil tyranny, but it's beyond my comprehension why would I have to trust current or any government with the data I'm sure they'll abuse the moment they have it.
I bought myself an anker powerbank because of all the rave around them. Mine behaves incredibly strange. Charged in seconds, then not containing half a phone charge.
For a 20.000 mAh this was really disappointing.
Probably a one of but still leaves the impression that this was looked at because it ruined the price for others.
Had a tangential issue with an Anker power bank (screen was sometimes showing bogus charge essentially), and can confirm Anker E-Mail support is pretty good in my experience, they sent me a second unit (even though the first is still functional and I still use it just fine to this day), free of charge after a brief exchange.
They also did a recall on speakers (under their soundcore subbrand) for the same thing. I'm not sure if this is good or bad - they proactively contacted me to let me know about the recall.
reply