

This isn’t limited to Omarchy. It’s part of the way Docker works.


This isn’t limited to Omarchy. It’s part of the way Docker works.
Having worked at an email provider before, I can assure you that hosting your own email is not, as you put it, “trivially simple.” The number of spam filters that sit between every server is insane, and they’re all controlled by third parties that, almost universally, deem any server hosted on a residential IP address block to be spam. Even medium-sized commercial providers get blacklisted every so often and have to appeal to the filter providers to get back in business. Hosting it yourself is almost guaranteed to mean that nobody ever gets your emails.
Removed by mod


I would say that finding that balance is up to the individual admin and application, really, which is where the defense in depth comes in. Yeah, it’s rare, and if those exploits are being used it means you’ve got the attention of someone you probably can’t really stop, but it’s something to take into consideration. Bad configs can cause data leakage across container boundaries, too, so without knowing the admin’s skill level, I tend to recommend against sharing that hardware with something that might have something valuable on it. AI has made it easier for script kiddies to find zero-days and exploit APT-level vulnerabilities, too.


It masks the registration info, but it can’t mask the IP by definition, and that can still be traced back to you.


Removed by mod


It’s not about the container escape so much as the potential for someone to do a DNS lookup on your domain name and use that to locate you physically. Yes, it’s coarse location data, but someone on 4chan was able to locate Shia LaBoeuf from a single picture of a flagpole. It doesn’t take much.


I would NOT host a Lemmy instance at home unless you’re going to obfuscate your IP address. If you make it public, you’re inviting any whackjob that sees your username to find your physical location. Additionally, I wouldn’t host it on a PC that you actually intend to use for day to day stuff, just in case the instance gets hacked and someone manages to escape the container it’s in. If you wanted to do this, I would put it on its own box with Cloudflare in front of it, otherwise you’re inviting trouble where there doesn’t need to be any.
As I recall, it was a transient packaging bug that was fixed within an hour of it occurring, well before the video even aired.
Yeah it looks to me like TinyCore is either made by the same guy as DSL, or uses a substantial number of components from DSL. Either way, it feels very familiar to anyone who’s used DSL in the past, so I consider it a spiritual successor.
2024, when it was briefly reborn and then re-forgotten.
DSL is dead. Long live TinyCore.


Not for things like check deposits, unfortunately


I see what you did there


Life, uh…life finds a way
I think you mean “suite” instead of “suit.”
Yes. Life gets in the way sometimes.
The Intel Panther Lake chips apparently approach the same kind of battery life as the M-series chips, so the newer XPS machines actually look like a worthwhile competitor that’s capable of running Linux.
EDIT: The Framework 13 Pro also has a panther lake chip and promises pretty beastly battery life, so if OP is willing to wait, that might be a good alternative as well.


I know some people who would actually kill for a physical T9 keyboard so they could touch-type. It’s not my cup of tea, but I can definitely see it being a major draw for people who grew up texting on a real flip phone.
That I’m not sure about. It’s part of the official install docs for docker, though there is a big scary warning saying that that group gives you root permissions. Either way, I place the fault on docker more than Omarchy directly since it’s a group that gets automatically when you install it on any distro.