• 1 Post
  • 25 Comments
Joined 3 years ago
cake
Cake day: July 15th, 2023

help-circle

  • We are talking about Tesla robotaxis. They certainly do drive in very limited geofenced areas also. While Waymo now goes on freeways only in the Bay Area with the option being offered to only some passengers Tesla Robotaxis do not go on any freeways ever currently. In fact they only have a handful of cars doing any unsupervised driving at all and those are geofenced in Austin to a small area around a single stretch of road.

    Tesla Robotaxis currently also cease operations in Austin when it rains so Waymo definitely is the more flexible one when it comes to less than perfect conditions.








  • The unsupervised cars are very unlikely to be involved in these crashes yet because according to Robotaxi tracker there was only a single one of those operational and only for the final week of January.

    As you suggest there’s a difference in how much the monitor can really do about FSD misbehaving compared to a driver in the driver’s seat though. On the other hand they’re still forced to have the monitor behind the wheel in California so you wouldn’t expect a difference in accident rate based on that there, would be interesting to compare.



  • This seems like your standard open core/dual licensing, CLA controlled BS where open source is indeed treated like an inconvenience… Perhaps with more obfuscation than on average. Probably not really adding requirements on top of AGPL as such but they seem to be offering multiple releases under a more restrictive license either because they have the rights so they can do dual licensing or they keep certain components proprietary and don’t offer those with the team/community editions.

    So yeah, probably within their legal rights and I assume there is still a codebase/release that you can use under the terms of the AGPL but they do seem to be looking for ways to make it be used as little as possible.

    I could be wrong if the AGPL and other open source parts aren’t enough for actually compiling a functional version of this but this is what it mostly looks like to me.










  • Well, parent poster was talking about Mastodon, you seem to be talking about threadiverse platforms like Lemmy. One thing that applies to both and every single platform that is large enough for that to happen is that you’re always going to lose out on a lot of the content because there is just too much content for one person to look at. It isn’t actually that difficult to subscribe so much that you get past that point in my experience.

    For the Mastodon-type fediverse microblogging platforms there’s some things that can help when trying to sift through the more popular stuff more (and less) similarly to how an algorithmic timeline would do it. Boost bots that track what’s trending and tools like Phanpy that allow you to check out what has been boosted the most in your recent timeline. There’s also starter packs (currently a fedidevs third party feature but will be added to Mastodon in the future too) and Sharkey antennas that let you watch for keywords over all the posts that flow through your instance. When it comes to things that aren’t here yet but are being worked on Fediscovery seems very promising.

    Maybe some of that stuff should exist for Lemmy etc. too or maybe the “all” feed could be improved.