I think having separate standard APIs for screenshots, screen capture, and video capture that aren’t married to one implementation makes sense.
The idea of a using a separate thing for it is fine, in itself, but necessitating it is an issue to me. There are a LOT of wayland compositors now, for all sorts of systems, each one also new needs a compatible xdg portals implementation (or whatever third party tool you like), in the case of xdg portals this also means pulling in things like dbus. It actually becomes a lot to build a “Minimal but fledged out” ecosystem. something which should otherwise be possible.
we’re talking about standalone desktop apps, they need some common building blocks no matter if they’re containerized or not, right?
sure but then you have xdg-portals denying actually useful a11y protocols because they “don’t want to expose it to containers” -_- apparently they never heard of a permissions system? but this also highlights why the wayland ecosystem right now is so poor for select individuals (and why they get heated when told that they need to swap to wayland)
I have a couple of issues with portals. One is that we’re putting too much eggs in the basket of something that is designed for containers. XDG portals Have rejected features that people have requested because they don’t want to expose that functionality to a container and they are allergic to permission prompts apparently.
I also have other issues with the portals for instance video capture. It requires you to have a camera portal. It requires you to have a desktop capture portal. It also requires you to have an app to app, video, portal, which doesn’t exist yet. All of these things require pipewire pretty much in most cases, so why can’t we just have a single pipewire portal? It may not scale well in the future, but it doesn’t scale well now anyways. If you want just a generic pipe wire stream, you’re not gonna be able to have it, you’re going to have to conform to one of the standards anyways. For a case in point example, the OBS pull request for Game Scope Capture is the perfect example of this over reliance in XDG portals.
I’m showcasing this just to highlight the fact that the XDG portals are incredibly poorly thought out, and I don’t think that it’s a reliable method for the future going forwards.
PS. Please pardon any oddities in this, I had to use speech to text, since my RSI is acting up.
I did and quite frankly it’s trash, XDG portals are a clunky and quite frankly terrible and poorly thought out api. I’m not the only one that disagrees with this sentiment as multiple people are trying to get protocols like ext-screencopy-v1 for screen recording and ext-foreign-toplevel-* for window management upstreamed into wayland so that xdg portals aren’t necessary for these use cases. I don’t mind the reliance on pipewire too much, but I too think that It shouldn’t be necessary for screen capture.
IMO It is one of nate’s worst takes of all time if not the worst. Usually I agree with most things he writes, but not this, xdg-portals is a travesty, pipewire is nice and all, but I don’t see why we should need an entire media system for basic screen capture capabilities. and clearly im not alone on this sentiment
woops my bad, I mean to link this github.com/…/wayland-x11-compat-protocols it’s a repo of going to be protocols, to fill in the gap instead of pretending the issue doesn’t exist
I fell for the lie of flatpak not being bloated, I just nuked flatpak from my PC since I just run arch anyways. Im not sure if repo is safe to remove. You might be able to run rmlint -g and see how much data can be deduplicated on an FS level, I never checked myself since I run f2fs, but if you run an FS with dedupe capabilities it may work for you.
For sure try out olive You can’t do automatic stabilization but manual works fine, However I will always use gyroflow whenever possible anyways. If needed you can easily script motion tracking data from 3rd party sources.
but it is properly color managed throughout the entire editor so doing color correction works properly and accurately. the node system is really powerful despite it’s early nature, and as far as I know olive is the only FOSS editor with proper OCIO integration, which means you get industry standard color management tooling including things like ACES support. You also have OTIO support for importing and exporting editorial cutting information.
i’ve been using sonobus lately and it’s been pretty good, I had latency issues when I tested the android app a long time ago, ill have to test it again
You could probably look into something like paperwm or Niri, I think scrollable window managers have a lot of potential to be a novel but good touch experience
EDIT: Im not sure if niri support touch, I havent tested it, but I think i might actually try it myself when I get the chance now
I am, very hesitantly, optimistic for the new smithay based compositors. Cosmic doesn’t have touch support yet, but it’s super light weight, I get better perf then I do even with KDE. I plan on swapping to it full time on my tablet when it gets touch support. (and when some touch friendly gui stuff is available). you also have catacomb which is an actual mobile compositor. Very promising stuff, but still very far out
I find that even if you get a touch primary device, make sure to get one with a keyboard, Ubuntu, Fedora, doesn’t matter, KDE, Gnome doesn’t matter, the touch only experience on linux is simply not great. Make extra sure to get the keyboard with it if its optional.
it’s not accurate to say android is centred on touch input. Android has some of, if not the most diverse input options, mouse and keyboard works fine, also there is a large library of apps compatible with remotes/gamepads. While that might be how a lot of people normally interact with it, android is very well developed to be diverse
android as desktop works pretty decently actually, it can be quite nice when you set it up, especially for lower end hardware, and ofc, if you need more flexibility, you can run linux in a chroot and use x11 to bring the screen to the android env. or go vice versa and use waydroid in linux and your desktop, then simply swap out when you dont need it. (though waydroid can be harder on low end hardware)