Basically a deer with a human face. Despite probably being some sort of magical nature spirit, his interests are primarily in technology and politics and science fiction.
Spent many years on Reddit before joining the Threadiverse as well.
Warl0k3 has posted elsewhere in this thread with information about how these logs are generated and kept, they’re event data recorders. They need to meet federal standards which presumably would include protections against having the data rewritten like that. Seems likely that if this was being done it would be a serious crime and probably a bigger news story than the crash itself, do you have any actual sources?
Capability, sure. Do you think they actually did, though? That’s a positive assertion that I would want to see some kind of actual evidence for beyond an assertion by some random commenter on the Internet.
I suspect you don’t have any evidence because if there was I think that would probably be by far the bigger story here. Which is why I expect Tesla would refrain from taking the risk of tampering with logs in situations like this.
What “defending?” I’m explaining where they got the information from. It’s literally in their preliminary report. I said nothing beyond that fact.
They read the logs themselves. The NTSB routinely does investigations and Teslas are a popular brand of car, why wouldn’t they have the ability to read their logs?
Really. Do you have any sources that indicate that?
Yeah. That’s always been my nightmare driving a regular car too, the “stop” and “go faster” buttons are right next to each other and in a place you can’t see them. Such a weird standard, presumably a result of the requirement for physical linkages from early in car history. Would have been nice if electric vehicles had provided an opportunity to rethink that paradigm.
They checked the car’s logs.
Electronic data recovered from the vehicle indicated that before the crash, the driver manually overrode FSD (Supervised) by pressing the accelerator pedal to 100%
So no, looks like they checked the logs.
The older the jpeg the more likely it is that he’s moved on to another job by now.
I didn’t say anything about the “prevent instances from being overloaded” part being good or bad. I didn’t even give an opinion on ActivityPub, just pointed out the practical limitations and incompatible design goals.
Personally, I’ve got no problem with websites implementing rate caps and whatnot to ensure that their traffic remains within the limits they can handle, or throttling specific IPs. I am very concerned with how Cloudflare in particular has become the single centralized “gatekeeper” for vast swaths of the Internet, though. If they decide that some particular client isn’t allowed to see stuff then poof, a big chunk of the Internet is cut off. That’s worrisome IMO.
Your original post didn’t specify a particular kind of data scraping. TropicalDingdong had no way to know you were only specifically interested in that one kind of data scraping, so his comment is appropriate - you can’t stop data scraping in general, and attempting to do so in the general case goes directly against the goal of ActivityPub.
This sort of nonsense, along with idiocy like that guy who uses the þ character in place of “th” in all his comments, does absolutely nothing to hinder AI training. The only effect it has is to bother human readers. Completely counterproductive.
That’s a very narrow view of data scraping, there’s lots of ways to get data.
The Fediverse is built on ActivityPub, which is an open protocol that’s designed to broadcast data with no limitations or restrictions. If you don’t want your data to end up in the hands of anyone who wants it - including those nefarious AI trainers - then that’s an inherently incompatible goal with ActivityPub.
If you’re just worried about specific instances being overloaded with requests, then sure, all the usual rate limiting DDOS-prevention Cloudflare tricks will work. But the data itself isn’t “protected.” Someone who wants it could simply run an instance of their own specifically to collect it.
He was an incredibly prolific poster. Unfortunately I found him to be rather abrasive, I don’t recall any particular interaction but I do get an “oh yeah, that guy. Glad he’s not been around much lately” sense when I see that name.
The world is changing. It happens from time to time. In this case the change is a particularly big one and it’s still ongoing, so I can’t make any predictions about where it’s going to end. But I can be pretty confident that it’s not going to magically change back. So my best advice is to try out the new tools, see whether you can adapt to them and use them to improve your own productivity in new ways, and if not then as a fallback start looking at other directions to take your career.
Harsh, perhaps, but the world does as the world does.
The best part of DS9’s Section 31 was that Section 31 knew they were the bad guys too.
Witches can be found everywhere once you start hunting for them.
And even if it was 100% vibe coded, how could one tell? The code has never been published before so there’s no way to determine its origin.
Pride and Prejudice and Zombies is based off of public domain sources but it is nevertheless under copyright itself. So even if the output of LLMs was public domain (not something that has been clearly or universally established) that doesn’t mean a project incorporating it would have to be. Public domain is not “viral.”
It’s not accidental acceleration, though. The driver had the accelerator pressed 100%.