Assuming your Fiesta produces < 100g/km CO2, looks like you’ll now be paying £20/year (as it was manufactured before 2017, different rules apply) - could be worse!

Not quite. Even existing EVs (with some exceptions for older vehicles) will be charged the new basic VED rate of £195 when they are next due to renew (which could be in up to a year’s time).

What EV purchasers were trying to avoid was the expensive vehicle supplementary tax of £425/year for cars with a list price of over £40k, which EVs purchased/registered since the start of April are no longer exempt from.

As the vast majority of new EVs on the market fall into that price bracket (including all Teslas except the base tier Model 3), suddenly the yearly tax for most new EV purchases jumps from £195 to £620/year.

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.

How often do you need to travel the entire range your car allows?

If you do need to drop everything and drive across country in an EV, you should be stopping at service stations to do short fast charge sessions anyway, as with modern fast chargers and battery tech you will typically go from something like 30% SoC to say 70% in only a few minutes. This saves a lot of time on longer trips.

If you are driving an EV by depleting the battery completely and then charging it back to 100% every time, you are doing it wrong.

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.

Solution: don’t read that shitrag. It was always a waste of paper, now it is a waste of bandwidth as well.

I’ve tried Copilot and to be honest, most of the time it’s a coin toss, even for short snippets. In one scenario it might try to autocomplete a unit test I’m writing and get it pretty much spot on, but it’s also equally likely to spit out complete garbage that won’t even compile, never mind being semantically correct.

To have any chance of producing decent output, even for quite simple tasks, you will need to give an LLM an extremely specific prompt, detailing the precise behaviour you want and what the code should do in each scenario, including failure cases (hmm…there used to be a term for this…)

Even then, there are no guarantees it won’t just spit out hallucinated nonsense. And for larger, enterprise scale applications? Forget it.

I grew one during lockdown, decided I liked it and kept it. I suspect I am not an anomaly in this.

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.