Kushan

That’s not strictly accurate.

The slicer is Open Source yes, but not the printer firmware or software. That’s closed source and proprietary to Bambu.

Now there’s some contention there because a lot of the features and ideas that make modern 3D printing as reliable and great were developed in the open, under open source licenses and Bambu has definitely implemented many of them in their printer firmware, but they don’t infringe any licenses in the printer software itself (as far as anyone is aware).

This whole debacle centres around the slicing software, which is separate from the printer itself (though is necessary to actually use the printer) and it’s AGPL.

Same, I am used to being the punch line in various jokes but I’ve never heard it referred to as “Irish Logic”.

Plus people knew the increase was coming so I imagine there was a spike in sales just before hand.

We have faster charging speeds with lithium today, 800v cars that can charge at 300KW+ have been on the market for half a decade, BYD has launched cars that can charge at 2-3x that speed. The charging infrastructure is the bottleneck there, even if all new cars could charge at those speeds it wouldn’t mean much because hardly any chargers can support it.

Besides it’s almost moot, most EV owners aren’t charging via fast chargers like you would fill up an ICE car, they’re charging at home at much cheaper rates and only using fast chargers for particularly long trips.

Sodium batteries are real though. You can buy them today, their big promise was that they would be cheaper than lithium batteries because sodium is abundant and readily available whereas lithium is a rare mineral. Then lithium prices fell through the floor and the value proposition failed, at least for now. They’re also not as energy dense, which is probably what will hold then back from EV use for a while yet, but the claim around being safer holds up.

You’ve done the hard work building the compose file. Push that file to a private GitHub repository, set up renovate bot and it’ll create PR’s to update those containers on whatever cadence and rules you want (such as auto updating bug fixes from certain registries).

Then you just need to set up SSH access to your VM running the containers and a simple GitHub action to push the updated compose file and run docker compose up. That’s what I do and it means updates are just a case of merging in a PR when it suits me.

Also I would suggest ditching the VM and just running the docker commands directly on the TrueNAS host - far less overheads, one less OS to maintain and makes shares resources (like a GPU) easier to manage.

You should look at restic or Kopia for backups, they are super efficient and encrypted. All my docker data is backed up hourly and thanks to the way out handles snapshots, I have backups going back literally years that don’t actually take up much space.

I’m not entirely sure what the “maintenance burden” even is on a tech that hasn’t changed in decades.

Only because of current RAM prices and artificial scarcity keeping those prices high.

300GB of RAM shouldn’t be that expensive. I have 1/3 of that in my server (bought years ago). If it wasn’t for the AI bullshit, 300GB would be fairly reasonable to buy in a couple of years time.

To be fair, not to defend the CEO at all but when this story first broke it was so wild that you knew someone had to be making up some serious bullshit but it was just so out there, it could have been either side.

Why anyone decided to pick sides is beyond me, this is why courts exist.

Fuck, I love ntfy, it’s one of the best self hosted push notification systems I’ve used. It has been flawless so far.

Don’t like this.

It was a couple of weeks ago for me but I managed to get my docker compose script for all my infrastructure cleaned up and all versions of containers are now pinned.

I have renovate set up to open PR’s when a new version is available so I can handle updates by just accepting the PR and it’s automatically deployed to my server.

Nice and easy to keep apps up to date without them randomly breaking because I didn’t know if a breaking change when blindly pulling from latest.

Absolutely! Here’s my CI pipeline, it’s actually super basic: https://gist.github.com/neoKushan/bd92031bb9c8db3320e8c19d5dae3194

Happy to answer questions if you like.

I just added my compose files to the repo, that CI file and set up renovate https://github.com/renovatebot/renovate to create my PR’s for me.

I generally agree with the sentiment but don’t pull by latest, or at the very least don’t expect every new version to work without issue.

Most projects are very well behaved as you say but they still need to upgrade major versions now and again that contains breaking charges.

I spebt an afternoon putting my compose files into git, setting up a simple CI pipeline and use renovate to automatically create PR’s when things update. Now all my services are pinned to specific versions and when there’s an update, I get a PR to make the change along with a nice change log telling me what’s actually changed.

It’s a little more effort but things don’t suddenly break any more. Highly recommend this approach.

The main argument against bsky is that they’re still holding all of your data, unless you self host your own server.

I don’t actually see how Lemmy is much different. Most users are not self hosting on Lemmy either, you’re trusting your data to a 3rd party. The main difference seems to be that there’s much more centralisation on bsky.

I think it’s entirely reasonable to be wary of any service, be ready to delete your account if it goes to shit or whatever it is you need to do to feel safe.

But right now, I like blue sky. I’ve had far more positive interactions on there than I ever had on twitter (even before musk took it over), the lists feature that lets you pre-emptively block entire swathes of dickheads is a game changer (I just block one group, anyone Maga) and I’m having a good time.

I expect I’ll get downvoted for this but honestly I don’t care, the world has gone to shit far too much for me to give a crap about what internet strangers think over my own health and wellbeing and right now I’m having a good time and will not apologise for it.

The second that stops, I’ll be leaving bsky.

My main issue with live service games is that I just don’t have the fucking time to invest in them.

I’ve yet to see a game move to live service that didn’t just pad out all the busy work and fuck with the pacing of any story element.

Give me a single player experience that I can push up 6 months later and not have to grind to get back to where ever I was.

From the paper itself:

We had a video-conference and numerous email exchanges with Bitwarden. At the time of writing, they are well advanced in deploying mitigations for our attacks: BW01, BW03, BW11, BW12 were addressed, the minimum KDF iteration count for BW07 is now 5000, and their roadmap includes completely removing CBC-only encryption, enforcing per-item keys and changing the vault format for integrity. On 22.12.25 they shared with us a draft for a signed organisation membership scheme, which would resolve BW08 and BW09. At our request, to maintain anonymity, they have not yet credited us publicly for the disclosure, but plan to do so.

I didn’t look at the response to other Password managers, but the gist here is that the article is overblowing the paper by quite a bit and the majority of the “issues” discovered are either already fixed, or active design decisions.

In your compose file, make sure you’ve added runtime: nvidia.

You also don’t need to deploy the resources and reserve the GPU, you can remove the entire deploy section when using the nvidia runtime.

I just changed my compose reference to update the volume and base image. Worked a treat.

Jellyfin is a fork of emby (from when it went closed source), so that makes sense. They have diverged quite a bit but seems the Auth hasn’t changed enough.

She’s an utterly dispicable woman. That doesn’t mean she’s wrong on this one issue.

It’s completely fine (and reasonable) to say “I hate this person and everything they stand for but on this one issue we’re in complete agreement”.