Same, I set it up a few years ago and both me and my partner have been using it since then with no issues at all, it’s completely replaced Google Photos for us.
We’ve also set up immich-frame and repurposed an old Google Nest hub to use as a digital photo frame.
Cable wasn’t as much as a thing over here except in specific areas, but if you were flush you might have satellite TV. Nothing so bourgeois for me though!
I was born in 89, so remember a good portion of the 90s. It was a much simpler time but obviously we tend to romanticise the fun memories and quietly ignore how vastly more inconvenient daily life was.
Mobile phones were not really a thing yet so getting in touch with your friends required a combination of patience and sheer luck.
The internet was a different place entirely and was experienced in 30 minute chunks of time, just long enough to download a song or two before being kicked off for tying up the landline.
Daily entertainment was 4, maybe 5 analogue TV channels, plus a collection of VHS tapes which are all degrading by being rewatched constantly.
Every piece of life admin that you would normally do online today was instead done with pen and paper.
Honestly, I’m amazed we ever got anything done.
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’…
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.
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.
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.
There’s a lot to cover here but I’ll try to touch on each point:
The key requirement is fast memory that can be addressed by your GPU, and ideally a lot of it - hence the insane cost of this hardware right now.
Remember that you need space for the model’s weights (think of this as its ‘knowledge base’) and the context window, which is basically the data needed for the LLM to keep track of your current conversation with it (effectively its short term memory).
With smaller pools of VRAM (8-16gb) you will have to compromise and either have a more capable model that will lose context quickly and start hallucinating, or a less capable model that can maintain a session for a bit longer but overall less ‘smart’.
For software - there are a couple of options for running the LLM itself, Llama.cpp is one of the more popular tools and is the one that I use. It has a web UI with the usual chat interface, and also exposes an API that you can plug other tools (e.g. opencode) into, depending on your use case.
In terms of hardware recommendations, at 20GB+ of VRAM you do have a bit more headroom compared to more consumer grade GPUs, but to be honest the most cost effective way to get a shitload of VRAM is likely not with a dedicated GPU but actually using a system based around a recent APU.
I got a Minisforum MS-S1 last year for exactly this purpose. It is based on AMD’s Strix Halo platform which it has in common with the Framework Desktop and a couple of other similar devices.
It has 128gb of unified RAM which can be divided between the GPU and CPU however you like, so plenty of capacity for even fairly chunky models. It also uses a tiny amount of power compared to a more traditional system with a dedicated GPU, while also giving really reasonable performance for most AI workloads, more than enough for use in a homelab.
For cloud rental - doable, but pricing is a factor, and of course this will not actually be running locally.
Usability - manage your expectations, but overall for a lot of use cases and of course depending on the model that you are running and the resources you throw at it, it can be comparable with especially older iterations of ChatGPT, Gemini etc.
But remember, you are not a Google or an Anthropic and do not have an infinite pool of compute to throw at your model, nor do you have access to the specific models they are using.