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.
We refer to it as kew-bee-cuttle
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.
Nah, the SWAT would have to arrest themselves.
Regarding battery degradation - I’ve owned my EV for 4.5 years now, and its battery is still at 93% of its original capacity. That equates to maybe 10 miles of range lost, from an original range of around 230 miles. At that rate, it’ll still be giving usable range in 10, 15 years from now. It’s even warrantied to keep over 75% of its original capacity for 8 years / 100,000 miles - if it fails to achieve this (likely due to some defect), it’s replaced for free.
And when it does eventually need replacing, it can be recycled into something like a home storage battery - where the power demand is not as high, but still more than enough to power everything in your home for days. Meanwhile, the car can be upgraded to a brand new battery, which will likely last even longer.
Edit: In fact, I tell a lie - I did have to replace a battery on my EV recently. The 12v lead-acid battery, that ICE cars also rely on.
For digital copies, they could bury this into the EULA and make it a requirement that you agree to it before you make your purchase (IIRC some storefronts do this already).
However for physical copies I suppose there could be a case made if the duration of support was not disclosed at the time of purchase (or it was not printed somewhere on the outside of the packaging).
I use both. Pi-hole running in a docker container on one of my home servers which my gateway is configured to assign as the default DNS for all clients, and uBlock Origin on all my browsers to catch everything else.
Pihole is pretty good at catching ads on platforms that are not suited to browser based blockers (IoT devices, streaming boxes etc) but it isn’t perfect and is best used in conjunction with another solution.
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.