

“Visio” is their internally developed video conferencing platform. It’s part of their “La Suite Numerique” suite of software, most of which is open source in large capacity


“Visio” is their internally developed video conferencing platform. It’s part of their “La Suite Numerique” suite of software, most of which is open source in large capacity


They’re portable and don’t require that I install anything. If I’m looking for an odd tool, it’s usually the easiest way to download and test something out. It’s just nice to have a standalone executable.
Flatpaks are fine, I really have no problem with them in theory but I spend twice as long configuring them as I do with a native program, and I have to trust that the maintainer is affiliated with the project, which isn’t always the case.


I think they were getting at Flatpaks, Snaps or AppImages (my personal favourite)


I hope this has movement that feels in any way similar, but aesthetically this looks interesting.


Interviews do typically count, it just has to be citable. Videos are sufficient in that regard as well, not just articles or books. It would be different if Torvalds had edited his own wikipedia page, but an editor who updates the page and cites this video would not be in the wrong.


I mean, I feel like he outright confirms it in the video. It’s his distro of choice since it allows him to easily use his own compiled kernels in testing. Anything else is an inconvenience to his work.


How’s the overall health of the drives? You might want to get a quick SMART report.
Otherwise, this sounds like pretty normal drive activity. It could be the result of anything from indexing tools to casual background processes doing a read.
If it’s periodic in a way that’s consistent, then it’s almost definitely something in software. What docker services are you running? Do you have any auditing tools or security processes that might be actively logging activity?
It’s pretty unlikely you’ve contracted malware unless you’ve gone out of your way to expose the server to outside sources, so I think you can alay those concerns.


A couple points:
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.


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.


I had completely forgotten this limp puppet corpse of a game had come out at all. I saw 0 marketing for it, saw a ton of bad reviews and then it disappeared into the void.
I’m actually more surprised to see any further news about it, given it felt like the kind of thing that folds a studio in half.


Most domain registrars make whois info private by default these days. It’s typically just a toggle. Same with DNSSEC


Yes. Texture and asset streaming is affected pretty significantly by the speed of your storage. Load times are a large part of where SSDs of different classes can help, but the better your SSD performs for I/O operations, the better for overall visual performance.


I don’t feel like this is a terribly recent attitude. It’s definitely one I’ve encountered repeatedly over a decade or more of dipping my toes in the pool. It’s not incorrect in a lot of circumstances, but it’s very difficult to find support when no one wants to help you improve. There’s always been a significant degree of ego in Linux user communities.


That’s exciting. It looks very clean, but until it has the tv remote support aspect I think it’ll wait
Flatpaks are basically containers, allowing applications to maintain their own dependencies separate from your system. It’s similar to a Windows program shipping with its own precompiled DLLs, helping prevent dependenct conflicts when you go to update something you installed with pacman or yay.
Arc support was added after release to Linux Kernel 6.2 and it’s steadily improved since. Older Linux distros, or “LTS” oriented distros that favour stability may still not have support for them. I know Unraid was very slow to pick up on it and I had to settle for passing the pcie device through to a VM to get it working. Intel is keen to made these viable though, and I love having the AV1 encoder from my A380.


That one sounds squarely on Nvidia. Any driver that uses undocumented workarounds to gain kernel level access or utilizes an access loophool for system hooks is a bad driver. I’d assume Debian, or likely more accurately the Linux kernel itself was updated following some matter of CVE that Nvidia was quietly abusing.
Frustrating, but a good example of why those kinds of proprietary drivers are such a nightmare. You really just don’t know what techniques they’re using.


Biggest difference is that wormhole will pass traffic between devices on different networks as long as both are routable. So it’s not limited to a local network connection.


Honestly the idea of a Gamepass Centric handheld is one I’m surprised they didn’t go for already. If they push it with just the Xbox styled front end, it’ll probably be more appealing than the xbox itself
I wouldn’t expect that to change. Their primary intention is in building out a suite of tools for use within their own government institutions, rather than a wider audience. If you’re interested in self hosting though, the Github documentation is pretty much all in English