In 6th grade, my teacher read us the same book mentioned in the Tumblr post. It’s called “We all fall down”, and it’s written by Eric Walters and is a fictional account. At the time, the book had only come out a couple years prior. It’s a good book. It’s well informed, well written, and it never talked about who was to blame, only the tragedy that occured. The author is also Canadian and he wrote a sequel that covers the aftermath and emotional trauma for survivors and their family members. It’s not a book about the attack, it’s a book about loss, grief and shock, and about how people can come together to heal from it.

Of course, it sure doesn’t sound like this teacher was trying to send that message. I just wanted to shout out a good book.

A couple points:

• Your website does not properly convey the technical context of Safebox. Docker is a complex platform, and asking someone to install it point blank on any OS, while also championing ease-of-access feels at odds here.
• There is a severe lack of documentation about the tool. Discord is not an appropriate means to find these documents if they exist. It is rarely okay as a support channel.
• I saw your post from a few days ago, but it was framed as a question about about gatekeeping specifically. The post also advertised Safebox. Given that the post no longer exists (but the comments sure do), I’m inclined to think you didn’t get quite the answer you were looking for.

I dove into self-hosting several years ago and ultimately I think I found the experience quite welcoming. I also don’t know that Safebox has a lot to offer over well-established alternatives these days like Unraid or TrueNAS, which have large user-bases and a depth of support articles to help admins better understand what they’re doing and how to do it. It’s true that not everyone would want to do this as a hobby. No one wants their services to break, or their data to be lost, and more tools that make it easier to prevent these scenarios are helpful. With that in mind, I am not left with a clear understanding of how Safebox is meant to provide safeguards here.

I used the word “admin” in the previous paragraph for good reason. Self-hosting makes you the administrator, and it means that you, the administrator, have the power to make mistakes. My recommendation is not to talk down to your users. Someone interested in self-hosting should be aware of the potential security implications of what they’re taking on, alongside the risk to their data and that breaking changes are something they can and will make along the way. If you really want to make self-hosting accessible, then the documentation for your tool needs to be accessible too.

Safebox runs on Linux, macOS, and Windows, supports both x86 and ARM64 (including Raspberry Pi, Banana Pi, and others), and handles domain/subdomain setup, Let’s Encrypt certificates, DNS configuration, reverse proxy (nginx), and also offers WireGuard-based remote access.

A user should be able to learn why these elements are important and how they work together. Talk about the limitations of running it on a raspberry pi vs a workstations or server. What’s a reverse proxy? Is WireGuard good? This doesn’t mean the average person needs to know how to configure detailed permissions or application configs, and if the goal is to provide a repository of pre-hardened Docker configs for use then that’s cool too, but there should never be a barrier to the information itself. Especially as it is relevant to the tool you’ve built.

I think that fundamentally, you’ve built a good tool that simplifies things someone who is already familiar with its components, and where it needs to improve is by expanding to help new users familiarize themselves. Education is as big a part of accessibility as the ease-of-setup.

If this is based on the GamersNexus videos, those are pretty absurd hit pieces that seemed to come from some bizarre place of resentment. They’ve had process issues when it comes to how they benchmark hardware, but never anything paid or purposefully misleading.

I’m honestly wondering if you’ve confused it with something else.

Yep. Two different platforms with different developers

I mean, they have done it. When I was looking at phones a few years back, it was genuinely a toss up between a Pixel 4a and an iPhone SE. If all you need it to be is a cameraphone, then both were good options.

Even now, the iPhone 16e is a relatively inexpensive phone when considering its featureset, but I would prefer a “mini” or newer SE variant instead.

Brother you have eaten the onion

Something KDE has done seems to have resolved the issues I used to have with DPI related scaling problems in Wayland. Once Plasma 6 hit, it’s been nothing but rapid improvements with Wayland as a focus and man does it feel nice.

That said, there’s virtually no downside to still using X unless you have explicit display features you need from Wayland like HDR or the per-display scaling. Xfce is stupid lightweight and still my default for anything where battery life is a benefit.

It’s been interesting, watching the lag here. This feeling was felt by many who played games on PC 15 years ago when DVDs were starting to become less common and games were expanding in size. I distinctly remember buying a game I was excited for only to learn now I had to spend part of my data cap on downloading it. What had even been the point of buying the boxed copy?