Does anybody have recommendations for a drink carbonator? (like a sodastream)

My partner likes fizzy drinks. I want to get something that will last, and won't lock us into a single vendor for refills or replacement parts.

I looked at making our own custom one - like this. We might still do something like this, but I'm also pretty clueless with this stuff and don't want anything to explode or poison us :)

Our priorities, ordered by importance, are:

• No lock-in (adversarial interop is fine)
• Well built/long-lasting
• Convenient, safe, easy to use

Any suggestions?

This was quite a damning read, and not just for the sake of being damning. I can relate to a lot of it. I think the most common feeling I have on the trains is one of uncertainty: do I have the right ticket, am I on the right train, will i get a seat? It's frustrating that the everyday experience is so poor - even if they're running late, they don't have to be so stressful.

This means I can't skip to the next podcast as soon as they're done, I instead have to use the "fast forward 30s" button to see if there's any other content. And then inevitably I'll press that button with 29s to go and it will jump to the next episode, losing where I was up to. So if I do want those last crumbs of content, I have to return to it manually.

This post is part of a series explaining the authour's steps into self-hosting again. The earlier posts were more focused on the authour's specific priorities and why it's important to them. This informed both what they are deciding to self-host and the order of deployment/how things are set up. This post is the first one that takes a more technical angle, and the initial steps they took setting things up.

I enjoyed this post, and the series by the authour, because what really comes through is the sense of why they are configuring things certain ways and what their priorities are. Many other blog posts I've read jump straight into this step - how they configured the server. But throughout this series, I really get a sense of why the authour decided to configure it a certain way and I find that enjoyable to read. They were very systematic and thorough in building an inventory of what dependencies they have and their priorities for replacements.

This post is by Tara Tarakiyee, who works at the Sovereign Tech Agency. For avoidance of doubt, I am not the authour of the blog post.