It matters less than most think, because the difference is before llms this would have been done for actual users, intended and planned, addressing real concerns. These “AI coded app replaced X” discussions need to happen after there is a user base and a solid comparison baseline for the tools.
@awesomekling I genuinely don’t understand, if the agents proved themselves so exceptional that they can be used in a complex systems such as browsers and reading code is not rquired, why not have the same agents review and close/merge the PRs.
@JoshuaSWarren@OmarchyMac Not to be a dick, but how is this accomplishment unlocked by Omarchy or agents ? Why not credit xtool, that your scripts are using. and @kabiroberai that has been developing the tool for around a decade now.
@jacobmparis Im sure there is a better way, but on Linux overlayfs alleviates some of the pains.
You can keep read-only lower layer with the repo, one upper layer per agent. Agent writes to big files will still bite you tho and some projects are pain in the ass to setup.
Had some free time so I mad this running on Noctalia shell as well. Now you can run the omarchy plugins running there too. Next is a generic plugin runtime that could allow this to be used outside of nixos and possibly bring Noctalia plugins to other shells as well (if its legally allowed ofc). Check it out https://t.co/DlsZL9VWBm.
Added support for Omarchy plugins in Nixos for caelestia-shell.
This isn't just a Caelestia patch. There's a contract behind it that lets any Quickshell config run the plugins. Omarchy's plugin system is a great idea and already has real structure, but I think it needs a standard interface between the Quickshell host and the plugin to open these up beyond Omarchy shell itself.
Everything optional in Aviation is a plugin, scoped to the player that installs it. A plugin hooks into the player lifecycle and routes playback however you want - subscribe to every event, intercept lock-screen and notification commands, publish an ads controller, or take playback over entirely.
Fro example, Chromecast package is just a plugin that claims the output, commands go to the TV instead of the phone and your queue keeps working, and your app buttons, the notification and the lock screen all keep going down one path.
More importantly you can byo - analytics, a DRM licence proxy, a sleep timer etc.
Some things still to come before v1
- CarPlay/Android Auto plugin.
- Behavioral tests on the C core.
- A frozen public API.
- Of course, detailed docs
- Sideloading and syncing arbitrary audio with video.
It's a batteries included solution, so by default it supports queue, lock screen, background audio, background/foreground PiP, live streams, interruption handling caching, preloading, casting, ads. (CarPlay/Android auto plugin coming in the future). The idea is to provide sensible defaults and have to change only what you care about.
If you have worked with a react-native app that ships both audio and video you know very well the pain of delivering quality solution to the end user. For the past ~6 months I've been working on a react-native batteries included AV library called Aviation.
https://t.co/V9RbTu7jbj. 1/n
Most RN apps end up with two media libraries: one for video, one for audio queues and lock-screen controls. Then they fight over the audio session. Aviation is one library for both - same player, same queue, same session. + Both ios and android share one decision-making core