I have witnessed companies make this exact mistake before - they have a legacy system written in $LanguageA that they either cannot find developers to maintain, believe is badly written, or does not support some new feature they want to implement (or some combination of the three) - and decide to solve this by taking the existing codebase and porting/transpiling it to $LanguageB (which is more modern, performant, is easy to hire developers for, etc) - without actually rewriting or rearchitecting anything.

What they are actually doing is substituting one kind of tech debt for another. The existing code that was poorly written and/or not well understood is now just bad code written in a different language. Fixing bugs or implementing new features now takes just as long, if not longer to account for the idiosyncrasies of how the code was ported.

And now this is being done by AI with even less oversight than usual? Recipe for a maintenance disaster.

There are only two industries that call their customers ‘users’…

2017: covfefe

2025: cvefefe

Right now none of the native clients support SSO. It is a frequently requested feature but, unfortunately, it doesn’t look like it will be implemented any time soon. As with many OSS projects it is probably a case of “you want it, you build it” - but nobody has actually stepped up.

For web access, stick it behind a reverse proxy and use something like Authentik/Authelia/SSO provider of your choice to secure it.

For full access including native clients, set up a VPN.

Oh fuck me, HOW in like 25 years did I not get that pun?!

As a developer myself I’m not sure if I would trust any application to safely handle a configuration that has become invalid due to a breaking change, especially not an app that is still under active development! Better safe than sorry.

Immich has completely replaced Google Photos for me, love it!

My only bugbear is that it is updated very frequently (what a nice problem to have!) which in my case requires a manual once-over of my docker-compose file every time in case there are breaking changes.

Not at all.

Lemmy is overwhelmingly militantly anti-Tesla, which is understandable considering who owns it, but it does mean that users tend to interpret any neutral or factual statements (basically anything that is not outright criticism) as having a pro-Tesla bias.

In this case, all I am stating is the fact that this specific change currently only affects corporate users. That could of course change in the future.

There is a rich history of cloud based data providers pulling the rug from under users with no warning. Look at what happened to Nest users when Google took over.

There is most likely an overlap on what you can get from the OBD port, but generally speaking the API will provide more high level info e.g driving status, mileage, live location - and the OBD port will provide more low level data e.g. detailed battery stats from the BMS, energy usage, etc.

Highlight where in the above post I am defending anything.

Something to note: Tesla has two vehicle APIs, the Fleet API for commercial accounts and the Owner API for individuals. This change currently only impacts the Fleet API.

If you are an individual owner who accesses your vehicle data from the Owner API (usually via a self hosted tool like TeslaMate), this does not affect you. Yet.

That also means we can still use the expansion cards for the Framework in any other device that also has a USB-C port. Need an SD card reader or a 2.5Gb LAN adapter? Not a problem, I’ll just grab one from my laptop.

I can’t speak from experience as I don’t own any Amazon devices, but I have read reports that it seems to work fine with the FireTV variant of Android.

The dev has only tested it against Chromecast with Google TV, with that said I’m using it on a Shield TV and a Shield Pro and it runs fine on both.

Google is already doing this with their default Android TV launcher. I tolerated their home screen ‘recommendations’ for a while as they occasionally highlighted something interesting to watch, but one day I switched on the TV and was greeted with a huge advert banner for a fucking watch on the home screen.

At that point I spent a few hours setting up FLauncher on all my ATV devices.

Same. Coming up to 4 years owning my Model 3 with no major issues and no work needed other than normal serviceable items common to all cars (tyres, wiper blades, cabin filters, etc).

On the flip side, one of my old coworkers who got his Model 3 at the same time as me had a litany of problems from day one. We used to joke that his car had been built by an intern on a Friday night before a major holiday.

I don’t do enough miles these days to justify getting rid of a perfectly good, functional, almost brand new car and buying a new one - I plan to just run it into the ground instead.

I don’t think I’d buy another Tesla in the future, though. Not necessarily because I care what people think of the car I drive, but because Tesla has made some astonishingly stupid decisions with their new/refreshed cars. No physical drive selector? No TURN SIGNAL STALK? Yes, because I love having critical vehicle controls on a movable surface. Come on now.

Unlike oil, rare earth minerals can be recycled to a degree. What is today your car battery may end up in 10+ years as someone’s house battery, or a power bank or other low-load energy store. The raw materials can eventually be recovered to an extent as well.

A resource disaster is inevitable either way as nobody wants to give up the convenience that we have become accustomed to. Encouraging affluent economies to adopt EVs is pure damage limitation at this point, our biosphere is already fucked from over a century of waste emissions, the least we can do is try and find solutions that don’t involve burning fossilized plant matter for every car journey.

Doesn’t really surprise me, I’ve had a Steam deck since launch and the performance on Windows titles has always been impressive, even considering its relatively low-end hardware.

The only thing preventing me from dual-booting my desktop is lack of software RAID support in most distributions (by this I mean RAID configured in the BIOS but not using a dedicated hardware controller).