My hotest selfhosting take is that stuff I use in my day job, docker/k8s/cloud is not worth it and generally worse for long-term self hosting than a Debian box.
Like I have the skills to troubleshoot containerized setups, it’s litterally my dayjob, but I’d rather not deal with it in my freetime unless there is no other way to run it.
What advantage does it have compared to Matrix?/IRC?
Kocialism is when you get your friend to install KDE
And when enough of your friends install KDE THATS Kommunism
~DicK Wolff
It’s not really ambiguous at all.
A stable distro is one that doesn’t update packages except for security updates within the lifecycle of a release.
You can install debian 13 on release day in 2025 and when it gets deprecated in 2030 it will be functionally the same.
A byproduct of that is that apt updates are very unlikely to break anything.
None of that changes that you can run sudo apt remove dpkg or rm -rf / or dd in=/dev/zero of=/dev/sda1 (this one might actually work).
But for your average desktop users it means you don’t boot up your laptop and have to learn how to use libreoffice 26’s new UI on the day you need to finish an assignment.
This seems like slop for all the Ubuntu haters, but i agree moving to testing isn’t a good sign.
TBH while I like the hardware of my laptop, I’ve been pretty unimpressed by the software that Tuxedo provide.
While i appreciate not having snaps by default, the control center they ship is an electron app that requires /tmp be executable out of the box, and talks to a backend daemon that wasn’t particularly secure by default, and both live in /opt despite coming from the distro itself, so I think it’s ironic when people engage in technical sneering while throwing stones from within their glasshouses.
Also boot security doesn’t seem to be a priority for them out of the box, this seems like what they should focus on IMO, instead of switching their base
✘ CET OS Support: Unknown ✘ Linux kernel lockdown: Disabled ✘ Linux kernel: Tainted ✘ UEFI secure boot: Disabled
That it’s good enough as a distro, although I’ll probably just switch to neon if Tuxedo move to a rolling release base.
laud Debian for its stability, but you can easily break it with one wrong command.
Well because that’s not the stability release schedules are talking about
the industry has moved beyond simple IP address checks to deep packet inspection of wireless network identifiers.
I don’t think this is a good description of what happened.
The app likely used the BSSID based location service or even did that itself with their own service.
But it renders the advice kind of useless:
While they cannot stop BSSID collection at the network level
They litterally can, no app installed from the app store is setting your interface to promiscuous mode & manually reading SSID headers, if you don’t give permission to use location services they can’t read use the services that translate BSSIDs into locations.
Whereas Discord the Nazi & groomer site, is completely pedophile free?
Weird to consider Google Pedos you want to keep away from your Discord account.
Seems like you could use swap if this is just running out during parts of the install.
Define securely.
I’ve run my nextcloud online for a few years with no incidents, it’s behind Apache, I keep it up to date, I have a bit of extra hardening (but none of it really hardens nextcloud itself it would just make running exploits on my server more visible).
It doesn’t really add security in the traditional sense but for a personal server logging outbound traffic and having it email me when something non standard initiates a connection also gives me an added sense of security.
Because snaps is a Ubuntu thing, and not particularly widely used on Debian.
#rank name inst vote old recent no-files
2 util-linux 4000213 2110588 1172784 345252 371589
2258 snapd 19307 17314 846 1033 114
I actually don’t understand what use case snapd on Debian covers better than docker on Debian or snapd on ubuntu
A bit overdue, but as a Debian user who doesn’t contribute back, not really my place to criticize.
What do you mean by lacking?
I think QML apps are meant to be designed to work on touchscreens but whole pre-QML apps prioritize a mouse+keyboard interface I’d be curious as to how that sucks for touchscreens?
You can never be sure there is no spyware because if your infected a sufficiently advanced spyware can hide itself.
In theory you can use a liveCD to scan your OS for specious signs but if someone has written bespoke spyware for you it may be hard to detect as it won’t match any of the signatures.
Yeah it’s funny with AI they are deliberately obfuscating what they can actually do to scare people CEOs with FOMO.
Running an ISP is simpler than a powergrid, sewer system or water system.
It’s how rural America got electricity, it’s wild that the system is so captured that many people believe it’s easier to launch junk into space than to run cables to people’s homes.
That’s about it, I find it kind of annoying sometimes as it messes with stuff I knew how to do (harden per-user-tmp partitions), but overall the benefits to distro maintenance must be worth it so I don’t worry about it too much.
Much like the DoB stuff I find the pushback to it far more annoying than the actual inconvenience of sometimes not being able to configure a tweak how I’d like.
Maybe it’s not slop, but this can lead to lazy developers that don’t grok the code they write.
Linus was right to be sceptical about unit tests in the kernel, writing to test without understanding the problem is common in my paid job. The AI enabled equivalent of writing code without truly understanding it, is going to be much worse and is a separate issue to the pure slop AI generates at the moment.
You can prevent root login entirely using sudo and no root password.
Of course you could then override your init to give you a root shell, which you could avoid by having a grub and bios password.
But you’d be able to reset the bios password if you have physical access anyway.