Interestingly enough, the stats for Piefed are nearly identical for both sources, the Lemmy delta is huge though.

I am curious why there is such a big difference between FediDB and Fedi Observer.

FediDB has Lemmy at 48 K MAU:

https://fedidb.com/ (Lemmy is the fourth entry on the platform list).

It’s likely cheaper to go with SODIMM and SODIMM is actually widely available.

Government overreach (or corruption and enablement of oligarchs) is the responsibility of the citizens.

While Nvidia’s ICMSP can consume around an exabyte of 3D NAND per annum in 2026 ~ 2027 in the best case scenario, it cannot really be a reason for 3D NAND price doubling overnight, as the industry produces over 800 EB of NAND every year. Meanwhile, we still do not know how much 3D NAND a typical VR NVL144 machine carries, so we cannot estimate storage demands for Rubin-based platforms in general.

While Nvidia ICMSP isn’t the only source of 3D NAND demand, this does look like SanDisk trying to capitalize on machine learning hardware, as opposed to being driven exclusively by supply and demand.

You can’t trust any American oligarchs or large American companies.

The “shadowy cabal” rhetoric is funny considering how there is zero real judicial overcite if US technology companies due to corruption in all three branches of the government.

Perhaps, but if anything they should have used this as a cover to ban twitter. I do not find American style ostentatious “freedom polemics” to be convincing, but on top of that Musk has been found to meddle in local politics to benefit the far right and promote UK criminals.

With US oligarchs “threats” and discussions do not work. Only action and the type of action that hurts them personally.

I just hope they re-release the 5800X3D, it doesn’t look it will make sense to move off AM4 for at least another ~2 years and I am mainly CPU bound. I would go with a 5900X3D too.

640K

That’s the one I used albeit it was older version even when I tried it in early 2025.

I always use the lowest “quality preset” (e.g. “slow”, “VerySlow” in x264/x265). The equivalent present in SVT-AV1 will was a number value (I believe 0 = placebo in x265/x264, I went 1/2).

Unless there have been massive improvements in SVT-AV1 in the last 12 months, you most likely get much longer encode time if you go with lowest quality preset equivalent in SVT-AV1.

Maybe I am missing something? Genuinely curious as I don’t have much experience with SVT-AV1 (I’ve done several hundreds of encodes of different levels of complexity with Xvid, x264, x265 over the past ~20 years).

Unfortunately AV1 encodes simply take too long for me at the 1/2 preset (equivalent to very slow) with a 8c/16t CPU.

I will probably give it another go on my next build (was planning an update to Zen6, but considering the price situation, I will have to wait another 2-3 years). And honestly my 5800X/3080 system is doing fine.

Macroslurp

I believe you’ll need a reader of some sort if you want to get the Pi running and you can’t SSH into it in its current state.

Try DietPi (Debian based ARM distro). It has an excellent set of custom CLI tools. They’ve been around for over a decade and have an active community and release cadence.

They even support Raspberry Pi 1/2 (I started with Pi 3 though):

https://dietpi.com/#download

Got to disagree with you on that one. It was universally true for the move from ASP/H263 to AVC/H264. It’s not the case with H264 to H265 on a universal basis.

You can forget about such results if you’re dealing with grain (and preserving it). Things are a bit better with “complex” content (oceans, snow storms etc), but you’ll be struggling to get 50% space savings (more so with pre 2005 content).

The general bitrate level is also a massive factor.

Low bitrates, sure, even more than 50%. But you’ll still be dealing with artifacts.

Medium to high bitrates (i.e. targeting a “near transparent” encode), you often won’t be able to replicate a H264 encode at 12 Mbps (1080p 24 FPS) with a 6 Mbps H265 encode. Sometimes it works, but often it doesn’t; I find you often need to go with 9-10 Mbps.

Haven’t tried H266/VVC. For AV1 the x4 increase in encode times didn’t seem to be worth it at high bitrates. Although for low bitrates AV1 seems to be modestly better than H265 (for far worse encore times).

This is all for CPU encodes at the “VerySlow” preset (1/2 for AV1 if I remember correctly).

I will speculate you will never see this with a Qualcomm platform (I am aware that you technically can run Linux on some X Elite devices).

Has there even been regime change in Venezuela? It looks like the current regime will stay, but they’ll have to give Trump and his oligarchs a cut (perhaps a large one).

Video compression has its limits. A modern BD release has a bit/pixel value of around 0.5 - 0.7, while streaming copies are around 0.1 - 0.2. You’re going to lose detail even if you use AV1 or H265.

Then you also have the problem that certain content (naval/oceanic scenes, storms, jungles) doesn’t compress as well.

IMO we are also starting to see lower “returns” with every new codec generation. MPEG4 ASP (Xvid) to H264/AVC was a massive jump. H264 to H265 (or even AV1) was IMO a much smaller jump.

That was my initial reaction as well! :/