Grabbed my bunch of 4K video samples (in VP9 and HEVC/H.265 formats) and gave the latest versions of #GStreamer a try, to see if my playback performance issues have indeed been solved. Well… it seems there's still some room for improvement with gtk4paintablesink 😉 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/work_items/5236
Happy nine to one of my favorite games of all time! Hundreds of hours playing this with the kids. So good. https://world.hey.com/dhh/house-rules-in-fortnite-16e0e5e8
https://bird.makeup/users/hypex/statuses/2081052683826319571
Video detection in ReadSeek will be based on a storyboard.
Qwen3-VL-2B processes only images; it does not understand videos. In other words, a video must translated into a meaningful set of images.
A storyboard is a tiled composite image generated from a fixed number of down-scaled video frames. Let’s mark this with N, and further constrain that N>2.
Algorithm:
Use two frames of the frame budget for start and end timestamp frames.Place the remaining N-2 timestamps initially even distances from each other.Shift the timestamps within 50% range of their initial distance with some yet to be defined best effort strategy. maximizing the difference between the frames. Note that timestamps positions form a O(2^N) problem as the timestamps affect each other as a system.
This idea could be taken out of the domain to an imaginary movie studio. What if you wanted back-engineer a storyboard to already shot material? A previous might be lost, or sometimes might not even exist.
Figuring out the answer to this question provides an optimal answer to the problem in my original domai
Nothing built in for Waybar etc, but agents are really, really good at this stuff. So you could surely have them help you convert your customizations to Quattro quickly. Keybindings should be fine.
I would not call landstrip and opencode-landstrip as stable software just yet, but at least I've started to forget that the sandbox is active, unless it asks for a new permission.
I hit a bug in every two or three days, and the code base becoming less of a chaos i.e., all the convergence metrics are pointing to the right direction :-) Windows was quite rotten up until recent releases when I got some great feedback from an actual dog food eating Windows user.
While the most of the sandbox implementations taken the obvious container approach, I modeled a coding agent as follows:
1. A coding agent are bit like web browsers.
2. Thus, the process model for a sandbox should be modeled from a browser tab.
Based on these premises I made a Linux-container-free implementation, which protects the sensitive data with a combination of Landlock and SECOMP filters in Linux, Seatbelt (SBLT) in macOS and Win32 AppContainer framework in Windows, and adheres to Anthropic Sandbox Runtime JSON policy.
The chose approach has also many robustness benefits. E.g., nested containers are not required for CI runs.
My 3rd inference engine will land to Landstrip in foreseeable future. It will be be part of the sentinel layer for I/O, which protects the secrets even when prompt injection attacks are in effect.