Quack Doc

specific parts. you need metal to withstand the pressures of the actual bullet to get a somewhat degree of reliability, so any pressure bearing part needs to be metal, everything else can be plastic, but the more metal the better. Now you can get some more basic designs with parts that you could fabricate at home, but a lot of the higher end designs require off the shelf gun parts.

The “leading design” right now is the FGC-9 which is actually seeing a degree of use in myanmar(??). The design requires metal parts that could be feasible to fabricate at home. However it is shockingly easy, even in heavily restricted countries, to be able to order the metal parts.

we already have them. It’s not hard to make a firearm, and the 3d printed weapons scene has taken off quite well. all of the good ones still need metal parts ofc, but they are pretty easy to get your hands on in many cases.

I like both, airsoft does happen to be a whole lot cheaper though

Edit: Accidentally thought it was a Glock at first, my bad.

Sig boys are seething

not enough guns, needs a rifle and a shotgun at least.

Yes, there are open source firearms. there is even 3d printed designs for an MP5 the youtube channel Print shoot repeat showcases a lot of them.

The issue with flat packs is the more you use it, the higher the chance that you get less shared runtimes and the higher the chance of the duplication. And at some points it really does get to awfully ridiculous levels.

A while back, I had run everything I possibly could with Flatpak to the point I’d even make my own Flatpak to try and see how well it would work. Instead of using the AUR. And it worked great for the first little while. I’d installed all of my apps and it was fine, but as I kept using the system, kept installing new apps and not uninstalled the old ones, it really started to build up awfully quick, especially with older apps.

I feel like the usefulness of flatpaks is the inverse parabola, where it’s extremely useful in the center use, but when you go to either side of it, it becomes less and less useful.

Apologies for any incoherentcy this was written with a speech 2 text.

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 https://github.com/probonopd/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

Really glad probonopd is doing this, X11 is dying but wayland isnt ready to replace it, so it’s nice to have this

EDIT, paste didn’t work https://github.com/probonopd/wayland-x11-compat-protocols

I use mpvpaper on sway and cosmic

not to mention the totally bogus comparison they preformed which is an insult to anyone who has a even an inkling into how image metrics and comparisons work and more then 30sec to compare

Google has been trying to clamp down on people daring to run software they don’t approve on their devices.

“Google” isn’t. ChromeOS is actually providing more and more flexibility then ever. Android however is the exact opposite. One must keep in mind that google isn’t some monolithic company, it’s very fractured and has many independent teams, the best showcase of this is JXL. 3/4 top contributors to libjxl are google employees, and yet chromium decided to remove JXL support citing bogus reasons generated by obviously flawed testing and analysis.

crostini is pretty damn great but it’s important to know what it IS and it’s actually really simple. Crostini is two things combined into one

Firstly A VMM

Crostini uses the crosvm VMM which is can be thought of kinda like an inhouse version of qemu but designed to explicitly run natively integrated and high performance VMs safely instead of being a swiss army knife (KVM acceleration, virtio peripherals etc) (PS. it’s written in rust too) They use it for chromeOS to integrate android support (on select newer devices) and linux. It runs a supervisor distro which can run containers inside of it.

ChromeOS calls the VM termina. Im not sure what distro is running in the VM, or if its a specialized one. I forget

Next is the containerization

It is a lot like distrobox, It can run a myriad of distros but the key part of it is sommelier. A wayland compositor designed to render windows through virtio-wayland, an extension of virtio-gpu. In practice very similar waypipe which rendering wayland windows to a remote wayland client using network/sockets (Yes, it does support AV_VSOCK so it can work with qemu.)

Sommelier is run in the containerized Distro, running on the TerminaVM. Using termina provides excelent security and performance, and then using LXD inside of termina provides excellent flexibility

The guts of “crostini” crosvm, virtio-wayland, sommelieris all open source, you can actually (with some degree of hassle) set this up entirely yourself, or do what I do, and run qemu + waypipe for a similar experience. Waypipe is much easier to setup however it comes at a preformance detriment since qemu virtio-gpu perf is worse then crosvm (no vulkan support in qemu yet still)

EDIT: s/Architecturally/in practice/ I have no idea why I said Architecturally. they are quite different things. I must have had a brain fart

I just get any windows tablet that has good linux support and throw bliss on it, Linux tablet situation is bad right now

I am aware of that, but even with it there’s still a decent amount of waste.

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.