

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.
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
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.
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.
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.
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.
You might have seen a quest, where if you stream a specific game to your friends you get a free in-game item, but these are not advertisements.
…
Advertising is the practice and techniques employed to bring attention to a product or service. Advertising aims to put a product or service in the spotlight in hopes of drawing it attention from consumers
I have no interest in streaming “quested” games, and whatever deal Discord has done with the developer to encourage users to engage with such games (and by extension the game’s microtransaction economy), and regardless of what they call it, is by definition an advertisement. If you can’t see that, then you are an ad campaign exec’s wet dream. Either that, or a troll.
Discord enshittification is well under way, just this week I have started seeing ads in the client just above the voice channel status in the bottom left. Cancelled my Nitro immediately, no point if they are going to shove ads in my face anyway.
Currently looking at alternatives, Revolt looks promising, and can be self hosted.
I can’t speak from experience as I don’t own any Amazon devices, but I have read reports that it seems to work fine with the FireTV variant of Android.
The dev has only tested it against Chromecast with Google TV, with that said I’m using it on a Shield TV and a Shield Pro and it runs fine on both.
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.
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.