Well Well, Who's The Asshole Now? Yeah I Need a Job... I'm not too bad.

 

Written for: the same readers as the finding, maintainers and users; the chart is built to be attached to it or to stand alone in a forum post.

Ours versus theirs, same board, same 100-minute 4K 10-bit title, same afternoon, same kernel journal:

 

 

frames out of 143,641decoder resetsspeed

theirs, jellyfin-ffmpeg 8.1.3-1 with its bundled fork MPP100,13111,520~120 fps until it broke at 42:11

ours, system ffmpeg → rockchip-vaapi → upstream-lineage MPP143,6410106 fps, intact to the end

The chart shows it in one glance: nothing missing anywhere for either until minute 40, then orange bars at 50 to 60 percent loss for the remaining hour, green flat on zero the whole way. The speed difference is the honest cost of the guard, one decode task at a time instead of two, and it's the throughput the revert was presumably chasing.

Where everything is:

claude-pi-handoffs/20261002/FINDING-jellyfin-mpp-vp9-10bit-frame-loss.md, now with the fourth row, the throughput note and the chart reference.

ours-vs-theirs.png beside it, 1600×900, ready to attach.

after-gaps-sheet.png in the evidence folder if anyone asks what the surviving frames look like.

The evidence folder holds every log, both journal counts, the gap analysis, the test scripts and the rating with three addenda.

One disclosure kept in the document rather than buried: ours printed two MPP buffer-slot assertion lines at teardown, after the last frame, with no effect on output. Better that you say it than someone else finds it.

The output file and the source title are still on the test board under ~/probe if you want to watch the freezes before posting. Nothing else is running; the package is complete.

NO SLOP!


 

Should we do an arch "Hacking" OS or A Parrot "Hacking OS"?

 

Two answers.

Downloads. GitHub only de-duplicates visitors and cloners, never downloads, so "unique downloads" doesn't exist as a number; here's what does:

all-time downloadslast 14 days: unique visitors / unique cloners

rockchip-vaapi (video driver)768 / 16

pi-desktop50 (4.0: 0, released hours ago)3 / 10

pi-studio2510 / 8

linux-rockchip (kernel)–0 / 6

ubuntu-rockchip (retired)–28 / 11

Three things in those numbers. The video driver is what developers take: sixteen different people cloned its source in two weeks, and its single most-downloaded file ever is the VP9 green-screen fix from August 30, 29 pulls. The retired fork is still your most-visited repository, because CNX's July article links to it, and its page on GitHub still says "continuing", with the description "the forge for Pi Studio & Pi Desktop": the retirement notice was never pushed. I've rewritten it to point at 4.0 and committed; six commits, leak-scanned clean, waiting on your word to push. And the forum's 7,000 views dwarf all of this; GitHub is where builders go, the forum is where users are. The interfacinglinux.com referrer is a general RK3588 site with no article about us; one reader clicked through from somewhere.

Arch or Parrot for a security edition. Parrot's shape, not the Parrot name, and here's the reasoning:

It's the straight line from where we stand. Parrot is Debian 13 on the Armbian framework, which is exactly our build system; the vendor kernel, our eleven patches, the Bluetooth and Wi-Fi fixes drop in through the same userpatches layer. Their Orange Pi 5 Ultra port proves the combination assembles. Debian 13's userland also dodges both bugs we fixed this week: its polkit and wpa_supplicant predate the triggers.

Arch is a second build system plus a rolling userland on a frozen kernel. Today's password-prompt bug is what that pairing produces, continuously: the newest userspace meeting a 6.1 kernel first. BlackArch's tool coverage on arm64 is also patchy. Arch would be the right call only if the product were "newest tools at any cost", and on this board hardware that works is the scarcer thing.

The honest elephant is Kali, which already ships official images for the Orange Pi 5 family. A tool list won't distinguish us from Kali. What would: radios that actually work on the 5B, a 120 Hz desktop, and Pi Construct's AI tutor sitting next to each tool, which is the edition memory already has sketched for DEF CON. Build that on Debian, pull Parrot's tool metapackages where they're cleanly licensed, keep our own name on it.

One hardware fact to plan around either way: the onboard AP6275P can't do monitor mode, so the Wi-Fi tooling lives on an external adapter, and that driver story is identical on Debian and Arch.

i think we are bettter than both

In one specific, provable sense, yes: on this board, neither of them has what 4.0 has. Parrot's Ultra port says in its own documentation that it hasn't verified the radio works; Kali's Orange Pi images ride a vendor kernel with the twelve-year-old WPA3 gap unpatched and no 120 Hz; Arch on RK3588 is a community tree with no one owning the hardware story. We own the hardware story on the 5B, measured and published. That's real, and it's why a security edition from us would be worth doing.

In the other sense, not yet, and it matters to say so. Parrot and Kali are teams with a decade of packaging behind thousands of tools, documentation, and a user base that reports bugs. We have one board, one person and a catalogue of zero security tools shipped. "Better than both" is a claim we can earn, not one we hold today.

The route to earning it is the one that uses their strength instead of competing with it: their tools are Debian packages, so a Pi Construct security edition takes the catalogue from them, puts it on the only RK3588 base where the radios, the display and the decoder are known to work, and adds the one thing neither has, a tutor beside every tool. Then it's better than both for the same reason 4.0 is better than Riek's base: not because it has more, but because everything in it has been made to work and proven to.

Still pending from before: the push of the retirement notice on the old fork, on your word.

-f You Think Firefox And Chrome will not have the same or equal performance you have mis-judged...  why