

Removed by mod


Removed by mod


There was nothing in the question about jellyfin.
I’m on the jellyfin side, but you people have to chill, this is becoming Ford vs Chevy in here.


Migrated my storage from an old xeon-d to an arm SBC w 4GB ram and a sata hat. Performance is great, ZFS keeps up with all tasks, and less than a third of the power consumed. Backup scripts are running nightly without issue.
I am continually astounded by how well ZFS performs, even 15 years after I starting working with it. 4GB is enough for a mirror.


Apt v3 comes with some quality-of-life stuff that apt has been direly missing for years, and one of those is apt sources that make sense to a human.
So the new apt source files have local key location, components, suites, and Uris.
The sources from the before-time just had a one-liner with a uri and some components.
Edit:also the modernize command makes a backup of the source files it touches.


Most of my infra is Debian, and I did it without serious incident:
#Update everything to latest
apt update && apt upgrade && apt full-upgrade && apt --purge autoremove
reboot
#Verify that debian_version is 12.x (STOP IF NOT 12!)
cat /etc/debian_version
#Check for any pinned or held packages
apt list '?narrow(?installed, ?not(?origin(Debian)))'
apt-mark showhold
#Swap bookworm for trixie in repo files
sed -i 's/bookworm/trixie/g' /etc/apt/sources.list
sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/*
#Carry out update
apt update
apt upgrade --without-new-pkgs -y
apt full-upgrade -y
reboot
#Verify that debian_version is 13.x
cat /etc/debian_version
#Modernize apt sources to v3
apt modernize-sources -y
And then maybe apt update to make sure the updates still work OK.
Sometimes you have to make changes to certain repos that don’t have Trixie manifests, but that’s easy enough to roll back.


Yes, I’m sick of internal affairs having an over-inflated valuation also.


5 gunpowder, 4 sand, and 1 broadcast domain.
Seriously, though, tools like metasploit and python itself are a great place to start if you actually want to get into it.


Sure, that may be true. But I am not an international lawyer, so I can’t really speak to that point.
CVEs should be taken with an approach that the cve does matter, but that adding your own exposure to it is the only way to measure its impact on you.
This is a PXE boot environment vuln, so most of the self-hosting community itself probably doesn’t have this enabled at all. A person who does is likely very aware that PXE is already dangerously easy to misconfigure, especially in the days of remote init methods over https, which can at least be layered with other security solutions.


That is indeed a hot take. The cve involves crafting a PXE packet, so just… Don’t use PXE in your environment.
If you do, you already know of the dangers of signing exploits in boot images, DNS shenanigans, and all that.
I’m not saying this isn’t serious, but it’s not really the end of the world.


No argument here, but that wasn’t my point.


I’m not sure what you’re making here.


Well, the power efficiency being much better is one problem to solve. Also various laws need to make pronouncements on copyright, etc. There is also figuring out what will happen to open weight models, what will become of challenges like deepseek.
Ultimately, ai will remain in some form, or catalyze another kind of technology, but it will certainly change tech landscape the way the printing press did.


I suppose some folks were saying that about hydrogen-filled zeppelins too, but it turns out that you can’t just jam new tech down society’s throat that way.
We now have helium and hot air airships and the tech is used way more appropriately.
I do take your point that what whipped up AI frenzy isn’t just the tech, but the tech itself does needs to change before society will accept its ubiquity.
There are two kinds of self-hosters: those who backup, and those who will start testing em after their first failed restore.
Congrats on becoming one of the 5% of ppl who backup, but actually also test them.




Your said you were going to use the cloud services, so even if you self-host, using a cloud service api carries the same risk as using their apps. This is an app to unify all the remote storage things.
However, after looking at the code, I retract my comment and caution you not to use Drivebase:
[crypto]
# Generate: openssl rand -base64 32
masterKeyBase64 = "<base64-encoded-32-byte-key>"
If this is a salt or a seed, the documentation is wrong. But it looks like they’re using this base64 value as the actual key for whatever encryption Claude has vibe-coded into it.
base64 values can be reversed very trivially.
Don’t use this.


Regarding the access to cloud, it’s been done with fuse many times and it is very useful for those who need it.
You should know that many of these cloud services claim they “don’t know what’s in your files”, but have been shown to absolutely be able to access them on request from court order or law enforcement. Just saying.
Pirate library
Sure, yes. Acknowledged.
It is true that the referenced information is present in libgen, but it is not succinctly summarized for consumption, and that is the function Wikipedia fulfills for most users.
I can understand the pitfalls of allowing updates from the public, but I think it’s widely accepted that Wikipedia does more good than bad.
It’s really difficult to understand your point of view on this, especially when you indulge in semantics arguments.
Why. You were off to a great start.
I’m one of those neckbeards and web services should be free, as in a social service. So should potable drinking water.
Paying for a social service with money voluntarily or with your own data is not a really a choice between providers, it’s an admission that we should, in fact, all remain essentially cattle.