TWiST News: Tesla Robotaxis, Electric RVs, and How Startups are Helping Secure Elections | E2025

[@Chewy777100]

Jason loved the lightship guys so much it brought a tear to my eye

[@barriehep]

Always appreciate the founder interviews 😊

[@mattyk35nyc]

electric RV's?!?! love it

[@williamthompson3639]

Imho Electric RVs will attract a new generation of buyers and will also capture market share in the travel trailer space (largest segment). On average, RV owners purchase four to five RVs in their lifetime. Before the rise of RV rental marketplaces, RVs were often seen as depreciating 'toys.' Now these assets can be monetized, typically reaching break even afyer 4-6 rentals

[@mikecoker5961]

I don't understand the LightShip RV market. It doesn't seem like a fit for people that buy a RV. The idea that it has windows everywhere because of "the view" makes no sense. The purpose of the RV is a retreat away from being outside where you enjoy the view. The purpose for the RV is a place to rest, relieve yourself and eat. You're not going to want to spend your vacation inside of it. Maybe it has a purpose as a mobile work area, but I don't get the RV part.

[@bnjiodyn]

Tesla's robotaxi production will grow by more than 30% a year. Growth will be based on demand, and demand will be very high if tesla is first with a global unfenced mass-market robotaxi. This is likely a 3x growth per year or more till projections on demand level. ...Just the commercial transport sector alone will demand more than a doubling of capacity per year.

[@petermaltha]

Two is logic because you have the other 3,Y and X to use bigger. All of you forget that 95 % is one person transport.

[@ibgib]

19:08 - this style of human + ai multiplayer editing shows just one perfect use case for ibgib's semantic data protocol. The fact that theyre using regular expressions here should show anyone with a nose for money the opportunity missed out here, not to mention ai + human multiplayer IDEs which are all failing to address the core design shift required right now. Huge opportunity

[@ibgib]

To be more explicit in this particular use case, in ibgib, you can think of the document itself like a git repository and section chunks like files. When you make edits on your local machine, it's like committing to your local branch and the main document (in the cloud probably) as the remote branch. Your local branch pushes updates, all content addressed, to the remote. Other parties are also receiving these changes like git pulls. The ai itself is just another participant with its own local branch. This timeline + chunking approach works not just in text editing but in most command pattern scenarios (basically anything with an undo/redo stack) where order is not important. That is still solvable but requires either locking or more complex conflict resolution. So if you have a photo editor - and guess what we can just consider the ai models themselves as the photo editor "apps" - then you can use the same architecture to iterate non-text components as well. There's so much more with this approach if you could just stand on your tippy toes and peek outside the box.

[@ibgib]

Im in San Antonio if you want a demo