Personally any game that requires a rootkit in order to play is not a game I'm interested in, from either a gameplay or a security point of view.
2017: covfefe
2025: cvefefe
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?!
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.
Not exactly crazy but just mysterious...this was at a software company I worked at many years ago. It was one of the developers in the team adjacent to ours who I worked with occasionally - nice enough person, really friendly and helpful, everyone seemed to get on with them really well and generally seemed like a pretty competent developer. Nothing to suggest any kind of gross misconduct was happening.
Anyway, we all went off to get lunch one day and came back to an email that this person no longer worked at the company, effective immediately. Never saw them again.
No idea what went down - but the culture at that place actually became pretty toxic after a while, which led to a few people (including me) quitting - so maybe they dodged a bullet.
I grew one during lockdown, decided I liked it and kept it. I suspect I am not an anomaly in this.
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.
Rookeh
0 post score0 comment score
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.