You are assuming that they have a personality to begin with.

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.

As others have said, 100% a leak.

I would advise to stand on a chair or stepladder underneath the ceiling and check to see if it is still level. If you see an obvious deformation around the stain, this will be being caused by water pooling on top of the ceiling plasterboard. In which case, once the leak is sorted, you will likely need to drain the pooled water, cut out the damaged section, replace it, then replaster and repaint.

We had exactly the same issue in our last house. It was in a difficult to see spot hidden behind our kitchen cabinets. We only realised the severity of the issue when the ceiling boards gave way and fell on my head.

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

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.