ParetoOptimalDev

joined 2 years ago
[–] ParetoOptimalDev 2 points 22 hours ago

Sounds like endorsement to me.

[–] ParetoOptimalDev 7 points 1 week ago (3 children)

I heard https://www.onlyoffice.com/ is good, but have no personal experience.

[–] ParetoOptimalDev 14 points 1 week ago (5 children)

Pixel + GrapheneOS is a dream.

[–] ParetoOptimalDev 0 points 1 week ago

Preventing supply chain attacks for one.

[–] ParetoOptimalDev 8 points 1 week ago (1 children)

You are so right. We should just leave it be and make no noise.

[–] ParetoOptimalDev 8 points 2 weeks ago (5 children)

Mints outdated drivers can definitely cause issues for beginners.

[–] ParetoOptimalDev 4 points 1 month ago (3 children)

No, people who want something approaching chatgpt but local want to run at least deepseek V3 32B.

Qwen at least fares much worse for my usage as do deepseek V3 under 32B.

[–] ParetoOptimalDev 10 points 1 month ago (2 children)

The Rust code isn't closed source, but I'd strongly prefer a coreutils replacement to use GPL over MIT as well.

[–] ParetoOptimalDev 7 points 1 month ago

Already fixed, in software that's existed for years and is used by millions. But Oh no, memory issues, let's rewrite that in ! will surely result in a better outcome.

Rsync is great software, but the C language fates it to keep having memory issues in spite of its skilled developers.

Preventing a bug from being possible > fixing a bug.

[–] ParetoOptimalDev 9 points 1 month ago (4 children)

I fear moving away from GPL that moving to Rust seems to bring, but Rust does fix real memory issues.

Take the recent rsync vulnerabilities for example.

https://www.cyberciti.biz/linux-news/cve-2024-12084-rsyn-security-urgent-update-needed-on-unix-bsd-systems/#more-2215

At least this one in a Rust implementation of rsync would have very likely been avoided:

CVE-2024-12085 – A flaw was found in the rsync daemon which could be triggered when rsync compares file checksums. This flaw allows an attacker to manipulate the checksum length (s2length) to cause a comparison between a checksum and uninitialized memory and leak one byte of uninitialized stack data at a time. Info Leak via uninitialized Stack contents defeats ASLR.

[–] ParetoOptimalDev 77 points 1 month ago (15 children)

I would love this news if it didn't move away from the GPL.

Mass move to MIT is just empowering enshittification by greedy companies.

view more: next ›