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’…

I’ve switched both my laptop and desktop over to Linux (Bazzite and Fedora respectively) in the last 6 months.

The last time I tried to daily Linux (over a decade ago) I ended up switching back eventually, but this time I really don’t think I’ll need to. All of the games I play most often work perfectly, the dev tooling is even better than it is on Windows, and the hardware compatibility side has been completely flawless.

Gone are the days of having to hunt down obscure Linux drivers for your touchpad or webcam. Everything just works out of the box.

Because, unless you’re driving a forklift, the point of a vehicle’s rotation is in line with the rear wheels, meaning you can take turns at a much more acute angle when reversing than going forwards. Which makes backing into spaces much easier.

Notice that most of the half-assed parking jobs you see are generally people who have driven forward and left the car parked at a diagonal half out of the space, because getting the vehicle lined up in that situation is more difficult.

Well, I’m currently writing a service and frontend, both in C# (Blazor for the UI), and using docker-compose to build and deploy them to a Raspberry Pi running Linux. So not only cross-platform, but cross-architecture as well.

This is not a new thing either. Since .NET Core was released almost 10 years ago, it has supported cross platform development.

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?!

We refer to it as kew-bee-cuttle

I have a IIIXe (very similar to the one in OP) somewhere. Really limited in what it could do, but very cool for the time. I also have a later model Zire somewhere that had enough horsepower (with a mild overclock) to play Quake.

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.

I have a Model 3 at the moment. I’ve had it for almost 5 years and it’s generally been great - cheap to run, quiet and comfortable on longer trips but still fun to drive on back roads.

Recently it had its first major breakdown, and although Tesla service did manage to take care of it, it’s got me browsing for new EVs - but now, buying a Tesla is not the foregone conclusion it once might have been.

First, they have been making some truly stupid design choices in their latest facelifts (deleting the indicator stalks and gear selector).

Second, their CEO has now gone completely mask-off fascist.

Third - after a few years for the competition to catch up, we now have genuine alternatives from other marques which are just as good if not better EVs than Tesla’s offerings.

I think my next car will likely be a Polestar 2.

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.